Menu

Mattering Automations Mailjet integration

Connect Mailjet to Mattering Automations: contacts, lists and custom properties, bulk and CSV import, segments, campaign drafts through send, statistics and raw event logs, templates, senders and domain verification, Event API webhooks and inbound parse routes as workflow steps, authenticated with your API key and secret key pair.

The Mattering Automations Mailjet integration puts 71 Mailjet nodes on your automation canvas: create and update contacts, manage contact lists and custom properties, run bulk writes and the two step CSV import, build and evaluate segments, assemble campaign drafts and take them through content, test, schedule and send, read sent campaigns and per message history, pull statistics and the raw open, click and bounce logs underneath them, manage templates and their bodies, register senders and verify sending domains, configure Event API webhooks, and set up inbound parse routes.

The credential is a two part key pair rather than a single token. Mailjet authenticates over HTTP Basic with the API Key as the username and the Secret Key as the password, and both halves are generated with your account and shown together in the Mailjet app. There is one global host, so nothing about the connection depends on a region, an environment or an account subdomain. Setup takes a few minutes, and this guide walks through each step and ends with the full node reference. Mailjet is part of Sinch.

One structural fact is worth knowing up front, because it explains why the catalog is broader than any single Mailjet reference page. Several Mailjet API generations are current at the same time and each endpoint belongs to exactly one of them: contacts, lists, campaigns, statistics, templates, senders, webhooks and parse routes sit on the v3 REST surface, the CSV upload sits on a separate v3 data plane that takes a raw text body, sending sits on v3.1, and contact deletion, which is a GDPR anonymization rather than a row removal, is the one v4 endpoint. Each node carries its own version, so nothing about this is a field you have to fill in. You connect one credential and the whole estate is reachable.

Before you start

  • A Mailjet account you can create API credentials in. The pair is shown in the Mailjet app under Account settings, then API Key Management.
  • At least one validated sender, if any of your workflows will send. Only a sender whose status is Active can be used in a send, and Mailjet: List Senders shows the status of each. Mailjet: Create Sender and Mailjet: Validate Sender cover the rest of that path from the canvas.
  • A Mailjet plan that covers what you intend to do. Check Mailjet's own pricing page for what your plan includes, including whether API access is part of it, and note that your account's sending quota is the ceiling a sending workflow will meet first. This guide quotes no plan figures, because plan contents move.
  • A Mattering workspace with access to the Automations app.
  • Not required and not stored here: a region, an environment name, or an account subdomain. Mailjet serves one global host, so the credential is the pair and nothing else.

Create a Mailjet API key pair

Mailjet authenticates with HTTP Basic rather than a bearer token: the API Key is the username and the Secret Key is the password, and both are sent on every request. That is why the credential form has two fields. Both halves are generated automatically with your account, so there is usually nothing to create, only somewhere to look.

Sign in to Mailjet and open Account settings, then API Key Management.
Copy the API Key and the Secret Key. The secret half is the one Mailjet hides behind a reveal control, so copy it carefully and check for leading or trailing whitespace.
There are no scopes to compose and no host to choose. The pair addresses the whole account against one global Mailjet host, which is what lets the connector run a fixed connection test with no configuration.
This pair can send mail. It reaches the five sending nodes as well as every read, and mail that has gone out cannot be recalled. If you are connecting Mailjet purely to report on campaigns, gate the sending nodes behind an approval step in your workflows rather than relying on the credential to stop them.

Connect Mailjet to Mattering

In Mattering Automations, open Connectors and click Add Connector.
Choose Mailjet from the list.
Click Create new credential, paste the API Key into API Key and the Secret Key into Secret Key, and save.
The credential is stored encrypted in Google Secret Manager and never appears in workflow logs.
Click Test Connection. Mattering calls Mailjet's sender list endpoint, which takes no parameters and needs no per account host, so a successful response proves the pair even on a brand new account. A 401 means one of the two halves is wrong: check that the API Key went into the first field and the Secret Key into the second, since swapping them fails the same way as mistyping either.
Click Connect. All 71 Mailjet nodes appear in your canvas palette.

Verify it works

After connecting, open any automation canvas and check the palette: a Mailjet section should list the read and action nodes. Drop Mailjet: List Senders onto the canvas and run a test step. It is the integration's natural probe: it needs no parameters, and it returns every address and domain registered on the key with its validation status. Note which senders come back Active, because those are the only addresses a send is allowed to use later.

Now read something with a shape to it. Drop Mailjet: List Contact Lists onto the canvas, set Limit to something larger than the default, and run the step. You get each list's id, name, subscriber count and magic list address. Two shapes to notice while you are here, because both trip people later. Mailjet's rows arrive inside a capital D Data array within the connector envelope's lowercase data, so a single row reads as data.Data[0].ID rather than data.id. And the Limit parameter defaults to 10 on every Mailjet lister, so an unraised limit truncates a real account silently, with nothing in the response to say it was cut short. Everything in this verify path is read only, so it cannot reach the 15 destructive nodes and is safe to re run whenever you rotate the key.

