Mailbase
FeaturesPricingDocsBlogComparisonsChangelog
Sign inStart free
Home/Docs/No-code integrations
IntegrationsUpdated 2026-05-25

No-Code Integrations With Zapier, Make, And n8n

Connect Mailbase to Zapier, Make, or n8n with REST Hooks: subscribe a callback URL to an event, sample real payloads while you build, and unsubscribe when the automation is turned off.

Canonical: /docs/no-code-integrations
On this page
What The Hooks API IsAuth ModelConnect Zapier, Make, Or n8nSubscribable EventsPayloads And SignaturesLifecycle RulesCallback URL Rules

What The Hooks API Is

Mailbase exposes a REST Hooks surface under /api/hooks. A visual builder registers a callback URL for one event type, receives a signed POST every time that event happens, and deletes the registration when the user switches the automation off. This is what Zapier, Make, and n8n expect from a platform; it is not the same thing as pasting a webhook URL into Settings.

A subscription is backed by a normal Mailbase webhook endpoint, so it appears in Settings alongside endpoints your team added by hand, it is signed with the same HMAC scheme, and its deliveries show up in the same delivery log.

EndpointMethodPurpose
/api/hooks/eventsGETList subscribable event types with human descriptions and their sample fields.
/api/hooks/subscribePOSTRegister a callback URL for one event. Returns the subscription id.
/api/hooks/subscribeGETList the current workspace's subscriptions.
/api/hooks/subscribe/{id}DELETEUnsubscribe. Called when the automation is turned off.
/api/hooks/sample?event=GETRecent real payloads for one event, so the builder can render field names.

Auth Model

Every /api/hooks endpoint uses the same bearer API tokens as /api/v1. Create a token in Settings, then send it as an Authorization header. The token is pinned to one workspace, so a subscription can only ever receive events from the workspace whose token created it.

All four endpoints require the webhooks:write scope. Sampling is included in that scope because anyone who can subscribe can already receive the same payloads.

curl -X POST https://mailbase.example.com/api/hooks/subscribe \
  -H "Authorization: Bearer $MAILBASE_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"event":"email.clicked","targetUrl":"https://hooks.zapier.com/hooks/catch/123/abc/","client":"zapier"}'

Connect Zapier, Make, Or n8n

  • Create an API token in Settings with the webhooks:write scope, and keep it in the tool's credential store rather than in a step body.
  • Point the tool's subscribe action at POST /api/hooks/subscribe with the event and the tool's own catch URL as targetUrl, and store the returned id.
  • Point the unsubscribe action at DELETE /api/hooks/subscribe/{id} using that stored id.
  • Point the sample or list action at GET /api/hooks/sample?event=... so the field picker has data before the first real event arrives.
  • In n8n, a Webhook node's production URL is the targetUrl. In Make, use the custom webhook address. In Zapier, use the REST Hook subscribe and unsubscribe URLs.

Subscribable Events

One subscription watches exactly one event. Subscribe more than once to watch more than one.

EventFires when
email.sentEmail accepted by the provider.
email.deliveredEmail delivered by the provider.
email.openedHuman open recorded.
email.clickedHuman click recorded.
email.bouncedBounce recorded.
email.complainedComplaint recorded.
email.unsubscribedUnsubscribe recorded.
reply.receivedInbound reply received.
audience.createdAudience or dynamic segment created.
campaign.launchedCampaign send launched.

Payloads And Signatures

Deliveries are POSTed as JSON with an envelope of id, type, created_at, workspace_id, and data. The Mailbase-Event, Mailbase-Delivery, Mailbase-Timestamp, and Mailbase-Signature headers accompany every request. The signature is an HMAC-SHA256 of the timestamp, a dot, and the raw body, using the signing secret returned once when the subscription was created.

GET /api/hooks/sample returns a bare JSON array. When the workspace has recent history for that event you get real envelopes; otherwise you get one synthetic envelope of the same shape, flagged with sample: true. The Mailbase-Sample-Source response header says which you received.

Lifecycle Rules

  • Subscribing twice with the same event and callback URL returns the existing subscription instead of creating a duplicate, so a retried call cannot double your deliveries.
  • A callback URL that answers 410 Gone is unsubscribed immediately and its endpoint is removed. This is how an automation deleted on the tool's side stops receiving traffic.
  • Deleting the endpoint in Settings also ends the subscription. The tool's next unsubscribe call then returns 404, which builders treat as already removed.
  • Each workspace can hold up to 40 hook subscriptions.

Callback URL Rules

Mailbase makes outbound requests to whatever callback URL you register, so the URL is validated before it is stored and the checks are deliberately strict.

  • https only. Plain http, and any other scheme, is rejected.
  • No credentials in the URL, and no privileged port other than 443.
  • No literal address inside a private, loopback, link-local, carrier-grade NAT, multicast, or reserved range, including the IPv6 and IPv4-in-IPv6 spellings of those ranges.
  • No localhost, no single-label hostname, and no local-only suffix such as .local or .internal.
  • The hostname is resolved when you subscribe and rejected if any answer falls inside a non-public range, so a public name pointed at an internal address is refused too.

Related Docs

OperationsUpdated 2026-05-25
Cron setup
Configure the recurring Mailbase cron endpoints that enqueue scheduled campaigns, process durable send-job batches, and run due workflow steps.
ComplianceUpdated 2026-05-25
Unsubscribe compliance
How Mailbase signs unsubscribe links, enforces suppression states, adds List-Unsubscribe headers, and keeps marketing sends compliant.
Developer APIUpdated 2026-05-25
API tokens
Create, scope, rotate, and verify Mailbase API tokens for workspace-safe backend integrations.
DeliverabilityUpdated 2026-05-25
Sender domains
Connect sender domains, understand hosted versus BYO useSend sending, and keep SPF, DKIM, and DMARC status visible in Mailbase.
MCPUpdated 2026-05-25
MCP OAuth
Connect Claude, Cursor, Codex, or another MCP client to Mailbase with OAuth-scoped workspace access.
Mailbase
Product
FeaturesPricinguseSend integrationChangelog
Learn
BlogDocsAPI referenceResources
Compare
ComparisonsAlternatives
Guides
Transactional email servicesSelf-hosted useSend stackSelf-hosted email marketingSPF, DKIM & DMARCEmail deliverability
Legal
TermsPrivacy
© 2026 Mailbase · french-webEmail workflow for builders.