> ## Documentation Index
> Fetch the complete documentation index at: https://docs.thinnest.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Make.com

> Trigger Make.com scenarios from your agent. Paste a webhook URL from a Make.com scenario and the agent can POST structured payloads to run the scenario.

# Make.com Integration

<Note>
  Make.com is configured through the unified **[API & Webhooks](/docs/tools/api-webhooks)** tool in **Webhook** mode. This page covers the Make-specific setup; see the unified tool page for everything else.
</Note>

Trigger your Make.com scenarios directly from an agent conversation. The agent fires a webhook when something worthy happens (new lead captured, appointment booked, support ticket raised) and your Make scenario picks it up to do whatever you've wired — create a CRM record, send a Slack message, add a Google Sheets row, anything Make supports.

## How it works

1. In Make.com, create a scenario that starts with a **Custom webhook** trigger.
2. Copy the webhook URL Make generates (looks like `https://hook.eu2.make.com/abc123xyz`).
3. In thinnestAI, add the **Make.com** tool to your agent and paste the URL.
4. When the agent decides to trigger the scenario, it POSTs a JSON payload to that URL.
5. Make receives the payload and runs your scenario.

No API keys, no OAuth, no per-platform credentials. The webhook URL itself is the auth — Make gives each scenario a unique unguessable URL.

## Setting it up

### Step 1 — create the Make scenario

1. Log into [Make.com](https://www.make.com/) and click **Create a new scenario**.
2. Add a module. Search for **Webhooks** and pick **Custom webhook**.
3. Click **Add** to create a new webhook. Give it a name like "thinnestAI agent events."
4. Make will show you a URL. Copy it.
5. Wire the rest of your scenario (add modules to do work on the incoming data — HubSpot create contact, Slack post, Google Sheets append row, etc.).
6. Save the scenario and toggle it to **ON** (top-left switch). A turned-off scenario won't run even if it receives a webhook.

### Step 2 — add the tool in thinnestAI

1. Open your agent → **Tools** → **Add Tool** → **API & Webhooks**, and choose **Webhook** mode.
2. Paste your Make.com webhook URL and (optionally) name it "Make.com".
3. (Optional) Add a secret. If you set one here, it gets sent as `X-Webhook-Secret` header — your Make scenario can verify it as a simple authenticity check.
4. Save.

### Step 3 — tell the agent when to use it

Add a line to your agent's instructions:

```
When a user gives you their contact details and says they want a demo,
trigger the Make.com scenario with their name, email, phone, and any
preference they mentioned.
```

The agent now has two LLM-callable functions:

| Function                                                                                      | When to use                                                                        |
| --------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
| `send_event(event_name, customer_name, customer_email, customer_phone, notes, custom_fields)` | Structured CRM-style events (new lead, callback, ticket). Use this for most cases. |
| `send_webhook(data, event_type)`                                                              | Free-form — send any JSON you want. Use for non-CRM use cases.                     |

## Payload format

Every request Make receives has this shape:

```json theme={null}
{
  "event": "new_lead",
  "source": "thinnestai",
  "data": {
    "customer_name": "Sarah Johnson",
    "customer_email": "sarah@acme.com",
    "customer_phone": "+1-555-0100",
    "notes": "Wants pricing for 50 seats, Enterprise plan"
  }
}
```

In Make.com, after the first successful fire, the webhook module will remember this structure — you can map `1.data.customer_name`, `1.data.notes`, etc. into downstream modules.

## Example: lead capture → HubSpot + Slack

**Voice flow:**

```
User: "Hey, I'm Rahul from Acme. Can you send me pricing?"
Agent: "Sure — what's the best email and phone to reach you on?"
User: "rahul@acme.com, +91-98-1234-5678"
Agent: "Got it. I'll get that out to you right away."
       [calls send_event with customer_name="Rahul", customer_email="rahul@acme.com",
        customer_phone="+91-98-1234-5678", event_name="pricing_request"]
```

**Make scenario:**

```
Custom Webhook → HubSpot: Create Contact → Slack: Send Message to #sales
```

**Result**: Rahul is in HubSpot with the right properties, the sales team gets a Slack ping with his details, and it happened inside the live call — the agent didn't need to hand off.

## Securing the webhook

Make.com gives you an unguessable URL, which is the first line of defense. For extra protection:

1. In the thinnestAI tool config, set a **Secret** (any random string).
2. thinnestAI sends it as `X-Webhook-Secret: <your-secret>` header on every request.
3. In your Make scenario, add a **Router** or **Filter** module right after the webhook that checks the header matches your secret. Reject (do nothing) if it doesn't.

Make doesn't have first-class request-header validation in its UI, but you can use a **Tools > Switch** module to check `1.headers.x-webhook-secret === "your-secret"` and halt the scenario if not.

## Limits & pricing

* **Make's free tier**: 1,000 scenario operations per month. Each webhook call = 1 operation, plus each subsequent module.
* **thinnestAI's side**: no per-call charge. Unlimited webhook triggers from the agent.
* **Latency**: the agent waits for Make to respond (up to 15s timeout). If Make takes longer, the agent sees a timeout and may apologize to the user.

## When to use Make.com vs. alternatives

| Need                                                      | Use                                                                                     |
| --------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| Trigger a scenario with many steps (CRM + Slack + Sheets) | **Make.com** (this tool)                                                                |
| Trigger an n8n workflow                                   | Use the [n8n tool](/docs/tools/n8n) instead                                             |
| Generic HTTP webhook to your own backend                  | Use the [generic Webhook tool](/docs/tools/crm-webhooks#webhook-tool-zapier--make--n8n) |
| Deep native CRM integration (Gmail, HubSpot, Sheets)      | Use the native [Gmail](/docs/tools/gmail) / [Sheets](/docs/tools/google-sheets) tools   |

## Troubleshooting

| Symptom                                       | Fix                                                                                                                               |
| --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| Agent says "Webhook returned status 404"      | Scenario is OFF in Make. Toggle it on.                                                                                            |
| Agent says "Could not connect to webhook URL" | URL is wrong or Make is down. Copy the URL again from the webhook module.                                                         |
| Make fires but data is missing                | Your scenario's modules are mapped to the old payload structure. Re-run the webhook, let it re-learn the JSON shape, then re-map. |
| Multiple webhooks arriving                    | LLM is retrying. Usually fine — Make.com scenarios should be idempotent (dedupe on `data.customer_email` or similar).             |

## Configuration reference

| Field                    | Required | Description                                                                     |
| ------------------------ | -------- | ------------------------------------------------------------------------------- |
| **Make.com Webhook URL** | Yes      | The `https://hook.*.make.com/...` URL from the Custom webhook trigger module.   |
| **Secret**               | No       | Random string sent as `X-Webhook-Secret` header for scenario-side verification. |

## Next steps

* **[n8n](/docs/tools/n8n)** — same pattern but for self-hosted n8n workflows.
* **[CRM & Webhooks](/docs/tools/crm-webhooks)** — the generic webhook tool and CRM lookup patterns.
* **[Gmail](/docs/tools/gmail)** — native Gmail integration (deeper than triggering a Make scenario).