Node reference

71 nodes, generated from the connector itself so this reference always matches what ships.

Read and query nodes 35

Mailjet: Get Anonymized Contact

mailjet_get_anonymized_contact

Read back a contact after a GDPR deletion to confirm the anonymization landed: the address becomes a hashed @domain.invalid value and the name becomes Anonymized. Same endpoint as Mailjet: Get Contact, kept separate because it is the documented verification step of the deletion flow and takes the numeric id only.

Mailjet: Get CSV Import

mailjet_get_csv_import

Poll a CSV import job: Status moves through Upload and Parse to Completed, Count is the rows processed and Errcount the rows that failed. A non-zero Errcount means part of the file did not land.

Mailjet: Get Campaign

mailjet_get_campaign

Fetch one campaign by id, or by the mj.nl=<draft id> form that resolves a campaign draft to the campaign it produced. That second form is how a workflow that created and sent a draft finds the campaign id its statistics live under.

Mailjet: Get Campaign Draft

mailjet_get_campaign_draft

Fetch one campaign draft, including its Status: the field that says whether it is still editable, programmed for a future send, or already delivered. Check this before any send or schedule call.

Mailjet: Get Campaign Draft Content

mailjet_get_campaign_draft_content

Read the HTML and plain-text bodies stored on a campaign draft, plus its MJML source when the draft was built that way. Note the property names carry hyphens: Html-part and Text-part.

Mailjet: Get Contact

mailjet_get_contact

Fetch one contact by numeric id or by email address. This is how you turn an address into the contact id every other contact node wants. The row still arrives inside the standard envelope, so read it at data.Data[0].

Mailjet: Get Contact List

mailjet_get_contact_list

Fetch one contact list: name, subscriber count, creation date, and the magic-list Address that lets Send API mail the whole list by writing to <address>@lists.mailjet.com.

Mailjet: Get Contact Lists

mailjet_get_contact_lists

List the contact lists one contact belongs to, with the subscription date and whether the contact has unsubscribed from each. IsUnsub true means they are still on the list but opted out, which is not the same as not being a member.

Mailjet: Get Domain

mailjet_get_domain

Fetch one sender domain by id or by domain name: the exact DKIM record name and value, the SPF value, the ownership token, and when each was last checked.

Mailjet: Get Geo Statistics

mailjet_get_geo_statistics

Opens and clicks grouped by the recipient's country, optionally narrowed to one campaign. Lifetime figures, not a time series.

Mailjet: Get Link Click Statistics

mailjet_get_link_click_statistics

Total and unique clicks for each URL in one campaign's email, with the link's position in the body. These are lifetime figures for the campaign, not a time series: re-fetch rather than trying to add them across periods.

Mailjet: Get List Many Contacts Job

mailjet_get_list_many_contacts_job

Poll an asynchronous list subscription job until its Status is Completed. Needs both the list id the job was started on and the JobID it returned.

Mailjet: Get Many Contacts Job

mailjet_get_many_contacts_job

Poll an asynchronous bulk contact job until its Status is Completed, and read how many rows it processed. A non-empty ErrorFile means some rows failed and names where the detail is.

Mailjet: Get Message

mailjet_get_message

Fetch one sent message by id: its current status (queued, sent, opened, clicked, bounced, spam), arrival time, attempt count and the campaign and contact it belongs to.

Mailjet: Get Message History

mailjet_get_message_history

List every event recorded against one message in order: sent, opened, clicked, bounced, unsub, with the Unix timestamp of each. This is the per-message audit trail behind the aggregate statistics.

Mailjet: Get Recipient ESP Statistics

mailjet_get_recipient_esp_statistics

Delivery and engagement for one campaign broken down by the recipient's mailbox provider, which is how you tell a provider-specific deliverability problem from a content one. The row carries real RATE columns (OpenRate, ClickThroughRate, the bounce and spam rates) alongside the counts: rates are per-provider ratios and must never be added together.

Mailjet: Get Stat Counters

mailjet_get_stat_counters

The account's main statistics endpoint: delivery and engagement counters for one campaign, one list, or the whole API key, either as a lifetime total or as a time series. CounterTiming decides what a bucket MEANS, and the choice matters: Event buckets by when the open or click happened and stops changing once the day is past, while Message buckets by send time and keeps being revised as engagement arrives days later. Mailjet documents two response shapes for this one endpoint, so read rows from data.Data or, on sub-lifetime resolutions, from data.StatCounters.Data.

Mailjet: Get Template

mailjet_get_template

Fetch one template's metadata: name, description, author, editor mode and intended purpose. The body itself lives on a separate resource, Mailjet: Get Template Content.

