Integration
Connect Cronly and MailUp
When something happens in Cronly or MailUp, your agent does the next thing in the other. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Cronly and MailUp 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 Cronly and MailUp can do together
From Cronly to MailUp
When Trigger Activated in Cronly
then Add list in MailUp
From MailUp to Cronly
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 Cronly and MailUp
Triggers and actions 5 triggers · 47 actions
- Trigger Activated
Triggers when a trigger is activated.
- Add back-up
Create a new back-up snapshot for a server/username (or a new one if none exists).
- Add job monitor
Create a new cron job monitor.
- Add project
Create a new project used to group monitors.
- Add server
Register a new server for back-up monitoring.
- Add SSL certificate monitor
Register a new SSL/TLS certificate monitor.
- Delete back-up
Delete a back-up by server ID and username.
- Delete job monitor
Delete a job monitor by ID.
- Delete project
Delete a project by ID.
- Delete server
Delete a server by ID.
- Delete SSL certificate monitor
Delete an SSL certificate monitor by ID.
- Get back-up
Get details of one back-up by server ID and username.
- Get job monitor
Get details of one job monitor by ID.
- Get project
Get details of one project by ID.
- Get server
Get details of one server by ID.
- Get SSL certificate monitor
Get details of one SSL certificate monitor by ID.
- Get user
Get details of one user by ID.
- List job monitors
List all registered job monitors for the company.
- List notifications
List all notifications (monitor failures, SSL certificate status changes, etc), paginated.
- List projects
List all projects.
- List servers
List all registered servers.
- List SSL certificate monitors
List all registered SSL/TLS certificate monitors.
- List users
List all users within the organization.
- 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}
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 Cronly
Cronly to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Cronly to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Cronly to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Cronly to Google SheetsGoogle Sheets
Cronly to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Cronly to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
More into MailUp
Google Calendar to MailUpGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Mailchimp to MailUpMailchimp marketing automation and email platform.
Questions
Cronly and MailUp, answered
What can start an automation from Cronly?
Any of Cronly's 1 trigger in the catalog, including Trigger Activated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in MailUp when something happens in Cronly?
Any of MailUp's 25 actions, including Create New Email Message, Create New Group, Send Message to Email Address and Send Message to Group. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from MailUp to Cronly?
Yes. When something happens in MailUp, your agent can act in Cronly too. This page covers both directions: MailUp's triggers and Cronly's actions are listed here as well.
Do I have to build a connector for Cronly or MailUp?
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.