Build solutions, not workarounds.
What do you want MailUp and Qstash to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What MailUp can start in Qstash
When New Email Message in List in MailUp
then Enqueue message in Qstash
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with MailUp and Qstash
Triggers and actions 4 triggers · 45 actions
- New Email Message in List
A new email message was created in the list. MailUp is a multi-list environment and messages are list-specific.
- New Group
New group added to the specified list. MailUp is a multi-list environment and groups are list-specific.
- New Recipient Subscribed
There is a new subscriber in the specified list. MailUp is a multi-list environment.
- New Recipient Unsubscribed
A recipient unsubscribed from the specified list. MailUp is a multi-list environment.
- Add list
Create a new list. POST Console/List
- Add Recipient to Group
Add recipient to the specified group on the list.
- Add Recipient to List
Adds a new recipient to the specified list as a subscriber.
- Create New Email Message
Create a new email message on the specified list.
- Create New Group
Add a new group to the specified list. MailUp is a multi-list environment.
- Delete email message
Delete an email message. DELETE Console/List/{id_List}/Email/{id_Message}
- Delete group
Delete a group in a list. DELETE Console/List/{id_List}/Group/{id_Group}
- Delete list
Delete a list. DELETE Console/List/{id_List}
- Get email message
Retrieve email message details. GET Console/List/{id_List}/Email/{id_Message}
- Get list
Retrieve list details by id. GET Console/List/{id_List}
- List email messages
Retrieve email messages of a list. GET Console/List/{id_List}/Emails
- List Email Message Sendings
lists the sendings (send tasks, with recipients count and status) created for an email message.
- List Group Recipients
Lists the recipients in a MailUp group (GET Console/Group/{id_group}/Recipients), with id, email, name and personal data fields.
- List groups
Retrieve groups of a list. GET Console/List/{id_List}/Groups
- List lists
Retrieve the console's lists. GET Console/List on services.mailup.com/API/v1.1/Rest/ConsoleService.svc
- List subscribed recipients
Retrieve subscribed recipients of a list. GET Console/List/{id_List}/Recipients/Subscribed
- Remove recipient from group
Unsubscribe a recipient from a group. DELETE Console/Group/{id_Group}/Unsubscribe/{id_Recipient}
- Remove Recipient From List
This method unsubscribe the given recipient from the specified list.
- Send Message to Email Address
Sends the specified message (previously created in MailUp in the specified List) to the email address specified.
- Send Message to Group
Send a message to a predefined group in the specified list.
- Send message to list
Send an email message to all recipients of a list. POST Console/List/{id_List}/Email/{id_Message}/Send
- Unsubscribe recipient from list
Unsubscribe a recipient from a list. DELETE Console/List/{id_List}/Unsubscribe/{id_Recipient}
- Update email message
Modify an email message. PUT Console/List/{id_List}/Email/{id_Message}
- Update group
Modify a group in a list. PUT Console/List/{id_List}/Group/{id_Group}
- Update list
Modify details of a list. PUT Console/List/{id_List}
- Add queue
Create or update a queue (upsert), setting parallelism.
- Add schedule
Create a cron-based schedule that periodically publishes a message to a destination.
- Add URL group endpoint
Create a URL group or add/update an endpoint within it (fan-out publishing target).
- Batch publish messages
Publish multiple messages to multiple destinations in one call.
- Delete DLQ message
Remove a message from the dead-letter queue.
- Delete message
Cancel a message that has not yet been delivered.
- Delete queue
Delete a queue by name.
- Delete schedule
Delete a schedule by id.
- Delete URL group
Deletes a QStash URL group and all its endpoints. In-flight messages are not removed.
- Enqueue message
Add a message to a named queue for sequential delivery.
- Get DLQ message
Retrieve a single dead-letter queue message by id.
- Get message
Retrieve a queued/published message by id.
- Get queue
Retrieve a queue's configuration and stats by name.
- Get schedule
Retrieve a schedule by id.
- Get URL group
Retrieve a URL group and its endpoints by name.
- List DLQ messages
List messages that failed delivery and landed in the dead-letter queue.
- List queues
List all queues for the account.
- Publish message
Publish a single message to a URL or URL group for QStash to deliver.
- Retry DLQ message
Re-attempt delivery of a dead-lettered message now.
- Update schedule
Updates an existing QStash schedule by replacing its settings (destination, cron, message and delivery options).
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from MailUp
MailUp to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
MailUp to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
MailUp to StripeStripe is a payment processing platform for online businesses.
MailUp to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
MailUp to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
MailUp to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Qstash
HubSpot to QstashHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to QstashGoogle Sheets
Gmail to QstashGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to QstashGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
MailUp and Qstash, answered
What can start an automation from MailUp?
Any of MailUp's 4 triggers in the catalog, including New Email Message in List, New Group, New Recipient Subscribed and New Recipient Unsubscribed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Qstash when something happens in MailUp?
Any of Qstash's 20 actions, including Update schedule, Add queue, Add schedule and Add URL group endpoint. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Qstash to MailUp?
Qstash has no triggers in the catalog today, so automations start in MailUp. If you need the other direction, ask: your agent reads Qstash's API documentation and adds it.
Do I have to build a connector for MailUp or Qstash?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.