Mailjet: Get Template Content

mailjet_get_template_content

Read a template's stored HTML and plain-text bodies, its MJML source, and its Headers object of default From, Subject and Reply-To values. Note the hyphenated property names: Html-part and Text-part.

Mailjet: List Bounce Events

mailjet_list_bounce_events

The raw bounce log: one row per bounce with its timestamp, campaign and contact, whether the address was blocked, and whether the failure is permanent. Permanent bounces are the addresses to stop mailing; retrying them is how a sending reputation gets damaged.

Mailjet: List Campaign Drafts

mailjet_list_campaign_drafts

List the marketing campaign drafts on the account with their titles, subjects, sender, audience list and status. The draft id from here feeds the content, test, send and schedule nodes.

Mailjet: List Campaigns

mailjet_list_campaigns

List the campaigns that have actually been sent, marketing and transactional alike. A campaign here is the delivery record, distinct from the campaign DRAFT that produced it; the campaign id is what the statistics nodes take.

Mailjet: List Click Events

mailjet_list_click_events

The raw click-event log: one row per click with the URL, the timestamp, the delay between send and click, and the campaign and contact. Defaults to today; widen it with FromTS and ToTS.

Mailjet: List Contact Lists

mailjet_list_contact_lists

List the contact lists on the account with their ids, names, subscriber counts and magic-list addresses. The list id from here feeds every list-scoped node and every campaign recipient field.

Mailjet: List Contact Properties

mailjet_list_contact_properties

List the custom contact properties defined on the account with their datatypes. These are the names usable in contact Properties objects, in segment expressions, and in campaign personalization.

Mailjet: List Contact Statistics

mailjet_list_contact_statistics

Per-contact lifetime engagement: how many messages each contact was delivered, opened, clicked, bounced or complained about, and when they were last active. Useful for building an engaged-recipients segment or pruning dead addresses.

Mailjet: List Contacts

mailjet_list_contacts

List the contacts on the account with their ids, addresses, delivery counts and exclusion state. Pages of 10 by default and a maximum of 1000, so a large account is read by walking Offset. Rows come back under data.Data.

Mailjet: List Domains

mailjet_list_domains

List the sender domains on the account with their SPF and DKIM records and current verification status. The record values here are what has to be published in DNS before Mailjet will treat the domain as authenticated.

Mailjet: List Event Callbacks

mailjet_list_event_callbacks

List the Event API webhooks configured on the account: which URL receives which event type, at which payload version. Version 2 is the grouped format that batches several events into one POST.

Mailjet: List Messages

mailjet_list_messages

List sent messages with their delivery status, campaign and contact. Filter by the CustomID a send attached, or by ContactAlt to find every message sent to one address. This is how a transactional workflow answers did that email arrive without standing up a webhook.

Mailjet: List Open Events

mailjet_list_open_events

The raw open-event log: one row per open with its timestamp, campaign, contact and user agent. Defaults to today; pass FromTS and ToTS to widen the window. This is the pull equivalent of the open webhook, for workflows that cannot host a receiver.

Mailjet: List Parse Routes

mailjet_list_parse_routes

List the inbound Parse API routes on the account: each maps an address to a webhook URL that receives the parsed email as JSON. This is the mechanism behind reply capture.

Mailjet: List Segments

mailjet_list_segments

List the segments (contact filters) on the account with the expression each one evaluates. A segment id narrows a campaign draft's audience without creating a second list. Status used means at least one campaign references it.

Mailjet: List Senders

mailjet_list_senders

List the email addresses and domains registered as senders on this API key, with their validation status. Only an Active sender may be used in a send, so this is both the credential health check to run first in any Mailjet automation and the source of every sender picker. Rows come back under data.Data.

Mailjet: List Templates

mailjet_list_templates

List email templates. OwnerType user returns the account's own templates, which are the editable ones; the default includes Mailjet's shared gallery. The template id feeds both the Send API TemplateID property and campaign drafts.

Action nodes 36

Mailjet: Add Contact To List

mailjet_add_contact_to_list

Create a contact and subscribe it to one list in a single call, setting its custom properties at the same time. This is the everyday signup path. Action addforce also clears a previous unsubscribe; addnoforce respects it; remove and unsub take the contact off or opt it out. Property names must already exist on the account.

Mailjet: Check Domain

mailjet_check_domain

Run Mailjet's SPF and DKIM verification against a sender domain right now instead of waiting for the periodic check. Returns the values currently published in DNS alongside any errors, so a failing domain says what is actually there rather than only that it is wrong. Changes no configuration.

Mailjet: Create CSV Import

mailjet_create_csv_import

DESTRUCTIVE: start the bulk import of a staged CSV. It writes contacts and property values at file scale with no undo, and the Method decides how brutal it is: addforce clears existing unsubscribes, remove and unsub strip or opt out everyone in the file, and excludemarketing suppresses every listed address from ALL marketing on the account. Returns a job row; poll it with Mailjet: Get CSV Import.

