Chatlayer Documentation
Get in touchAbout Chatlayer
  • Welcome
  • What's new
  • Send feedback
  • start quickly
    • Leadzy tutorial
      • 0. Introduction
      • 1. New bot, new block
      • 2. Understand your users
      • 3. Collect and display user input
      • 4. Steer the conversation with Conditions
      • 5. Empower your bot with Actions
      • 6. Set up a channel and publish your bot
    • Templates
      • Banking
      • E-Commerce Returns
      • E-Bike Shop
      • E-Scooter Support
      • Feedback
      • Find Nearest Location
      • GPT
      • 🆕Gym
      • Job applications
      • Knowledge base AI template
      • Lead generation
      • 🆕NPS
      • Restaurant
      • Retail
  • navigation
    • Analytics
      • Dashboard
      • Customers
      • Conversations
      • User flow
      • Intents
      • 🆕Funnels [Beta]
    • Bot builder
      • Flows
        • Canvas functionalities
        • Collaborate with team members
        • Manage your flows
        • 🆕[Beta] Export and import flows
      • Bot dialogs view
      • Translations
      • Events
    • NLP
      • Dashboard
      • Intents
      • Expressions
      • Entities
      • Train
      • NLP settings
      • Improve
    • Knowledge base AI
      • Add content to your KBAI
      • Build your KBAI flow
      • Use your KBAI source URL in a button
      • Use tags to limit your KBAI content
      • 🆕Use Tables to store your KBAI questions
      • 🆕Manage handover where KBAI is unsatisfactory
    • History
      • Conversations
      • Execution logs
      • Versions
    • Channels
    • Tables
      • Create a table with records
      • Column types
      • Operate on your records
        • Insert record
        • Update record
        • Retrieve record
        • Delete record
      • API
    • Settings
      • Bot settings
      • Offloading
      • Variables
      • Voice
      • Import/Export
  • build your bot
    • Conversation design
      • Plan your bot
      • Conversation design workflow
    • Flow logic
      • Blocks
        • Message
        • Condition
        • Collect input
        • Action
      • Go-to connections
    • 🆕Emulator
    • Tips & best practices
      • Route your flow depending on the time
      • Improve the Not understood block
        • How to create better not understood messages
        • Not understood counter
        • Not understood Google search
      • Go to previous block
      • Recognizing a returning user
      • Skip introduction message
      • Route your flow depending on the channel
      • Reuse flows
      • Connect two bots to each other
  • understand users
    • Natural language processing (NLP)
      • Basic NLP concepts
      • Detect information with entities
        • Match entities
        • Contextual entities
        • System entities
        • Composite entities
      • NLP best practices
        • Word order and diversity of expressions
      • AI intent booster
      • Train your NLP
      • Context
      • NLP import & export
      • Sentiment analysis
    • Languages
      • Supported languages
      • Make your bot multilingual
      • Change language within the conversation
  • set up channels
    • Add a channel to your bot
    • All channels
      • 🚨Facebook Messenger [Deprecated soon]
        • Facebook Admin Removal
        • Facebook Webview Whitelisting
        • Facebook Messenger API updates for Europe
      • 🚨Google Assistant [Deprecated soon]
      • Webhook
      • Web
        • 🚨Web V1 [Deprecated]
          • Customize web widget
          • Live example web widget
        • 🆕Web V2
          • 🆕From Web V1 to V2
          • 🆕Web V2 methods and options
    • Sinch Conversation API
      • Configure your Sinch Conversation API
      • 🆕 Make the most of RCS with Carousels
      • WhatsApp Business API
  • integrate & code
    • API calls
      • Configure your API integration
      • Advanced API features
      • V1 API Reference
      • Custom integrations 101
    • Code editor
      • [Example] Sending data to Airtable (POST)
      • [Example] Retrieving data from Airtable (GET)
      • [Example] Making SOAP requests
    • App integrations
      • Airtable
      • Freshdesk
      • Freshdesk Messaging
      • 🆕Gmail
      • Intercom
      • Mailgun
      • OpenAI: GPT-3, ChatGPT and GPT-4
      • Salesforce
      • 🆕Slack
      • Topdesk
      • Zendesk Support
      • Zendesk Sunshine (beta)
    • 🆕Expression syntax
    • Human handover & live chat
      • Sinch Contact Pro
      • #Interact
      • Genesys Cloud
      • Offloading Webhook
      • Salesforce Service Cloud
      • Sparkcentral by Hootsuite
      • Zendesk Chat
    • Chatlayer messages specifications
  • Publish
    • Publish your bot
      • Publish a flow
  • Analyze & maintain
    • Analytics definitions
    • Data retention
    • Maintenance
    • Session
    • Track events for analytics
  • VOICE
    • 🆕Send bot response as audio
    • Voicebots
      • Create a voicebot
      • Voicebot-specific actions
      • Test your voicebot
      • From chat to voice
  • access & support
    • Identity & Access
      • Single Sign-On (SAML SSO)
    • Billing & subscription
    • Get in touch
    • Chatlayer glossary
    • SaaS Regions & IP Ranges
    • Status
    • Debug your bot
      • No correct response
      • Collect input not working
      • Video isn't working
Powered by GitBook
On this page
  • Publishing only NLP before publishing selected flow
  • Publishing sub-flow

Was this helpful?

  1. Publish
  2. Publish your bot

Publish a flow

Step by step on how to publish selected flow

PreviousPublish your botNextAnalytics definitions

Last updated 11 months ago

Was this helpful?

Previously, when using ‘publish’, all flows in your project would be published to the live version. However, now you can select a specific flow to publish. This can be useful if you only want to make updates to a specific flow and don’t want to publish the entire project.

Bear in mind, before you can publish a selected flow, it is necessary to perform a full publish. Without completing the full publish, the selected flow won't be executed.

1. First, select the flow that you want to publish from your list of flows.

2. Once you have selected the flow, click on the ‘three dots’ icon located at the top right corner and select ‘publish’.

  1. In the modal, include a brief description of your publication. Once you've entered the description, proceed by clicking the 'publish' button.

  1. Once you click ‘publish’, your publishing flow is started.

  2. Go to ‘history>version’ page, you will see the flow that you have selected to publish. Here you can see that the selected flow is in progress to be published.

  1. Once your flow has been successfully published, you will see a ‘live mode icon’ confirming that the publishing process is complete.

  1. If your published flow encounters an issue, you'll notice the status column displaying 'failed.' Clicking to expand the row will provide you with more details about the reason behind the failed publishing.

  1. To see your newly published flow, click on switcher button next to publish button on top navigation bar. This will open the live version of your flow, after which you can see that your selected flow is published to live.

Publishing only NLP before publishing selected flow

When using the ‘flow publish’ feature, it’s important to note that only the selected flow will be published. Any changes you’ve made to the NLP will not be included in this flow publish.

If you make changes to the NLP on your selected flow that you want to publish, you will need to follow a two-step process to ensure these changes are reflected in the selected published flow:

  1. On top navigation bar, click ‘publish’ button‘ then make sure to select ‘publish NLP’. This will ensure that any updates you’ve made to the NLP are published separately from the flow.

  1. After the NLP changes have been published, you can then publish your selected flow by following the process described at the top of this article. This will ensure that your flow is-up to date with the latest NLP changes.

By following this two-step processes, you can ensure that both your flow and NLP changes are accurately reflected in the published version of your bot.

Publishing sub-flow

The main flow needs to be published first on the live version. Otherwise, it won't let you publish your sub-flow(s).