FastBots + Make.com
Most chatbot integrations only fire one way: chat happens, then a row lands in a sheet. With FastBots and Make, you can do that, and you can also call your trained chatbot from inside a scenario and use its reply in the next step. It works as an AI agent for the apps you already automate.
New ScenarioDraftProviding AI Chatbots to Trusted Brands Around The World
إجابات سريعة
It's a two-way connection between your FastBots chatbot and Make.com scenarios. Make can react to events in the chat (like a captured lead) and your scenarios can also send a message to the bot and use its reply as input for the next step.
The FastBots app isn't in Make's public marketplace yet, so searching won't find it. You install it through the FastBots invite link in our help guide, which opens Make and adds the app to your organisation in a couple of clicks.
Two things. Outbound: a visitor submits the chat lead form and your scenario routes that lead to a CRM, sheet, Slack or email tool. Inbound: any event in Make sends a prompt to your trained bot and uses the answer in the next module: for example, drafting an email reply from your help-centre content.
No. You connect FastBots with your account API key, pick the bot from a dropdown, and drag modules onto the scenario canvas. The same skills that built your existing Make scenarios are all you need.
لماذا FastBots
Use FastBots as the trigger when a lead is captured, or as an action that returns a grounded AI reply for the next module. Most teams end up running both.
The 'Lead generated' trigger fires the moment a visitor submits the chat form. Your scenario runs straight away; no polling, no delay.
The 'Send message' action posts a prompt to a chosen bot and returns the reply. It's effectively a private LLM endpoint, grounded in your own content.
Route an inbound support email into a scenario, ask the bot to draft a reply from your help-centre content, then send it through Gmail or your provider of choice.
Send captured details straight into Google Sheets, HubSpot, Pipedrive, Notion or anywhere else Make connects, with whatever enrichment steps you want in between.
FastBots is an AI chatbot trained on your content. Through Make, it can also act as an AI agent: looking things up, drafting answers and triggering downstream work without you wiring a separate model.
Because the bot is trained on your website, files and Q&As, every reply Make pulls back is anchored in your real product, pricing and policies, not generic AI output.
Each bot can use a different supported model from OpenAI, Anthropic or Google. Use a lighter model for quick lookups and a stronger one for drafting tasks.
سيناريوهات واقعية
Lead form submitted in chat → enriched in Make → created as a new contact and deal in your CRM, with a Slack ping to the sales channel.
A new support email arrives → Make sends the body to your bot → the bot's reply (grounded in help-centre content) goes back to the customer through Gmail.
Someone fills a Google Form → Make passes the answers to the bot as a prompt → the bot returns a personalised response that's emailed to the submitter.
Scheduled run each morning → bot summarises today's FAQs or internal docs → summary posted to a Slack channel for the team to skim.
Any tool that supports webhooks can hit a Make scenario, get an AI answer from your trained bot, and pipe that answer back into its own workflow.
Captured leads are routed based on what they asked about, pricing leads to sales, support leads to a helpdesk, partnerships to a different mailbox.
Log every captured lead, the questions asked and any unanswered ones into Notion or Airtable so you can spot patterns and improve the bot's content.
Chat collects project details → Make adds them to a sheet, creates a folder in Drive, and sends a custom proposal template, all from one lead submission.
جربه مجانًا
Does This Match The Scenario You're Trying To Build?
خطة مجانية، دون الحاجة إلى بطاقة ائتمان. أنشئ أول روبوت دردشة خاص بك في غضون دقائق.
الإعداد
Open the invite link from our help guide, click Install, select your Make organisation and finish the wizard. The FastBots app then appears in any scenario search.
In Make, create a connection using the API key from your FastBots account page, then pick the chatbot you want to use from the dropdown.
Use 'Lead generated' as a trigger to react to new leads, or drop 'Send message' into any scenario to call your bot and use its reply in the next module.
جربه مجانًا
Spin Up A Bot Free And Wire It Into Make Today
خطة مجانية، دون الحاجة إلى بطاقة ائتمان. أنشئ أول روبوت دردشة خاص بك في غضون دقائق.
Very easy-to-use service. It takes 10 minutes to set up a bot. Service also very good value for money.
هل لديك أسئلة؟
الأسئلة الأكثر شيوعًا قبل قيام الفرق بالتسجيل. إذا لم تجد سؤالك هنا، فسيقوم فريق الدعم لدينا بالرد عليك في غضون ساعات خلال أيام العمل.
The FastBots app isn't published in Make's public marketplace yet. You install it through an invite link in our help guide. Open it, select your Make organisation and click Install. The app then shows up in any scenario you build.
Two. 'Lead generated' is an instant trigger that fires when a visitor submits the chat lead form. 'Send message' is an action that posts a message to a chosen bot and returns the bot's reply, ready to use in the next module.
Not through Make. Workflows run after a triggering event; typically when a lead is captured. The earlier 'Zapier AI Actions' style of mid-conversation tool calling isn't part of the product today. If you need the bot to do something live, capture the details in chat first, then let Make handle the action.
In FastBots, copy your API key from the Account section. In Make, when you drop a FastBots module into a scenario, choose 'Create a connection', paste the key and save. You can then pick the specific bot from a dropdown.
Yes, that's the whole point of the 'Send message' action. The bot's reply comes back as the action's output, so you can map it into a Gmail send, a Slack message, a sheet row, a Notion page, or anywhere else Make supports.
Make and Zapier workflow integrations are available from the Essential plan ($39/month). The free plan is great for building and testing a bot first, but live customer-facing scenarios need a paid plan. See the live pricing page for the latest details.
Probably not on its own. The bot handles the first-pass questions and Make routes the rest. For teams that want a real person to take over a live chat, that's a separate feature. Live Chat with human handover is included on the Business plan and above.
You pick the model on the bot itself, not the scenario. Each bot can use a supported model from OpenAI, Anthropic or Google. A common pattern is to create one bot for lightweight lookups and another tuned for longer-form replies, then point your scenarios at whichever fits.
Both are supported and the capability set is similar: a 'lead generated' trigger and a 'send message' action. Most teams choose based on which platform their other automations already live in. If you're a Make user, this integration slots in alongside everything else.
Connections use your FastBots API key, and uploaded data isn't used to train OpenAI models through the API. Treat the API key like a password and only share it with Make scenarios you control. For sensitive use, you can also mark a bot private and restrict where it can be embedded.
Spin up a chatbot on the free plan, then wire it into Make whenever you're ready. No credit card needed to start.
