Make

What it does#

The Make step connects your chatbot to Make (formerly Integromat) without copying webhook URLs. It runs in the background: the customer doesn't see it. It can:

• Run a Make scenario: runs an on-demand scenario of your Make team with the data you choose, waits for its outputs, and saves them for later steps.
• Send to a Make webhook: sends the data you choose to a webhook of your Make team. The scenario behind it runs in Make.
• Build a new scenario with the assistant: describe what should happen in Make, and the assistant plans the scenario for you to confirm.

Only the fields you add under Data to send leave Officely.

Connect Make#

Officely connects to Make once for the whole account. Every chatbot and every Make step uses that connection. Only the account owner or an admin can connect it.

1. 1

   Open Connected accounts

   In the Chat Builder, click Settings and scroll to Connected accounts > Make. You can also connect from inside any Make step.

2. 2

   Choose the Make region

   In Make region, pick eu1.make.com, eu2.make.com, us1.make.com or us2.make.com. It's in your Make address, for example eu2 in eu2.make.com.

3. 3

   Create a Make API token

   In Make: your avatar > Profile > API access > Add token. Tick the scopes Officely lists: organizations:read, teams:read, scenarios:read, scenarios:write, scenarios:run, hooks:read, hooks:write and connections:read. mcp:use is optional.

4. 4

   Paste and connect

   Paste the token in Make API token and click Connect Make. Officely checks it with Make, stores it encrypted and never shows it again.

5. 5

   Choose the organization and team

   Under Where should the assistant work in Make?, choose the Organization and Team, then click Use this team. Make steps and the assistant work only there.

When it's done, the section shows Connected and "The assistant works in: Organization · team X". Click Change to pick another team: scenarios already created stay where they are.

Disconnect deletes the saved token and revokes the Officely API keys the assistant created for Make, so those scenarios can't send messages anymore. The scenarios stay in your Make account.

Run a scenario#

1. 1

   Drag Make onto the canvas

   It's under Webhook and API. Connect the step before it and click it.

2. 2

   Pick the action

   Under What the step does, choose Run a Make scenario.

3. 3

   Choose the scenario

   Pick it in Scenario. Only scenarios scheduled On demand can run from Officely: others show (not on demand). Click the reload icon after you change something in Make.

4. 4

   Fill the inputs

   Under Data to send, the scenario's inputs are listed for you. Fill each one from the conversation, for example {{@full_name}} or {{#cphone}}. Click Add a field for more.

5. 5

   Set the wait

   Wait for the result (seconds): 5 to 40, default 30. If Make takes longer, the step takes its Error output.

6. 6

   Name the result

   Under Result, Save result as is make by default. Later steps use {{#make.outputs.<name>}}, {{#make.execution_id}} and {{#make.status}}.

7. 7

   Connect both outputs

   Connect Success to the next step and Error to a fallback message.

Send to a webhook#

1. Choose Send to a Make webhook.
2. Pick it in Webhook, or click Create a webhook, give it a name (for example New lead from the chatbot) and click Create.
3. Under Data to send, add the fields. They're sent to the webhook as JSON.
4. The result is saved as {{#make.status}} and {{#make.body}} (what the webhook answered).

If no scenario uses the webhook yet, the step says so: the data waits in Make until a scenario picks it up.

Build a scenario with the assistant#

Choose Build a new scenario with the assistant, add the fields you want to send under Data to send, and click Open the assistant. The assistant opens with the step's details. Finish the sentence "In Make it should: ...", for example "find the customer in my Google Sheet and email the sales team".

The assistant shows every change before it happens and waits for your confirmation: Create (inactive), Turn on, Turn off or Run once. It lists any personal data the automation sends. When you confirm the plan, this Make step sends to the new scenario's webhook.

Results, errors and testing#

Under Save fields as variables, copy a field of the result into its own short variable, for example outputs.orderId -> orderId.

When Make fails, the chat continues on the Error output, with the reason in {{#make_error.message}} and a short code in {{#make_error.code}}. If Error isn't connected, the chat stops at this step and you get an alert. The run itself is never retried, so a scenario can't run twice by accident.

The preview chat doesn't call Make: it shows "Would run ..." and continues on Success. To run it for real, use Try it in the step: fill sample values and confirm. It really runs the scenario, so it may send a message or add a row.

Common mistakes#