Mailjet: Create Campaign Draft

mailjet_create_campaign_draft

Create a marketing campaign draft: who it comes from, what the subject line is, and which list (optionally narrowed by a segment) it will reach. This creates the shell only and sends nothing. Add a body with Mailjet: Set Campaign Draft Content, then send or schedule it.

Mailjet: Create Contact

mailjet_create_contact

Create a contact from an email address. This creates the contact on the ACCOUNT only; it does not subscribe it to anything. Use Mailjet: Manage Contact Lists or Mailjet: Add Contact To List afterwards. Reversible with Mailjet: Delete Contact.

Mailjet: Create Contact List

mailjet_create_contact_list

Create a contact list. Only a name is required; Mailjet assigns the id and the magic-list address. Reversible with Mailjet: Delete Contact List.

Mailjet: Create Contact Property

mailjet_create_contact_property

Define a new custom contact property. It has to exist before any contact can carry a value for it, so this is the first step of any personalization or segmentation work. Reversible with Mailjet: Delete Contact Property.

Mailjet: Create Event Callback

mailjet_create_event_callback

Point an Event API webhook at your endpoint so Mailjet POSTs delivery and engagement events as they happen. One callback per event type, or use the all event type to receive every kind. Version 2 groups several events into one POST, which is what a high-volume receiver wants. Reversible with Mailjet: Delete Event Callback.

Mailjet: Create Parse Route

mailjet_create_parse_route

Create an inbound parse route. Supply only the URL and Mailjet generates an address on parse-in1.mailjet.com to forward mail to; supply an address on a domain you have already pointed at Mailjet with an MX record to use your own. Mail arriving at that address is POSTed to the URL as JSON with headers, parts and attachments. Point a campaign's Reply-To at it to capture replies.

Mailjet: Create Segment

mailjet_create_segment

Create a segment from a filter expression over contact properties, for example age>40 or country="US" AND age>30. Expressions combine property comparisons with AND, OR and NOT; every property named must already be defined. The segment is then attached to a campaign draft through its SegmentationID.

Mailjet: Create Sender

mailjet_create_sender

Register an email address, or a whole domain with the *@ form, as a sender on this API key. The new sender starts Inactive: Mailjet emails a confirmation link, or you can prove ownership with a DNS TXT record or a file at the domain root and then call Mailjet: Validate Sender. Nothing can be sent from it until it is Active.

Mailjet: Create Template

mailjet_create_template

Create a template. This creates the metadata shell only and the template has no body until Mailjet: Set Template Content runs against the returned id. Reversible with Mailjet: Delete Template.

Mailjet: Delete Contact

mailjet_delete_contact

DESTRUCTIVE and irreversible: the GDPR contact deletion. Mailjet anonymizes the contact rather than removing the row, replacing the address with a hashed @domain.invalid value and the name with Anonymized, and strips its personal data everywhere on the account. The original address cannot be recovered, and re-adding it creates a NEW contact with no history. This node is the one call in the connector that goes to the v4 API, and it takes the numeric contact id only, never an email.

Mailjet: Delete Contact List

mailjet_delete_contact_list

DESTRUCTIVE: delete a contact list. The contacts themselves survive on the account, but the list, its membership and its campaign associations are gone, and any campaign draft pointing at it loses its audience. There is no undo from here; the reversible alternative is Mailjet: Update Contact List with IsDeleted true, which soft-deletes instead.

Mailjet: Delete Contact Property

mailjet_delete_contact_property

DESTRUCTIVE: delete a custom contact property definition. Every contact's stored value for it goes with it, and any segment expression or campaign personalization referencing the name stops resolving. Recreating the property does not bring the values back.

Mailjet: Delete Event Callback

mailjet_delete_event_callback

DESTRUCTIVE: remove an Event API webhook. Mailjet stops delivering that event type immediately and does NOT replay the events that occur while no callback exists, so whatever happens in the gap is lost rather than delayed.

Mailjet: Delete Parse Route

mailjet_delete_parse_route

DESTRUCTIVE: delete an inbound parse route. Mail sent to that address stops being forwarded to your webhook, and a Mailjet-generated address is not reissued, so any campaign whose Reply-To points at it silently loses its replies.

Mailjet: Delete Segment

mailjet_delete_segment

DESTRUCTIVE: delete a segment. The expression is gone and any campaign draft pointing at it loses its audience narrowing, which means the next send reaches the WHOLE list rather than failing. The reversible alternative is Mailjet: Update Segment with Status deleted.

Mailjet: Delete Template

mailjet_delete_template

DESTRUCTIVE: delete a template and its stored body. Any send or campaign draft still referencing the id starts failing with error send-0010, and the content cannot be recovered.

