API & automation

Make MailRig part of your stack.

Connect your CRM, lead sources, AI workflows, internal tools, and reporting directly to MailRig. Move leads, launch campaigns, personalize messages, receive events, and automate your outbound.

REST APIWebhooksAI-ready
MailRig Integrations: Claude, ChatGPT and other AI apps, the CLI, API, SMTP and webhooks

Use the AI you want. Send through MailRig.

Use Claude, ChatGPT, an enrichment tool, or your own models to personalize a lead before it enters a campaign. MailRig handles the sequence and the sending.

  1. 01Lead data
  2. 02AI or automation
  3. 03Personalized variables
  4. 04MailRig campaign
  5. 05Send
The lead
Sarah · VP Sales · Acme
What your workflow returns
opening_line

Saw Acme just expanded its enterprise sales team…

pain_point

Scaling outbound without adding more SDR admin

cta

Worth comparing notes?

Need us to build it? Custom AI and automation work is available on custom pricing.

Control the outbound operation programmatically.

Your systems work with the same contacts, campaigns, sequences, replies, and data your team uses inside MailRig.

Contacts

Create, update, search, tag, and organize leads programmatically.

Campaigns

Create campaigns, add contacts, change campaign state, and pause sending.

Sequences

Work with sequence steps, follow-ups, and test sends.

Replies

Read replies, update reply state, and trigger follow-up workflows.

Sending accounts

Read and manage the sending identities connected to your operation.

Reporting and data

Pull activity into your own reporting, applications, or internal systems.

Campaigns created through the API still run through the same pacing, suppression and deliverability controls as the dashboard.

Your leads can move without you moving them.

When something happens elsewhere in your stack, MailRig takes the next step on its own.

Enrichment tools

Enrich a lead, create the contact in MailRig, add it to the right campaign.

CRM

A prospect replies, the lead updates, sales gets a task.

Forms and lead sources

A qualified lead arrives and the right sequence starts.

Reporting

Campaign activity changes and the data reaches your dashboard.

Works with Clay, n8n, Make, Zapier, or anything that can send an HTTP request and receive a webhook. No app to write.

  1. Lead is qualified
    In your enrichment or automation tool
  2. Contact created
    MailRig
  3. Added to a campaign
    MailRig
  4. Sequence sends
    MailRig
  5. Prospect replies
    MailRig
  6. Webhook fires
    MailRig
  7. CRM updates
    Your system
  8. Sales is notified
    Your system

Your systems know the moment something happens.

Subscribe to MailRig events and let the rest of your stack react in real time.

reply.received
Update the CRM and notify sales.
unsubscribe
Suppress them everywhere.
campaign.updated
Update your dashboard.
bounce · complaint
Feed it into your reporting.
contact.updated
Keep lead state in sync.
email.sent
Log the activity against the lead.
A delivery your endpoint does not accept is retried rather than dropped.

Built for developers too.

curl https://api.mailrig.io/v1/contacts \
  -H "Authorization: Bearer $MAILRIG_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "sarah@acme.com",
    "company": "Acme",
    "custom_variables": {
      "opening_line": "Saw Acme just expanded its enterprise team..."
    }
  }'
GET/contactsPOST/contactsGET/campaignsPOST/campaignsPATCH/campaigns/:idGET/repliesPOST/webhooks
REST API

Standard HTTP requests with JSON.

Bearer authentication

Secure API-key based access.

Custom variables

Pass enriched or AI-generated data into campaigns.

Webhooks

Receive outbound events as they happen.

MailRig app

Run campaigns through the dashboard.

Connected workflow

Use your CRM, enrichment, automation tools, or AI alongside MailRig.

Custom build

Make MailRig part of your own product or internal systems.

You never need the API to run MailRig.

Frequently asked questions:

Yes. API access is part of the product rather than a separate enterprise-only add-on.

No. Everything required to run normal campaigns is available through the MailRig application. The API is there for teams that want more automation or custom workflows.

Yes. MailRig works with any platform that can send an HTTP request and receive a webhook, which covers the common automation tools as well as anything you build yourself.

Yes, through your own workflow. You generate the personalized fields with whichever AI tools or models you already use, then pass them to MailRig as custom variables on the contact. MailRig does not run those models itself; it sends the campaign that uses their output.

No.

API requests go through the same account, campaign, suppression, capacity and sending rules as actions made through the dashboard. There is no separate raw sending route that bypasses MailRig’s controls.

Icon

Still have questions?

Have a question about MailRig, your setup, or switching over? We’re happy to talk it through with you.