Deploy your Flow App
Deploying has two parts: publishing your flow (promoting Draft → Live) and connecting a provider (wiring up a channel so real users can reach it).
Publishing
Finish your draft
Design and simulate your flow until it behaves correctly.
Click Publish
In the project toolbar, click Publish. Flow App Studio copies the current Draft to the Live version. The Flow Engine immediately starts routing sessions through the new Live flow.
Continue iterating
Your Draft remains editable after publishing. Changes to Draft do not affect Live users until you publish again.
You can publish as many times as you like. Each publish replaces the previous Live version.
Setting up a Provider
Providers are configured once at the organisation level and then linked to projects via Access Points.
Go to Providers → Add Provider, choose the channel type, and fill in the required credentials.
Telegram
Telegram can auto-register its webhook — Flow App Studio calls the Telegram Bot API on your behalf after you save credentials.
Required credentials:
| Field | Where to get it |
|---|---|
bot_token | @BotFather — /newbot command |
Create a bot
Open Telegram and message @BotFather. Run /newbot, follow the prompts, and copy the token it returns.
Add credentials
In Flow App Studio’s Providers page, select Telegram, paste your bot_token, and save.
Auto-register
Flow App Studio calls https://api.telegram.org/bot{token}/setWebhook automatically. Your flow is live immediately.
Line
Line can auto-register its webhook.
Required credentials:
| Field | Where to get it |
|---|---|
channel_access_token | LINE Developers Console → Messaging API channel |
channel_secret | Same console |
Viber
Viber can auto-register its webhook.
Required credentials:
| Field | Where to get it |
|---|---|
auth_token | Viber Admin Panel → Bot account |
WhatsApp (Meta)
WhatsApp requires manual webhook registration in the Meta Developer Dashboard.
Required credentials:
| Field | Where to get it |
|---|---|
phone_number_id | Meta Business Suite → WhatsApp → Phone Numbers |
access_token | Meta Developers → App → Access Tokens |
verify_token | Any string you choose — you’ll use it in the next step |
Add credentials
In Flow App Studio, create a WhatsApp provider with the three fields above. Copy the Webhook URL displayed after saving.
Register the webhook in Meta
Open your Meta App → WhatsApp → Configuration. Paste the Webhook URL and your chosen Verify Token. Click Verify and Save.
Subscribe to messages
In the same Meta console, subscribe to the messages webhook field.
Instagram (Meta)
Instagram follows the same Meta webhook pattern as WhatsApp.
Required credentials:
| Field | Where to get it |
|---|---|
access_token | Meta App → Instagram → Access Tokens |
verify_token | Any string you choose |
Register the webhook URL manually in the Meta App dashboard under Instagram → Webhooks.
Slack
Required credentials:
| Field | Where to get it |
|---|---|
bot_token | api.slack.com/apps → OAuth & Permissions |
signing_secret | Same app page → Basic Information |
Register the Webhook URL in your Slack App under Event Subscriptions → Request URL.
Microsoft Teams
Required credentials:
| Field | Where to get it |
|---|---|
app_id | Azure Bot registration |
app_password | Azure Bot → Configuration → Client Secret |
Configure the messaging endpoint in your Azure Bot to point to the Webhook URL from Flow App Studio.
Discord
Required credentials:
| Field | Where to get it |
|---|---|
bot_token | discord.com/developers/applications → Bot |
application_id | Same page → General Information |
public_key | Same page → General Information |
Set the Interactions Endpoint URL in your Discord Application to the Webhook URL from Flow App Studio.
USSD
USSD requires manual configuration. Flow App Studio generates a webhook URL for each Access Point. Share this URL with your USSD aggregator/gateway.
Configure the request mapping in the Access Point to match the field names your USSD provider sends:
| Platform field | Typical USSD provider field |
|---|---|
id | sessionId |
user_input | ussdString |
custom_key_1 | msisdn |
custom_key_2 | network |
Set the newline character your USSD provider expects (commonly \n or \r\n).
Access Points
After creating a Provider, link it to your project by creating an Access Point (Trigger):
- Open your project → Access Points → New
- Select the provider
- Copy the generated endpoint URL and register it with your provider
- Configure request/response mapping if the defaults don’t match your provider
See Design → Access Points for the full mapping reference.
IP Whitelisting
For additional security, you can restrict which IP addresses can call your webhook. Add allowed IP addresses to the provider’s IP Whitelist. Requests from other IPs will be rejected.
Leave the whitelist empty to accept requests from any IP. Only restrict it if your provider has static outbound IPs.