Integration · Create and promote
Sender and Meteor AI agents
Connect Sender to a Met: add subscribers, build segments, keep campaigns as drafts and review how your emails performed with the official MCP.
How does Sender connect to Meteor?
With the Sender ready connector, your Met works on your Sender account, authorized once with OAuth and with your role's permissions. It finds a subscriber by email or phone, creates them or changes their groups, and reads your groups and segments. It builds new segments, keeps email campaigns as drafts with their content and returns the report of the ones already sent. It also reads your automations, validates them and creates new workflows, which start inactive. No campaign is sent through the MCP: you send it from Sender. Unsubscribing a subscriber and putting a workflow live start turned off.
What it automates
What a Meteor Met does with Sender
Add whoever asks to the list
A customer asks on WhatsApp to receive your news by email. The Met checks whether they already exist in Sender, creates them if not, and adds them to the group your team named.
Prepare this week's campaign
The Met uses a previous campaign as a reference, creates the new one as a draft with its audience and content, and lets you know so you can review it and send it from Sender.
Report how a campaign did
When you ask, the Met returns the report of the sent campaign and sums up opens, clicks and unsubscribes in the chat.
Review your automations
The Met reads your active workflows, validates them and tells you which step blocks activating a new one or which workflows overlap.
25 tools
Everything your Met can ask Sender for
Each one is a real action in the connector. You can switch off the ones you would rather it never used.
| Tool | What it does |
|---|---|
get_account_details | Returns the account name, time zone, country, plan and user. |
list_domains | Lists your sending domains with their verification, SPF, DKIM and DMARC status. |
list_subscribers | Lists the subscribers in the account. |
get_subscriber | Returns a subscriber by their ID, email or phone. |
create_subscriber | Creates a subscriber with their fields, groups and status on each channel. |
update_subscriber | Changes a subscriber's fields, groups or per channel status. |
subscribe_subscribers | Reactivates one or more people on a channel. |
unsubscribe_subscribers | Unsubscribes one or more people on a channel. Starts turned off. |
list_groups | Lists the subscriber groups. |
get_group | Returns the details of a subscriber group. |
list_segments | Lists the segments in the account. |
get_segment | Returns a segment's conditions, explained in plain language. |
create_segment | Creates a segment from conditions. |
list_email_campaigns | Lists the email campaigns. |
get_email_campaign | Returns a campaign with its audience, reports and content. |
get_email_campaign_report | Returns the performance report of a campaign already sent. |
create_email_campaign | Creates a draft campaign with sender, audience and content. It never sends it. |
update_email_campaign_content | Replaces the content of a draft campaign. |
list_workflows | Lists your automations with some engagement metrics. |
get_workflow | Returns the full workflow, its steps explained and what blocks activating it. |
get_workflow_report | Returns a workflow's performance report, with revenue if your plan includes it. |
validate_workflow | Checks a workflow without changing anything and returns everything that blocks activation. |
create_workflow | Creates a full workflow with its trigger and steps. It always stays a draft. |
activate_workflow | Runs the full preflight check and, if it passes, puts the workflow live. It starts off until the admin turns it on. |
deactivate_workflow | Returns an active workflow to draft without losing subscribers in progress. |
The limits
What the Sender integration does NOT do
We would rather say it here than have you find out during rollout.
-
It does not send campaigns. Campaigns created through the MCP stay as drafts and there is no tool to send them: you send them from Sender.
-
It does not create campaign drafts without a verified sending domain. The sender address has to be on a domain verified in your account.
-
It does not edit an active workflow. It has to go back to draft first; subscribers in progress are kept.
-
It does not ask you for confirmation in the chat before writing. The admin chooses which actions stay on; unsubscribing subscribers and activating workflows start turned off.
-
It does not go beyond your role or your plan. Each tool checks the permissions of the user who authorized the connection, and whatever your plan does not include is not available either.
Before you start
What you need to connect Sender
- 1
A Sender account
The Sender account where you keep your subscribers. To keep campaigns as drafts you need a verified sending domain.
- 2
Connect it in Met
In Met, open Connections → Sender → Connect. You sign in to Sender and approve access; there is no key to copy.
- 3
Decide which actions stay on
The workspace admin chooses which actions stay on. Unsubscribing subscribers and activating workflows start turned off.
Frequently asked questions
Questions about Sender and Meteor
No. The Sender MCP has no tool that sends campaigns: the Met keeps them as drafts and you send them from Sender.
Yes, if the admin turns it on: activating a workflow starts off. Activating a workflow runs the same preflight check as the Sender dashboard and, if something blocks it, it does not activate.
No. The connection carries the role of the user who authorized it: if your role cannot see or edit something in Sender, neither can the Met.
You do, with your Sender account and plan. Met does not charge for the calls your Met makes to Sender.
Step by step
Automations that use Sender
Complete tasks, with the steps and the tools that run at each one.
Create and promote
Other integrations in the same family
Want to see a Met running Sender?
We will show you with your own account connected, not with a canned demo.