Reference · Tools

Mailjet Trigger

Starts workflow when Mailjet email events occur via webhooks

Webhook trigger Marketing v1

The Mailjet Trigger fires on the email event type you select — blocked, bounce, open, sent, spam or unsub — splitting Mailjet's batched event array so each event becomes its own item with type, timestamp, message ID and email address. A typical build is suppressing an address after a hard bounce or spam complaint.

Node type
Webhook trigger
Parameters
1
Outputs
Output
Credentials
Mailjet Email

Mailjet Trigger

Triggers on Mailjet email events such as sent, opened, clicked, bounced, spam, and unsubscribed

Overview

Receives webhook notifications from Mailjet when email delivery events occur, such as messages sent, opened, clicked, bounced, marked as spam, blocked, or unsubscribed. Mailjet sends POST requests to the registered callback URL with an array of event objects containing the event type, timestamp, message ID, and recipient email. The trigger registers itself with Mailjet’s Event Callback URL API (POST /v3/rest/eventcallbackurl) for the selected event type. Useful for tracking email delivery, monitoring bounces and spam reports, automating re-engagement workflows on opens/clicks, and handling unsubscribe events. Authenticates via HTTP Basic Auth using the Mailjet API Key and Secret Key. WARNING: Mailjet does not sign webhook payloads. Security relies on the secrecy of the registered callback URL. Do not commit it to public repos or share publicly.

Category: Marketing
Tool Name: mailjet_trigger
Version: 1

Appearance: Icon: lucide-Mail | Color: #0078ff

Node Type

Trigger — webhook (receives incoming HTTP callbacks)

Input / Output

DirectionPort(s)
InputNone (trigger node)
OutputOutput

Credentials

This tool requires Mailjet Email credentials. See the Credentials Guide for setup instructions.

Parameters

ParameterTypeRequiredDefaultDescription
EventoptionsYesopenWhich email event type to listen for. Determines which Mailjet event callback is registered.
Options: blocked (email.blocked), bounce (email.bounce), open (email.open), sent (email.sent), spam (email.spam), unsub (email.unsub)

Output Data

Mailjet posts an array of event objects, and each entry becomes its own output item. Every item carries three metadata fields plus the event’s own fields:

  • _trigger — always mailjet_webhook
  • _timestamp — ISO 8601 timestamp of when the request arrived
  • _webhookEvent — the Mailjet event name taken from the payload
  • event — the Mailjet event name
  • time — the Unix timestamp Mailjet recorded for the event
  • MessageID, Message_GUID — identifiers for the message the event belongs to
  • email — the recipient address
  • mj_campaign_id, mj_contact_id, customcampaign, CustomID, Payload — Mailjet campaign, contact and custom-tracking identifiers
  • ip, geo, agent, url — client and link details recorded for open and click events
  • blocked, hard_bounce, error_related_to, error — delivery failure details
  • source — the source Mailjet attributes the event to

Any other field Mailjet includes in the event is merged in alongside these. Reference the result downstream by expression, e.g. {{ $json.email }}.

Usage Examples

  • Start a workflow when an email is opened by a recipient
  • Trigger an alert when an email bounces in Mailjet
  • Automate unsubscribe handling when a recipient opts out
  • Log email delivery events for analytics and reporting

Example Configuration

Listen for message opens:

{
  "type": "mailjet_trigger",
  "parameters": {
    "event": "open"
  }
}

Listen for bounces so you can clean your list:

{
  "type": "mailjet_trigger",
  "parameters": {
    "event": "bounce"
  }
}

Listen for unsubscribes:

{
  "type": "mailjet_trigger",
  "parameters": {
    "event": "unsub"
  }
}

Trigger Behavior

  • Activation: When the workflow is activated, a webhook endpoint is registered with the service.
  • Deactivation: The webhook is automatically unregistered when the workflow is deactivated.
  • Payload: The incoming webhook payload is parsed and output as workflow items.
  • Verification: Supports signature verification where applicable.

Tips

Entry point that fires when Mailjet sends a webhook for the selected email event type. Configure which event to listen for: blocked, bounce, open, sent, spam, or unsub. Mailjet sends an array of event objects; each is output as a separate item with event type, timestamp, message ID, and email fields. WARNING: Mailjet does not sign webhook payloads. Security relies on the secrecy of the registered callback URL. Do not commit it to public repos or share publicly.

Frequently asked questions

Are the webhook payloads signed?

No. Mailjet does not sign webhook payloads, so security rests entirely on the secrecy of the registered callback URL. Do not commit it to a public repository or share it publicly.

How are batched events handled?

Mailjet sends an array of event objects and each becomes a separate output item, so the next node runs once per event rather than once per delivery.

What is on each item?

Event type, timestamp, message ID and the email address — enough to act on the event without an immediate follow-up lookup.

Can one trigger watch several event types?

It is configured with the event type to listen for, so use a separate trigger per event you need to handle differently.

Build with the Mailjet Trigger node

Drop it into a workflow, wire it to an agent, or call it on a schedule. You'll need Mailjet Email credentials first.

Open BusyBot

Last updated . Spotted something wrong? Tell us.