Integrations
Connect Make, Google, Zapier and your own tools to Agentim: connected accounts, webhooks and the API.
Ways to connect#
| Tool | How | Guide |
|---|---|---|
| Make | The Make step, with a connected Make account. Or an HTTP step to a Make webhook. | Make step |
| Google Sheets, Calendar, Gmail | Google steps and triggers, with a connected Google account. | Google Sheets |
| Zapier, n8n, Pipedream | An HTTP step calls their webhook. Their action calls Agentim's Catch Hook. | Zapier and others |
| Your own system | An HTTP step calls your API. Your system calls Catch Hook. | HTTP, Catch Hook |
| Website forms | The Start a flow trigger gives your form a link. | Start a flow |
| Zendesk, Intercom, other help desks | Not set up in the app. Use HTTP and Catch Hook. | Zendesk and Intercom |
Connected accounts#
Accounts your steps use are connected once, for every chatbot of your Agentim account. Click Integrations in the sidebar. Make and Google steps also let you connect right inside the step, with a Manage connections in Integrations link under the connection.
Make: one connection for the whole account. Choose the Make region, paste a Make API token, then pick the Organization and Team the steps work in. Only the account owner or an admin can connect, change or disconnect it. Step by step: Connect Make.
Google accounts: connect as many as you need, with Connect Google. Each account shows its status and when it was last used:
- Connected: working. Check tests it with Google.
- Sign in again: Google stopped accepting Agentim for it (password change, removed access, or 6 months unused). Click Reconnect. Until then, steps using it take their Error output.
- Allow more: a step needs a permission the account hasn't given yet, for example Gmail. Approve it once in Google's window.
- Disconnect: steps and triggers using the account stop working with Google, and Agentim's access is removed at Google too. You can connect it again later.
Agentim keeps only an encrypted key Google gives it. Your files and events stay in Google.
Zapier, n8n and other tools#
Any tool that has webhooks works with two building blocks:
HTTP step
POST to the Zapier webhook
Zapier / Make / n8n
your automation
Catch Hook
POST /sendMessage
- 1
Agentim to the tool
In the tool, create a webhook trigger (in Zapier: Webhooks by Zapier > Catch Hook) and copy its URL. In Agentim, add an HTTP step:
POST, that URL, and a JSON body with the answers you want to send. The Send to Make webhook template sets this up for Make. - 2
Test it
Click Test call in the HTTP step so the tool receives a sample and learns the fields.
- 3
Handle failures
Turn on the Error output in Errors & retries and connect it. Publish warns you about Make, Zapier, Pipedream and n8n steps without one.
- 4
The tool to Agentim
To have the tool message a customer, add a Catch Hook step to your chatbot and call
POST https://api.agentim.ai/sendMessagefrom the tool's webhook action, with your API key in thex-agentim-tokenheader.
Zendesk and Intercom#
Zendesk and Intercom can't be set up from the Agentim app. To connect a help desk, send its events to a Catch Hook and call its API with an HTTP step.
Common mistakes#
| Problem | Fix |
|---|---|
| No Integrations in the sidebar. | Make and Google steps aren't available on your account yet. Use HTTP and Catch Hook instead. |
| "Only the account owner or an admin can connect Make." | Ask the owner or an admin. Everyone else can use the connection once it exists. |
| The tool never receives data. | Run Test call in the HTTP step and check the status and answer. Check that the URL is the tool's current webhook URL. |
| The chat stops when the tool is slow. | Connect the HTTP step's Error output, and set a Timeout and Retries. |