Mailjet: Manage Contact Lists

mailjet_manage_contact_lists

Subscribe or unsubscribe ONE contact across several lists in a single call. Each entry names a list id and an action: addforce adds and clears any previous unsubscribe, addnoforce adds but leaves an existing unsubscribe standing, remove takes the contact off the list, and unsub marks it unsubscribed while keeping the membership row.

Mailjet: Manage List Many Contacts

mailjet_manage_list_many_contacts

DESTRUCTIVE: apply one subscription action to many contacts on one list at once, creating any that do not exist. It OVERWRITES the properties it is given at whatever scale the payload has with no undo, and Action remove or unsub strips or opts out every contact in the payload in one shot. Runs asynchronously and returns a JobID; poll it with Mailjet: Get List Many Contacts Job.

Mailjet: Manage Many Contacts

mailjet_manage_many_contacts

DESTRUCTIVE: create or update many contacts at once and, optionally, apply list actions to all of them. It OVERWRITES the properties it is given on contacts that already exist, at whatever scale the payload has, with no undo, and setting IsExcludedFromCampaigns true here suppresses every listed contact from all marketing on the account. Runs asynchronously and returns a JobID; poll it with Mailjet: Get Many Contacts Job.

Mailjet: Schedule Campaign Draft

mailjet_schedule_campaign_draft

DESTRUCTIVE: schedule the campaign to go out at a future date. Flagged the same as an immediate send because it reaches real people with no second approval, and this connector ships no unschedule node, so from here it is a one-way door: cancelling means going into the Mailjet interface. The draft's Status becomes programmed.

Mailjet: Send Campaign Draft

mailjet_send_campaign_draft

DESTRUCTIVE and irreversible: send the campaign to its entire audience list right now. Every contact on the list, minus any segment narrowing and the exclusion list, receives real email within minutes and there is no recall. Confirm the audience and the body before wiring this into anything automatic.

Mailjet: Send Campaign Email

mailjet_send_email

DESTRUCTIVE: send one campaign email through Mailjet. Real mail to a real inbox, no recall. Uniform ESP contract: the same params and the same result envelope as the Postmark, Mailgun and SMTP campaign-send nodes, so a caller does not branch on provider. Returns {ok, provider, provider_message_id} or {ok: false, error, detail, retryable}, with a send failure arriving as HTTP 200 and ok false rather than as a transport error. Exactly one recipient per call; from_email must be a validated Mailjet sender or the send is refused with send-0008. headers are passed through verbatim, which is how compliance headers such as List-Unsubscribe arrive, and metadata is carried as the message's EventPayload.

Mailjet: Send Message

mailjet_send_message

DESTRUCTIVE: send transactional email through Send API v3.1. It delivers real mail to real inboxes and there is no recall, which is why it is flagged destructive even though it deletes nothing. Set SandboxMode true to have Mailjet validate the payload and return the normal response without delivering anything. Up to 50 recipients across To, Cc and Bcc per message, and several messages per call. Read results at data.Messages[]: a call can return HTTP 200 with some messages succeeded and others carrying Status error, so check per message rather than trusting the status code. For campaign sending with a uniform cross-provider contract, use Mailjet: Send Campaign Email instead.

Mailjet: Set Campaign Draft Content

mailjet_set_campaign_draft_content

Set the body of a campaign draft. Supply HTML, plain text, or both. Updating the MJML source does NOT regenerate the HTML automatically, so a draft edited that way needs its HTML written too or it goes out with the old body.

Mailjet: Set Template Content

mailjet_set_template_content

Set a template's body, and optionally its default From, Subject and Reply-To through the Headers object, so a send using the template does not have to repeat them. Anything the send supplies overrides these defaults. Storing MJML does not regenerate the HTML, so write html_part too.

Mailjet: Test Campaign Draft

mailjet_test_campaign_draft

DESTRUCTIVE: send a preview of the campaign to the named test recipients. It is called a test, but it puts real email in real inboxes and cannot be recalled, so it is flagged the same as any other send. The campaign itself stays a draft.

Mailjet: Update Campaign Draft

mailjet_update_campaign_draft

Change a campaign draft's subject, sender, audience list or segment. Blank fields are left alone, since Mailjet treats every PUT as a partial update. Only drafts that have not been sent can be changed.

Mailjet: Update Contact

mailjet_update_contact

Update a contact's name or exclusion state. Mailjet treats every PUT as a partial update, so fields you leave blank keep their current values rather than being cleared. Setting IsExcludedFromCampaigns true is the documented way to add someone to the exclusion list; it suppresses them from ALL marketing on the account, not just one list.

Mailjet: Update Contact Data

mailjet_update_contact_data

Set the custom property values on one contact: the fields campaign personalization reads. Every property named here must already be defined on the account with Mailjet: Create Contact Property, otherwise the call is refused with Property not defined.

