When a new lead is created in ArtiBot.ai, send a message to a Slack channel
Each time ArtiBot.ai records a new lead from your chatbot, this workflow posts a message about it to the Slack channel you pick, so your sales team sees the lead where they already talk.
ArtiBot.ai
Slack2 steps Setup ~5 min Used on 1.9k sites Free to import
What this workflow does
A chatbot can collect leads around the clock, but those leads sit in the ArtiBot.ai dashboard until someone thinks to check it. If your team lives in Slack, a lead that nobody opens for a day is a lead that went cold for no reason. This workflow brings each one into a channel the moment ArtiBot.ai reports it.
The ArtiBot.ai trigger, Lead Created, fires when your bot captures a new lead. The details ArtiBot.ai sends with that event become data you can place in a message. FlowMattic then runs Send Channel Message in Slack, which posts your text to one channel, with the lead's details filled in from the event.
There is no Filter in the template, so every lead the bot creates produces one Slack post. You write the message yourself after import, which means you decide how much of the lead to show. Task History keeps a record of each run, so you can check what was posted for a given lead.
Website chatbot leads for a sales team
Your site's ArtiBot.ai bot collects names and contact details from visitors. Each new lead appears in a #leads channel, where a rep can claim it with a reply in the thread.
Appointment requests at a local service business
The bot gathers details from people who want a visit or a call. Posting each lead to a shared channel lets whoever is free pick it up and call back.
Campaign landing page with a bot
During a launch, a bot on the landing page takes enquiries. The marketing channel gets a post for each lead, so the team can see the campaign producing contacts.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
ArtiBot.ai Lead CreatedFires when ArtiBot.ai creates a new lead from a chatbot conversation. The lead data sent with the event is passed on for the Slack message.
- Slack Send Channel Message
Sends your message to one Slack channel each time a lead comes in. Write the text, insert lead details from the ArtiBot.ai event, and connect your Slack workspace on import.
What you need
- FlowMatticCore
- ArtiBot.ai AccountAccount
- Slack AccountAccount
After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.
Make it yours
Changes worth making after you import it.
- Run one test conversation with your bot after import, so FlowMattic captures a real lead and you can see which lead fields are there to place in the Slack text.
- Add a Filter after the trigger if only some leads should reach Slack, for example leads where a phone number is present.
- For a private channel, change the action to Slack's Send Private Channel Message. To alert a single person, use Send Direct Message instead.
Questions about this workflow
Does every ArtiBot.ai lead post to Slack?
Yes, as imported. Each Lead Created event produces one message. Add a Filter after the trigger if you want some leads left out.
Which ArtiBot.ai details can go in the Slack message?
Whatever the Lead Created event carries for that lead. Create a test lead after import, then look at the captured data in the Slack step to see what you can insert.
Can ArtiBot.ai leads go to a private Slack channel?
Not with this action, which posts to regular channels. Swap in Slack's Send Private Channel Message action for a private one.
Are leads captured before I turn the workflow on sent to Slack?
No. The trigger reacts to new leads, so only leads created after the workflow is active produce a message.
More Notifications & Alerts workflows
Other ready-to-import templates from the same category.
Import this workflow into your WordPress site
Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.
30-day money-back guarantee Unlimited workflows and runs Self-hosted