Connect

Integrations

Connect Make, Google, Zapier and your own tools to Officely: 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 Officely'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	Channels for your AI flows.	Channels

Connected accounts#

Accounts your steps use are connected once, for every chatbot of your Officely account. Open any chatbot in the Chat Builder, click Settings and scroll to Connected accounts.

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 Officely 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 Officely's access is removed at Google too. You can connect it again later.

Officely 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

Officely sends a new lead to Zapier with an HTTP step; Zapier later sends an update back with Catch Hook.

1
Officely to the tool
In the tool, create a webhook trigger (in Zapier: Webhooks by Zapier > Catch Hook) and copy its URL. In Officely, 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 Officely
To have the tool message a customer, add a Catch Hook step to your chatbot and call POST https://api.officely.ai/sendMessage from the tool's webhook action, with your token in the x-officely-token header.

Zendesk and Intercom#

Zendesk and Intercom are channels, not steps: your AI flows answer tickets there.

Intercom: the Officely app adds an AI assistant to your Intercom Inbox. Sign in to Officely from the app, choose one of your AI flows, and click Answer this ticket for me to draft a reply.
Zendesk: Officely can answer Zendesk tickets with your AI flows. It's set up for your account by the Officely team. Contact support to start.

See Channels for details.

Common mistakes#

Problem	Fix
No Connected accounts section in Settings.	Make and Google steps aren't turned on for your account yet. Use HTTP and Catch Hook meanwhile.
"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.