Mailjet: Update Contact List

mailjet_update_contact_list

Rename a list, or flip its deleted flag. Mailjet treats every PUT as a partial update, so blank fields are left alone. Setting IsDeleted false is how a soft-deleted list is brought back.

Mailjet: Update Segment

mailjet_update_segment

Change a segment's name, expression or description. Blank fields are left alone, since Mailjet treats every PUT as a partial update. Editing the expression changes who a campaign using this segment will reach, so check which drafts reference it first.

Mailjet: Upload CSV Data

mailjet_upload_csv_data

Upload CSV contact data against a list and get back a data id. This stages the file only; nothing is imported until Mailjet: Create CSV Import runs against the returned id. The first CSV row is the header and must contain an email column; other columns must match existing contact property names. Read the id at data.ID, which is NOT the usual envelope.

Mailjet: Validate Sender

mailjet_validate_sender

Ask Mailjet to re-check a pending sender's ownership proof (the TXT record or the file at the domain root) and activate it if the proof is in place. Returns the per-method errors when it is not, which is what tells you whether the DNS record or the file is the missing half.

Using the integration

On the automation canvas

Mailjet nodes chain with every other node. A form submission can become a subscriber with Mailjet: Add Contact To List, a weekly schedule can read Mailjet: Get Stat Counters into a Mattering database and open a task when engagement drifts, and Mailjet: Check Domain can verify your sending domains on a timer instead of waiting for Mailjet's periodic check. Two values do most of the wiring: the contact list id from Mailjet: List Contact Lists, which every list scoped node wants, and the campaign draft id from Mailjet: List Campaign Drafts, which feeds the content, test, schedule and send nodes in order.

From AI assistants over MCP

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and Matter, the assistant built into the platform, can drive the same surface. An agent can answer questions about a campaign with Mailjet: Get Stat Counters and Mailjet: Get Recipient ESP Statistics, look someone up with Mailjet: Get Contact, and subscribe a new signup with Mailjet: Add Contact To List. The read nodes plus the contact nodes are the comfortable surface to hand an agent. Keep the five sending nodes and the bulk writers behind conditions or approval steps. Worth knowing when you compare options: Mailjet's published documentation, guides and official client library list mention no MCP server of its own. It ships REST wrappers for PHP, Python, Node.js, Java, .NET, Go and Ruby and nothing MCP shaped, so there is no first party server here to weigh this integration against. What this one adds beyond a chat session is that the same nodes run on a schedule or from a trigger with nobody present, chain with every other connector in one workflow, hold the credential once in a shared workspace rather than in an individual's local config, and carry destructive flags you can gate on.

Contacts, lists, and the difference between them

A Mailjet contact belongs to the account; a subscription belongs to a list. Mailjet: Create Contact creates the contact only and subscribes it to nothing, which surprises people who expect a signup. Mailjet: Add Contact To List is the everyday path: it creates the contact and subscribes it to one list in a single call, with custom properties set at the same time. Mailjet: Manage Contact Lists handles one contact across several lists at once, each with its own action, and Mailjet: Get Contact Lists reads the reverse direction, showing which lists a contact is on and whether they have unsubscribed from each. Custom properties are their own resource: define them with Mailjet: Create Contact Property before any contact can carry a value, then write values with Mailjet: Update Contact Data. One behaviour that saves a lot of confusion: Mailjet treats every update as a partial update, so a field you leave blank keeps its current value rather than being cleared.

Bulk writes and the two step CSV import

Loading a list is not one call, and assuming it is is the most common way this surface goes wrong. Mailjet: Upload CSV Data stages the file against a list and returns a data id, with no import happening yet, and Mailjet: Create CSV Import is what actually starts the write against that id. Mailjet: Get CSV Import then polls the job: the status moves through Upload and Parse to Completed, the count is the rows processed, and a non zero error count means part of the file did not land, so check it rather than trusting the status alone. Mailjet: Manage Many Contacts and Mailjet: Manage List Many Contacts are the JSON equivalents for smaller batches, each returning a job id that Mailjet: Get Many Contacts Job and Mailjet: Get List Many Contacts Job poll. All three writers are flagged destructive on purpose: they overwrite the properties they are given at whatever scale the payload sets, and their available actions include ones that unsubscribe or suppress addresses account wide. One shape to watch when you build the import: the import options field is a JSON string rather than a nested object, which is the one place in the API where that is true.

Campaign drafts, and where to put the human

