Make (Integromat)

Status

There is no custom Kerabie Mail app in Make's app directory, and none is currently planned: Make's app-building tooling requires its own hosted web IDE under a paid developer account, which is out of scope for now. What's below, using Make's general-purpose Webhooks and HTTP apps, is the actual, current way to use Kerabie Mail from Make, not a placeholder for something coming later.

Receiving events

1. In a Make scenario, add Webhooks → Custom webhook as the first module and create a new webhook. Make gives you a unique URL.
2. Register that URL as a Kerabie Mail webhook endpoint, from Settings → Webhooks in the console, or via the API:

curl -X POST https://api.kerabie.email/webhooks \
  -H "X-API-Key: $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
        "url": "https://hook.us1.make.com/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
        "events": ["email.received"]
      }'

Pick any event from the events table (mail delivered, sent, bounced, opened, clicked, and more). The custom webhook module's determined data structure will match the payload envelope documented for webhooks: event, timestamp, webhook_id, and an event-specific data object.

To verify the X-Kerabie-Signature header, add a Tools → Set variable / custom function step computing the same HMAC-SHA256 scheme described in the signature verification guide, and route the scenario to stop if it doesn't match.

Sending email

Add an HTTP → Make a request module configured as:

URL:    https://api.kerabie.email/mail/send
Method: POST
Headers:
  X-API-Key: YOUR_API_KEY
  Content-Type: application/json
Body type: Raw / JSON (application/json)
Request content:
{
  "from_email": "support@yourdomain.com",
  "to": ["{{customer_email}}"],
  "subject": "{{subject}}",
  "body_html": "{{html_body}}"
}

Map values from any earlier module in the scenario. See the full field list, including templates, scheduling, and attachments, in the Send email API reference.

Authentication

Create an API key under Settings → API Keys with the send scope for the HTTP module, and webhooks if you're also managing the endpoint from the API rather than the console. Pass it as the X-API-Key header on every request.

See also