Automation & No-code

Connect Mailgrid to every no-code workflow tool without writing a single line of code.

Every integration below authenticates with your mb_live_… API key. Set it once in the platform's credential store; all subsequent steps reference it by name.

Zapier

The official Mailgrid Zapier app lives at integrations/zapier/ and is published as the @mailgrid/zapier npm package that powers the Zapier CLI app bundle.

Available actions & triggers

Step-by-step setup

1. In Zapier, click + Create Zap and search for Mailgrid in the app browser.
2. When prompted to connect an account, paste your mb_live_… key into the API Key field and click Yes, Continue.
3. Choose an action (Send Email or Schedule Email) and map the fields from your trigger step.
4. Click Test & Review — Zapier sends a live test email and confirms a 200 OK response.
5. Turn the Zap on.

Example Zap: Typeform → welcome email

Trigger: New Typeform response (form: "Sign-up")
Action: Mailgrid — Send Email

# Trigger output (from Typeform step)
# {{email}}   → respondent's email
# {{name}}    → respondent's first name

from:    "hello@yourdomain.com"
to:      "{{email}}"
subject: "Welcome, {{name}} — you're in"
html:    "<p>Hi {{name}}, thanks for signing up!</p>"

Every new form submission triggers an instant welcome email delivered via Mailgrid's SES pipeline.

Make (Integromat)

The Mailgrid Make app ships as a full app manifest at integrations/make/. Import it once and all modules are available across every scenario in your organization.

Available modules

Import and authenticate

1. In Make, go to Apps → Browse apps → Import app.
2. Upload the make-app.json manifest from the integrations/make/ directory.
3. Open the app settings and paste your mb_live_… API key into the API Key connection field.
4. Click Save and verify the connection — Make sends a credentials check to GET /api/events and expects 200 OK.

Using modules in a scenario

Drag any Mailgrid module onto the scenario canvas. All dynamic fields (template IDs, domain names) auto-populate via the Make API introspection layer once the connection is active.

from:        "noreply@yourdomain.com"
to:          "{{1.email}}"          // mapped from previous module
subject:     "Your order is confirmed"
template_id: "tpl_order_confirm"
variables:   { "order_id": "{{1.id}}", "total": "{{1.amount}}" }

n8n

Mailgrid ships a community node published as n8n-nodes-mailgrid at integrations/n8n/. It integrates natively into n8n's visual editor.

Install

npm install n8n-nodes-mailgrid

Then restart your n8n instance. The Mailgrid node appears under Community nodes in the node picker.

Supported operations

Example: HTTP trigger → Mailgrid send

// Node 1 — Webhook (HTTP trigger)
Method: POST
Path:   /notify

// Node 2 — Mailgrid: Send Email
Credential:  Mailgrid API (your mb_live_… key)
Operation:   Send Email
From:        "alerts@yourdomain.com"
To:          {{ $json["recipient"] }}
Subject:     {{ $json["subject"] }}
HTML:        {{ $json["body"] }}

Post a JSON payload to the n8n webhook URL and the workflow forwards it as a live email in under a second.

Pipedream

The Mailgrid Pipedream action component is published as @mailgrid/pipedream at integrations/pipedream/. Drop it into any Pipedream workflow step.

Component props

props: {
  api_key: {
    type:        "string",
    label:       "Mailgrid API Key",
    secret:      true,
    description: "Your mb_live_… key from the Mailgrid dashboard"
  },
  from:    { type: "string", label: "From address" },
  to:      { type: "string", label: "To address" },
  subject: { type: "string", label: "Subject line" },
  html:    { type: "string", label: "HTML body",  optional: true },
  text:    { type: "string", label: "Plain-text body", optional: true }
}

Add to a Pipedream workflow

1. Open your workflow in Pipedream and click + Add step.
2. Choose Use an action and search for Mailgrid.
3. Select Send Email from the component list.
4. Enter your mb_live_… key in the API Key prop — Pipedream stores it as an encrypted environment secret.
5. Map from, to, subject, and either html or text from upstream step exports (e.g., {{steps.trigger.event.email}}).
6. Click Test to send a live message, then deploy the workflow.

Pabbly Connect

Pabbly does not have a native Mailgrid app yet. Use Pabbly's built-in HTTP module (or the "Webhook by Zapier" action) to call the Mailgrid API directly.

HTTP module configuration

Method:       POST
URL:          https://api.mailgrid.space/api/emails

# Headers
Authorization: Bearer mb_live_YOUR_KEY_HERE
Content-Type:  application/json

# Body (raw JSON)
{
  "from":    "hello@yourdomain.com",
  "to":      "{{email}}",
  "subject": "{{subject}}",
  "html":    "{{html_body}}"
}

Replace {{email}}, {{subject}}, and {{html_body}} with the variable tokens Pabbly provides from your trigger step. A successful send returns HTTP 200 with a "success": true JSON body.

IFTTT & other webhooks

Any platform that can make an HTTP POST request — IFTTT, Webflow Logic, Bubble workflows, Notion automations, or a custom cron job — can send email through Mailgrid directly.

Base request shape

POST https://api.mailgrid.space/api/emails
Authorization: Bearer mb_live_YOUR_KEY_HERE
Content-Type:  application/json

{
  "from":    "sender@yourdomain.com",   // verified SES domain
  "to":      "recipient@example.com",   // or array of strings
  "subject": "Hello from my workflow",
  "html":    "<p>Body goes here</p>",   // or "text" for plain
  "replyTo": "support@yourdomain.com"   // optional
}

IFTTT Webhooks setup

1. In IFTTT, choose Webhooks as your Then action and select Make a web request.
2. Set URL to https://api.mailgrid.space/api/emails.
3. Set Method to POST and Content Type to application/json.
4. In Additional headers, add: Authorization: Bearer mb_live_YOUR_KEY_HERE.
5. Paste a JSON body, using IFTTT ingredient tags like {{Value1}} for dynamic content.

{
  "from":    "ifttt@yourdomain.com",
  "to":      "{{Value1}}",
  "subject": "{{Value2}}",
  "text":    "{{Value3}}"
}

What's next?

• Email API reference — full list of request parameters
• Templates — reuse Handlebars templates across all integration platforms
• Events & webhooks — receive delivery callbacks in your automation tool
• MCP server — drive Mailgrid from Claude or Cursor