

Send every new Messenger conversation to Slack in real time
This Flow fires the moment a visitor starts a conversation in your Messenger, posts it to your Slack support channel with the customer's name, the first message, and a direct link back, and gets eyes on the chat while the visitor is still on the page.
Live chat only wins when someone answers fast. But nobody keeps the Customerly inbox open on a second monitor all day, so new Messenger conversations sit unseen while the team works out of Slack. First response times creep up, visitors leave the site, and hot leads go cold in the exact minutes they were ready to talk. The tool where the conversation starts and the tool where your team pays attention are not the same tool.
Every new conversation that starts in your Messenger shows up in your Slack channel within seconds, with the customer's name, email, company, the transcript, and a direct link that opens the conversation in Customerly. Whoever is around clicks it and replies while the visitor is still there. Optionally, an AI Assistant answers first and Slack only gets pinged when Aura escalates to a human. No tab babysitting, no missed chats.
The Flow you'll build
This is the exact Flow as it appears in the Customerly editor. Drag it around, then follow the steps below to build it.
Notify Slack on every new conversation
Alternative: let Aura answer first, escalate to Slack only when needed
Aura resolves routine questions on her own. Slack only gets pinged when she escalates the conversation to a human.
Step by step
- 1
Create a Slack incoming webhook for your support channel
Slack webhookIn Slack, open Apps → Incoming Webhooks → Add to Slack, pick the channel where new chats should land (for example
#support-inbox), and copy the webhook URL. It looks likehttps://hooks.slack.com/services/T0000/B0000/XXXXXXXXX.One webhook posts to one channel, so if you later want Aura escalations in a separate channel (step 4), create a second webhook for that channel now while you're in the Slack settings.
Treat the webhook URL like a password. Anyone who has it can post to your channel, so keep it inside the Flow config and out of shared docs.
textSlack channel suggestion#support-inbox - 2
Create a Flow with a New Conversation Started trigger
FlowIn Customerly, go to AI Studio → Flows → New Flow. Name it
Messenger → Slack. Choose New Conversation Started as the starting point, so the Flow fires the moment a visitor opens a new conversation in the Messenger.The trigger also lets you filter the audience that enters the Flow. Leave it open to everyone for a plain notification channel, or narrow it to a segment (for example paying customers only) if you only want Slack pings for a subset of your traffic.
textFlow nameMessenger → Slack - 3
Add a REST API block that posts the conversation to Slack
REST API blockAdd a REST API step after the trigger. It POSTs a message to the Slack webhook from step 1 with the contact's details, the conversation transcript, and a direct link back to the conversation in Customerly. The
{{...}}placeholders are conversation and contact properties that Customerly fills in at run time.Paste your webhook URL as the endpoint, keep the single
Content-Typeheader, and use the payload below as is. If you want to add or change fields, the complete guide about conversation properties lists every property you can use, and the REST API action docs cover the block itself.httpHTTP method + endpointPOST https://hooks.slack.com/services/T0000/B0000/XXXXXXXXXhttpRequest headersContent-Type: application/jsonjsonRequest body{"text":"🆕 New conversation started\nContact ID: {{contact.user_id}}\nEmail: {{contact.email}}\nName: {{contact.name}}\nCompany: {{company.name}} ({{company.company_id}})\nConversation: {{conversation._url}}\nLast message: {{conversation._transcript | escape: "json"}}"} - 4
Optional, let Aura answer first and escalate to Slack only when needed
AI AssistantIf pinging Slack on every conversation is too chatty, put Aura in front. Add an AI Assistant step between the trigger and the REST API block. Aura answers the customer using your Help Center knowledge, and the block exposes two branches: Solved and Escalation. Connect the Escalation branch to the Slack REST API block, so your channel only hears about the conversations that actually need a human.
You don't need an AI Mission here. Missions are for tasks that follow specific instructions, like collecting fields or filing a ticket. Answering questions from your knowledge base is exactly what the AI Assistant block is for (see the AI actions docs).
jsonRequest body for the escalation ping{"text":"🚨 Aura needs a human on this conversation\nContact: {{contact.name}} ({{contact.email}})\nCompany: {{company.name}}\nConversation: {{conversation._url}}\nTranscript: {{conversation._transcript | escape: "json"}}"} - 5
Send a test message and turn it on
FlowOpen your own website in an incognito window, start a conversation in the Messenger, and watch the Slack channel. You should see the message land within a couple of seconds, with your test name and transcript filled in. Click the conversation link and confirm it opens the right conversation in Customerly.
Then reply from the inbox and confirm nothing extra shows up in Slack. The trigger only fires when a conversation starts, so your own replies never echo into the channel. Once both checks pass, publish the Flow and tell the team new chats now announce themselves.
FAQ
Why not use Zapier or Make for this?
You can, but you don't need to. This runs natively inside Customerly with a single REST API block, so there is no third tool to pay for, no task quota to watch, and no extra place where the automation can silently break.
Will it ping Slack when my teammates reply?
No. The New Conversation Started trigger fires once, when the customer opens the conversation. Replies from your team, notes, and Aura's answers never re-trigger the Flow.
Which variables can I use in the Slack payload?
Any conversation, contact, or company property, like {{contact.email}}, {{company.name}}, {{conversation._url}}, and {{conversation._transcript}}. The complete guide about conversation properties in the Customerly docs lists them all.
Can I route different conversations to different Slack channels?
Yes. Create one incoming webhook per channel, then add a Conditional that branches on whatever you care about, such as the contact's plan or a segment, and point each branch at a different REST API block.
Won't this get noisy on busy days?
Put Aura in front (step 4). The AI Assistant resolves routine conversations on her own and only the escalations reach Slack. You can also narrow the trigger's audience filter to the segment you care about.
SaaS teams running this in production
Customerly tools used in this recipe
Ready to ship this recipe in your workspace?
Book a 1:1 demo and we'll build this Flow live in your Customerly account.
More AI Recipes
Auto create bug tickets in ClickUp from a Customerly conversation
Stop spending 5 minutes per bug copy pasting from chat to ClickUp. Fire one Flow and Aura collects the missing info, files the ticket, and replies in the conversation with the link.
Read the recipeCatch churn signals in support chats and loop in the CSM with full context
Customers don't churn on the day they cancel. They churn 3 months earlier, in a support chat. Aura listens for the signal, pings the CSM in Slack, and opens a renewal at risk task in HubSpot, automatically.
Read the recipeQualify inbound demo requests with AI and create HubSpot deals only for in target leads
Stop letting your SDRs spend hours qualifying out wrong fit leads. Aura asks the right questions, decides if the lead is in target, and only then creates a HubSpot deal and notifies the AE.
Read the recipe