Zapier, Make & n8n
Your agent can trigger the workflows you already run in Zapier, Make or n8n. A skill sends the details it collects in a conversation straight to your workflow's webhook, and with Make or n8n the workflow can even send data back that the agent uses in its answer.
This turns your agent into a front door for your automation stack. It talks to the customer, gathers what your workflow needs, and hands the result to the tools you already use: your CRM, a spreadsheet, a notification, or any custom logic you have built.
How it works
Every workflow platform can start a workflow from an incoming webhook: a unique URL that accepts data. Ultimo Bots uses exactly that. Mo builds a skill with a building block that sends the values you name (a name, an e-mail, an order number, anything you like) to your webhook URL as JSON the moment the skill runs. The skill can record the conversation as a lead in your Leads inbox at the same time.
There is no account sign-in and nothing to install on either side. The webhook URL is the whole connection. On the Skills tab the building block shows up under Uses as API with the platform's address, and View call shows exactly what is sent.
What you can build
- Leads into your CRM. The agent collects name, e-mail and context, records the lead, and your Zap or scenario writes it to the CRM, a sheet, or a Slack channel.
- Notifications with real data. A customer asks for a callback, and your workflow pings the right teammate with everything the agent gathered.
- Answers from your own systems (Make and n8n). The workflow looks something up, for example a row in a Google Sheet or a record in an internal tool, sends it back, and the agent works the result into its reply.
- Anything else your platform can do. If you can build it as a workflow with a webhook trigger, your agent can start it from a conversation.
Zapier, Make or n8n?
All three receive data from your agent the same way. The difference is the way back: whether the workflow can respond with data the agent then uses in its answer.
| Platform | Send data to it | Use its data in answers | Good to know |
|---|---|---|---|
| Zapier | Yes | No | A Zap always confirms receipt immediately and runs afterwards, so it cannot send results back into the conversation. Webhook triggers need a paid Zapier plan. |
| Make | Yes | Yes | Add a Webhook Response module at the end of your scenario and the agent receives whatever it returns. |
| n8n | Yes | Yes | End your workflow with a Respond to Webhook node. A self-hosted n8n must be reachable from the internet over HTTPS; n8n Cloud always works. |
Set it up
Copy your webhook URL
In Zapier, create a Zap that starts with the Webhooks by Zapier trigger (Catch Hook) and copy the hook URL. In Make, add a custom Webhook trigger to your scenario and copy its URL. In n8n, add a Webhook node and copy the production URL, not the test URL.
Start the request to Mo
In AI Studio, open the Apps tab and click Zapier, Make or n8n under Available. The dialog explains what the platform can and cannot do. Click its button, for example Connect Zapier: Mo's input now holds the request Please connect my agent to Zapier through a webhook. I will give you the webhook URL. The agent should send this:
Tell Mo what to send
Finish the sentence with when the skill should run and which details to send, for example when a customer asks for a quote: name, e-mail and company size. Send it and paste your webhook URL when Mo asks for it. Mo builds the skill and tells you what it does.
Test it
On the Test tab, chat like a customer. Check your Zap run history, Make execution or n8n execution list to confirm the data arrived.
Getting data back into answers
With Make or n8n, the same webhook call can return data. Your workflow does its work, for example reading a spreadsheet row or calling an internal system, and replies with the result. The agent then weaves that result into its answer in natural language, so the customer gets a real, current fact instead of a canned response.
Keep these workflows fast. The agent waits about 20 seconds for the reply, so a workflow that answers in a second or two feels instant. If the workflow does not answer in time or returns an error, the agent tells the customer honestly that it could not complete the step instead of pretending it worked. Return a small, clean result rather than a big data dump: the agent only sees a limited part of a long response.
Limits to know
- Zapier cannot reply. Zapier confirms receipt before your Zap runs, so its results can never appear in the conversation. That is a Zapier design decision, not a setting.
- One direction. Conversations trigger workflows. A workflow cannot message your agent or start a chat.
- Zapier webhooks are a paid Zapier feature. The Webhooks by Zapier trigger is not available on Zapier's free plan.
- Public HTTPS addresses only. The webhook URL must start with https and be reachable from the internet, and it must answer directly: redirects are not followed. A self-hosted n8n behind a firewall or VPN cannot be reached. n8n Cloud works out of the box.
- Other platforms work too. Anything that accepts webhooks, such as Pipedream or Activepieces, can be wired up the same way: describe what you need to Mo and paste that platform's webhook URL.
Need a hand?
If you would rather set this up together, book a free 15-minute integration call and we wire your first workflow with you, from webhook URL to test.