1. Store the API key
Create a key at 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
Request content (map the fields from your earlier modules):
{{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.
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}}:
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 sameidempotency_key returns the original decision and is not billed twice.