Short answer: Drop the "Mailjet → Mailjet Send Email" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
From Email fromEmail | Required | From Email | |
From Name fromName | string | Optional | From Name |
To Email toEmail | Required | To Email | |
To Name toName | string | Optional | To Name |
Subject subject | string | Required | Message subject line. |
HTML Body htmlBody | html | Required | HTML Body |
{"fromEmail": "{{trigger.from}}","fromName": "{{trigger.fromName}}","toEmail": "{{trigger.from}}","toName": "{{trigger.toName}}","subject": "e.g. Quick update"}
{"Messages": [{"To": [{"Email": "recipient@example.com","MessageID": 123456}],"Status": "success"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.