AI Studio

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.

How to get thereOpen your agentAI StudioAppsThe Zapier, Make and n8n cards are in the Automation category. The template chips in the Studio start the same setup.

This turns your agent into a front door for your whole automation stack. It talks to the visitor, 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. Inside a skill, the agent collects the values you define (a name, an email, an order number, anything you like) and sends them to your webhook URL as structured data the moment the skill runs.

There is no account sign-in and nothing to install on either side. The webhook URL is the whole connection, and you set it up by talking to the build agent, the same way you build any other skill.

Direction matters. The connection goes from a conversation to your workflow. Your agent triggers workflows; a workflow cannot start a conversation or send the agent a message on its own.

What you can build

Leads into your CRM. The agent collects name, email and context, marks the conversation as a lead, and your Zap or scenario writes it to the CRM, a sheet, or a Slack channel.
Notifications with real data. A visitor 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.

Want answers, not just triggers? If your goal is to fetch data into the conversation, build the workflow in Make or n8n. Use Zapier for everything that only needs to happen after the chat, like updating a CRM or sending a notification.

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 build conversation
On the Apps page, open the Zapier, Make or n8n card and click Connect. The build agent opens a conversation with everything prepared. The Zapier, Make and n8n chips in the Studio's template row do the same.
Describe the skill
Tell the build agent when the skill should trigger and which details to collect, for example "when a visitor asks for a quote, collect name, email and company size". Paste your webhook URL when it asks for it. The agent assembles the skill for you.
Test it
Switch to Test mode and chat like a visitor. Check your Zap run history, Make execution or n8n execution list to confirm the data arrived, then set the skill live.

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 visitor gets a real, current fact instead of a canned response.

Keep these workflows fast. The agent waits only a short moment for the reply (about twenty seconds), so a workflow that answers in a second or two feels instant, while a slow one falls back to a friendly "I could not check that right now". Return a small, clean result rather than a big data dump: the agent only ever sees a bounded summary of the response, which also keeps it from inventing details.

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.
Self-hosted n8n needs a public HTTPS address. An instance 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: build a skill with the API call tool and paste that platform's webhook URL.

Treat webhook URLs like passwords. Anyone who has the URL can send data to your workflow. Ultimo Bots stores it inside your skill and never shows it to visitors, and you should share it just as carefully.

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 live test.

How skills workThe building blocks behind this: tools, triggers, and the build agent.Connect your appsNative app actions for Calendly, Stripe, HubSpot, Mailchimp and more.Book a callFree 15-minute session to wire up your first workflow together.