The draft life cycle is four nodes in order. Mailjet: Create Campaign Draft makes the shell with its sender, subject and audience list, optionally narrowed by a segment. Mailjet: Set Campaign Draft Content puts the HTML and plain text bodies on it. Mailjet: Get Campaign Draft reads back the status that says whether the draft is still editable, programmed for a future send, or already delivered, which is the field to check before anything acts on it. Then the send. Mailjet: Send Campaign Draft mails the entire audience list right now and cannot be recalled. Mailjet: Schedule Campaign Draft carries the same destructive flag, for two reasons: it reaches real people with no second approval, and this connector ships no node to unschedule a campaign, so from the canvas it is a one way door. Mailjet: Test Campaign Draft is called a test by the API and still puts real mail in real inboxes. Assembling drafts is safe work for an automation or an agent; the send is where an approval task belongs. One editing trap worth knowing: updating a draft's MJML source does not regenerate its HTML, so a draft edited that way goes out with the old body unless the HTML is written too.

Statistics, and which numbers can be added up

Mailjet: Get Stat Counters is the main statistics read: delivery and engagement counters for one campaign, one contact list, or the whole API key, either as a lifetime total or as a time series. Two settings on it change what the numbers mean. The counter resolution decides the shape of the response, and a lifetime request returns one undated row rather than a series, so a scheduled report wants a day resolution. The counter timing decides which day a number lands on: bucketing by event means a partition stops changing once the day is past, while bucketing by send time means it keeps being revised as engagement arrives days later, so stable history wants event timing. The counters themselves are all additive. The rates are not published by this endpoint at all: Mailjet's guides tell you to compute open rate and click rate from the counts, which is the correct arrangement, because summing a numerator and a denominator separately is right where averaging daily rates is wrong. Mailjet: Get Recipient ESP Statistics does publish real rate columns per mailbox provider, and those must never be summed; re fetch them instead. Underneath all of it, Mailjet: List Open Events, Mailjet: List Click Events and Mailjet: List Bounce Events are the raw logs, one row per event, defaulting to today until you widen the timestamps.

Webhooks and inbound parse routes

Mailjet pushes delivery and engagement events to a URL through its Event API. Mailjet: Create Event Callback registers one, Mailjet: List Event Callbacks shows which URL receives which event type at which payload version, and Mailjet: Delete Event Callback removes one. The delete is flagged destructive for a specific reason rather than a general one: Mailjet stops delivering that event type immediately and does not replay what happened while no callback existed, so events during the gap are lost rather than delayed. Inbound mail is the mirror image. Mailjet: Create Parse Route maps an address to a webhook URL that receives parsed incoming email as JSON, which is the mechanism behind reply capture, and Mailjet: List Parse Routes and Mailjet: Delete Parse Route manage the set. Supply only a URL and Mailjet generates the address for you; supply an address on a domain you already control and it uses that instead. Note that a Mailjet generated address is not reissued after a delete, so a campaign whose reply address pointed at it silently loses its replies.

The 15 destructive nodes, gated

Five send mail and cannot be recalled: Mailjet: Send Message, Mailjet: Send Campaign Email, Mailjet: Send Campaign Draft, Mailjet: Schedule Campaign Draft and Mailjet: Test Campaign Draft. Three write contacts at file scale with actions that can suppress addresses account wide: Mailjet: Manage Many Contacts, Mailjet: Manage List Many Contacts and Mailjet: Create CSV Import. Seven delete, and each takes something specific with it. Mailjet: Delete Contact is the GDPR deletion: it anonymizes rather than removes, replacing the address with a hashed value that cannot be recovered, and re adding the address later creates a fresh contact with no history. Mailjet: Delete Contact Property takes every contact's stored value for that property with it. Mailjet: Delete Segment removes the expression, which means the next send from a draft that pointed at it reaches the whole list instead of the narrowed audience. Mailjet: Delete Template makes any send still referencing it start failing. Mailjet: Delete Contact List, Mailjet: Delete Event Callback and Mailjet: Delete Parse Route are covered above. The pattern for all fifteen is the same: put them behind a condition or an approval task rather than a bare trigger, and prefer the reversible neighbour where one exists, for example unsubscribing a contact rather than deleting it.

Troubleshooting

