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

# Make

> Add one HTTP module to a Make scenario so every AI draft is checked before it sends.

Put one **HTTP → Make a request** module between your AI module and your send module:

```text theme={null}
trigger → AI module (OpenAI, Claude, ...) → HTTP: DataVibe gate → Router → send / hold / log
```

## 1. Store the API key

Create a key at [app.datavibe.cc/security/api-keys](https://app.datavibe.cc/security/api-keys).
In Make, add it once under **Keys** (or a scenario variable) and reference it from the module. Do
not type it into the module where it is visible to anyone who opens the scenario.

## 2. Configure the HTTP module

| Field | Value |
| - | - |
| URL | `https://api.datavibe.cc/v1/gate/outbound` |
| Method | `POST` |
| Headers | `Authorization: Bearer <your DataVibe key>`, `Content-Type: application/json` |
| Body type | Raw, content type `JSON (application/json)` |
| Parse response | Yes |

Request content (map the fields from your earlier modules):

```json theme={null}
{
  "recipient": "{{1.email}}",
  "subject": "{{2.subject}}",
  "body_html": "<p>{{2.body}}</p>",
  "body_text": "{{2.body}}",
  "idempotency_key": "make-{{1.id}}-{{2.version}}",
  "metadata": {
    "integration": "make",
    "recipient_first_name": "{{1.first_name}}",
    "company": "{{1.company}}",
    "role": "{{1.title}}"
  }
}
```

The `{{1.…}}` and `{{2.…}}` references are placeholders for your own module numbers. Passing
`recipient_first_name`, `company`, and `role` turns on the wrong-name, wrong-company, and
wrong-role checks.

> [!NOTE]
>
> For WhatsApp, SMS, Telegram, LinkedIn, or Slack, use `https://api.datavibe.cc/v2/gate/outbound`
> and add `"channel": "whatsapp"` (or the right channel). Only `recipient` and `body_text` are
> required for non-email channels.

## 3. Route on the result

Add a **Router** after the HTTP module, with one filter per route on `{{3.data.status}}`:

| Route | Filter | Next module |
| - | - | - |
| Send | `status` equals `APPROVED` | Your send module (Gmail, Smartlead, CRM) |
| Hold | `status` equals `QUEUED` | Log or notify; a reviewer approves it in DataVibe |
| Stop | `status` equals `BLOCKED` or `FAILED` | Log `{{3.data.policy_violations}}`; do not send |

`SENT` means DataVibe already delivered it, so do not send again.

## 4. Fail closed on errors

Right-click the HTTP module → **Add error handler** → **Break** (or **Rollback**). If the gate
times out or returns an error, the draft must not reach the send module. Re-running with the same
`idempotency_key` returns the original decision and is not billed twice.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.