Test Connection fails with a 401
The pair is wrong, or the two halves are in the wrong fields. Mailjet authenticates with HTTP Basic where the API Key is the username and the Secret Key is the password, so swapping them fails exactly like mistyping either one. Re open Account settings, then API Key Management in Mailjet, copy both values again, and check for leading or trailing whitespace from the copy. Two Mailjet error codes distinguish the causes if you see the body: mj-0015 means no valid authorization credentials were supplied, and mj-0001 means the key itself is suspended, which is an account state rather than a typo.
A send reported success but no mail arrived
Read the response body rather than the status code. A Mailjet send failure arrives as an HTTP 200: the message that failed validation comes back inside a 2xx response with a status of error and an errors array on it, and one bulk call can carry successes and failures together. Anything that treats 2xx as proof of delivery will report mail as sent that Mailjet never accepted. Add a condition on the per message status after Mailjet: Send Message, or use Mailjet: Send Campaign Email, which classifies per message rather than per status code for exactly this reason. To confirm what actually happened to a specific message afterwards, Mailjet: Get Message returns its current delivery state and Mailjet: Get Message History returns the full event trail.
A send fails with a 403 and the credential is definitely correct
On the Send API a 403 is usually a sender configuration fault rather than an authentication fault, which is the opposite of what the status code suggests. The send-0006, send-0007 and send-0008 codes mean the From address is not permitted, not validated, or not authorized on this key, and retrying reproduces them forever. Run Mailjet: List Senders and check the status of the address you are sending from: only an Active sender can send. If it is missing or inactive, register it with Mailjet: Create Sender and complete the proof with Mailjet: Validate Sender, or verify the whole domain with Mailjet: Check Domain. A genuine credential failure shows up as a 401 instead.
A list read only returned ten rows
Mailjet's pagination Limit defaults to 10 on every list endpoint, and nothing in the response says the result was cut short. That is small enough to truncate almost any real account, and it also truncates a statistics window longer than ten slices, which is the version of this that looks like missing data rather than missing rows. Set Limit explicitly on every lister, up to Mailjet's maximum of 1000, and page past that with Offset. The connector already raises the limit on the pickers that populate node dropdowns, so a dropdown showing your data does not prove your own lister node is set correctly.
A template path reading a list of rows resolves to nothing
Mailjet nests its rows one level deeper than most APIs, and the capital letter matters. Every v3 read returns a uniform envelope with a capital D Data array inside the connector envelope's lowercase data, and a single object read still comes back as a one element array. So a row's id is at data.Data[0].ID and a list of addresses is at data.Data[].Email. Two documented exceptions are worth knowing before you write a path against them. The statistics counters move a level down when the resolution asks for a time series, so the rows are at data.Data or at data.StatCounters.Data depending on the request. And the CSV upload returns a bare object with an ID and no envelope at all.
An update cleared fields I did not mean to change, or failed to clear one I did
Mailjet treats every update as a partial update, so omitted properties are preserved rather than cleared, and this connector relies on that: optional fields you leave blank are omitted from the request rather than sent as empty. That means an update node cannot blank a field by leaving it empty, which is the direction people usually hit first. The bulk writers behave differently and more sharply: Mailjet: Manage Many Contacts and Mailjet: Manage List Many Contacts overwrite the properties they are given on contacts that already exist, at whatever scale the payload sets, which is part of why they are flagged destructive.
A campaign or template went out with the old content
Updating the MJML source does not regenerate the HTML. Mailjet states this explicitly, and it applies to both campaign drafts and templates: a draft or template edited only through its MJML property still sends the previously stored HTML body. Write the HTML too, in the same step, with Mailjet: Set Campaign Draft Content or Mailjet: Set Template Content, and read it back with Mailjet: Get Campaign Draft Content or Mailjet: Get Template Content before anything sends. Note that the underlying property names carry hyphens, which canvas fields cannot, so the node fields are spelled with underscores and renamed on the way out.
Contacts vanished from a segment or a campaign reached more people than expected
Check whether the segment still exists. Mailjet: Delete Segment is flagged destructive for exactly this outcome: the expression is gone, and any campaign draft that pointed at it loses its audience narrowing, so the next send reaches the whole list rather than the intended slice. Re create the expression with Mailjet: Create Segment and re attach it to the draft with Mailjet: Update Campaign Draft, and read the draft back with Mailjet: Get Campaign Draft before sending. The same class of surprise applies to Mailjet: Delete Contact Property: deleting a property definition takes every contact's stored value with it, so any segment expression or personalization referencing that property stops behaving as written.
Events stopped arriving at our webhook and did not catch up
They will not catch up. Mailjet does not replay events that occurred while no callback existed, so a deleted or misconfigured Event API webhook loses that window rather than delaying it, which is why Mailjet: Delete Event Callback is flagged destructive. Run Mailjet: List Event Callbacks and check that a callback exists for each event type you expect and points at the right URL and payload version. Re register the missing ones with Mailjet: Create Event Callback. To reconstruct what happened during the gap, the raw logs are still readable: Mailjet: List Open Events, Mailjet: List Click Events and Mailjet: List Bounce Events take a timestamp window, and Mailjet: Get Message History gives the full trail for one message.
A deleted contact came back as an unfamiliar address
That is the documented behaviour rather than a fault. Mailjet: Delete Contact is a GDPR deletion on Mailjet's v4 surface: it anonymizes the contact instead of removing the row, replacing the address with a hashed value and the name with a placeholder. Mailjet: Get Anonymized Contact reads the record back so a workflow can confirm the anonymization landed. Nothing recovers the original address, and re adding it later creates a new contact with no history, so treat this node as unrecoverable and gate it behind an approval. If the intent was to stop mailing someone rather than to erase them, unsubscribing through Mailjet: Manage Contact Lists is the reversible alternative.

Mailjet is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.

Start Free Explore our Products