# MailUp

```json
{
  "name": "MailUp",
  "slug": "mail_up",
  "url": "https://composio.dev/toolkits/mail_up",
  "markdown_url": "https://composio.dev/toolkits/mail_up.md",
  "logo_url": "https://logos.composio.dev/api/mailup",
  "categories": [
    "marketing & social media"
  ],
  "is_composio_managed": false,
  "updated_at": "2026-10-28T05:33:04.241Z"
}
```

![MailUp logo](https://logos.composio.dev/api/mailup)

## Description

Securely connect your AI agents and chatbots (Claude, ChatGPT, Cursor, etc) with MailUp MCP or direct API to manage recipients, create campaigns, send email and SMS messages, and review engagement statistics through natural language.

## Summary

MailUp is an email and SMS marketing platform for managing contacts, campaigns, and engagement data.
It helps teams run targeted marketing campaigns and track performance from one place.

## Categories

- marketing & social media

## Toolkit Details

- Tools: 151

## Images

- Logo: https://logos.composio.dev/api/mailup

## Authentication

- **Oauth2**
  - Type: `oauth2`
  - Description: Oauth2 authentication for MailUp.
  - Setup:
    - Configure Oauth2 credentials for MailUp.
    - Use the credentials when creating an auth config in Composio.

## Suggested Prompts

- List recent MailUp campaigns by engagement
- Add recipients to a MailUp subscriber list
- Review MailUp SMS delivery statistics

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `MAIL_UP_ADD_IMAGE` | Add Image | Decode and store supplied base64 image data in either MailUp's shared console library or one list, returning the resulting full paths. This creates persistent provider content, requires image/list access, and counts toward the 5-calls-per-second standard REST limit. |
| `MAIL_UP_ADD_MESSAGE_ATTACHMENTS` | Add Message Attachment | Upload base64-encoded bytes into a specific attachment slot on one MailUp email message. |
| `MAIL_UP_ASSOCIATE_PERSONALIZATION_ENDPOINT_WITH_LIST` | Associate Personalization Endpoint With List | Associate an existing MailUp personalization endpoint with one list. This operation requires Personalization to be enabled by MailUp for the connected platform account. |
| `MAIL_UP_ASYNC_IMPORT_SMS_RECIPIENTS_TO_GROUP` | Import SMS Recipients To Group | Asynchronously add or update an SMS recipient batch in a MailUp group and return the import ID. clear_missing_or_empty_fields=true permanently clears stored recipient fields omitted or empty in each row. remove_from_prev_groups=true removes each recipient from every previous group before adding this group. Requires SMS entitlement; limit traffic to 5 calls per second. |
| `MAIL_UP_ASYNC_IMPORT_SMS_RECIPIENTS_TO_LIST` | Import SMS Recipients To List | Asynchronously add or update an SMS recipient batch in a MailUp list and return the import ID. clear_missing_or_empty_fields=true permanently clears stored recipient fields omitted or empty in each row. Requires SMS entitlement; limit traffic to 5 calls per second. |
| `MAIL_UP_ASYNC_IMPORT_SMS_RECIPIENT_TO_GROUP` | Import One SMS Recipient To Group | Add or update one SMS recipient in a MailUp group and return the recipient ID. clear_missing_or_empty_fields=true permanently clears stored recipient fields omitted or empty in this request. remove_from_prev_groups=true removes the recipient from every previous group before adding this group. Requires SMS entitlement; observe the 5 calls per second limit. |
| `MAIL_UP_ASYNC_IMPORT_SMS_RECIPIENT_TO_LIST` | Import One SMS Recipient To List | Add or update one SMS recipient in a MailUp list and return the recipient ID. clear_missing_or_empty_fields=true permanently clears stored recipient fields omitted or empty in this request. Requires SMS entitlement; observe the 5 calls per second limit. |
| `MAIL_UP_BATCH_UNSUBSCRIBE_RECIPIENTS_FROM_LIST` | Batch Unsubscribe Recipients From List | Remove multiple recipients' memberships from one MailUp list without deleting their global recipient records. This non-atomic action processes 1-20 unique recipient IDs sequentially at less than 5 requests per second. It stops after the first failed or unknown removal, reports any partial completion, and marks remaining recipients not_attempted; successful earlier removals are not rolled back. |
| `MAIL_UP_CONFIRM_SMS_NUMERIC_SENDER` | Confirm SMS Numeric Sender | Confirm a MailUp numeric SMS sender using the code previously delivered by the sender-confirmation flow. Confirmation and SMS entitlement may be required before sending; observe MailUp's limit of 5 calls per second. |
| `MAIL_UP_COPY_EMAIL_MESSAGE` | Copy Email Message | Create a copy of one MailUp email message, optionally replacing its subject or internal notes; this does not send it. |
| `MAIL_UP_COUNT_MESSAGE_SENDING_RECIPIENTS` | Count Message Sending Recipients | Return MailUp's count of recipients to whom one email message was sent. This is the SendingRecipients statistic, distinct from the recipient-detail list; message-recipient data is retained for the console retention period, up to 12 months, after which related recipient statistics can be zero or empty. |
| `MAIL_UP_COUNT_SUBSCRIBERS` | Count Subscribers | Return the subscribed-recipient count for a MailUp list or, when group_id is supplied, for one group in that list. |
| `MAIL_UP_CREATE_AUDIENCE_GROUP` | Create Audience Group | Create a recipient group in one MailUp list and return the complete group record. |
| `MAIL_UP_CREATE_CONTENT_SOURCE` | Create Content Source | Create a named content-provider source in MailUp. |
| `MAIL_UP_CREATE_EMAIL_MESSAGE` | Create Email Message | Create a draft email campaign message in one MailUp list without sending it. |
| `MAIL_UP_CREATE_EMAIL_MESSAGE_FROM_TEMPLATE` | Create Email Message from Template | Create a new draft email message in a MailUp list from an existing template without sending it. |
| `MAIL_UP_CREATE_LIST` | Create List | Create a MailUp mailing list without adding recipients or sending messages. The request must supply at least one settings source: id_settings or use_default_settings. Availability and accepted settings depend on the connected user's console permissions; MailUp limits standard REST traffic to 5 calls per second. |
| `MAIL_UP_CREATE_PERSONALIZATION_ENDPOINT` | Create Personalization Endpoint | Create a MailUp endpoint used to obtain external personalization data. This operation requires Personalization to be enabled by MailUp for the connected platform account. |
| `MAIL_UP_CREATE_SMS_MESSAGE` | Create SMS Message | Create a MailUp SMS draft without sending or consuming delivery credits. The account needs SMS entitlement; observe MailUp's limit of 5 calls per second. |
| `MAIL_UP_CREATE_SMTP_PLUS_ACCOUNT` | Create SMTP+ Account | Create an SMTP+ user account for a MailUp list and return its generated credentials. Supply at least one non-empty trusted domain or confirmed trusted sender, and choose priority_code from GET_SMTP_PLUS_PRIORITY_CODES. This feature-gated operation requires SMTP+ to be enabled by MailUp for the connected platform account. |
| `MAIL_UP_CREATE_TAG` | Create Tag | Create a named tag in one MailUp list for organizing email messages. |
| `MAIL_UP_DELETE_AUDIENCE_GROUP` | Delete Audience Group | Permanently delete one MailUp group. This does not delete its recipients from the parent list. |
| `MAIL_UP_DELETE_AUDIENCE_RECIPIENT_FROM_LIST` | Delete Audience Recipient From List | Delete one recipient record from one MailUp list only; other list memberships are unaffected. |
| `MAIL_UP_DELETE_AUDIENCE_RECIPIENT_GLOBALLY` | Delete Audience Recipient Globally | Permanently delete one MailUp recipient from every list in the account. This high-impact operation can remove all list memberships and returns a result for each affected list. |
| `MAIL_UP_DELETE_CONTENT_SOURCE` | Delete Content Source | Permanently delete one MailUp content-provider source. |
| `MAIL_UP_DELETE_EMAIL_MESSAGE` | Delete Email Message | Permanently delete one MailUp email message from a list. This does not cancel an already queued sending. |
| `MAIL_UP_DELETE_IMAGE` | Delete Image | Permanently delete the image at an exact full MailUp path from provider storage. This destructive operation has no list-specific route, requires image access, and counts toward the 5-calls-per-second standard REST limit. |
| `MAIL_UP_DELETE_LIST` | Delete List | Permanently delete one MailUp list and its list-scoped configuration. This destructive operation requires console permission, cannot be undone, and is subject to MailUp's 5-calls-per-second standard REST limit. |
| `MAIL_UP_DELETE_MESSAGE_ATTACHMENTS` | Delete Message Attachment | Permanently remove the attachment in one slot from a MailUp email message and return the remaining attachments. |
| `MAIL_UP_DELETE_PERSONALIZATION_ENDPOINT` | Delete Personalization Endpoint | Permanently delete one MailUp personalization endpoint. This operation requires Personalization to be enabled by MailUp for the connected platform account. |
| `MAIL_UP_DELETE_SENDING` | Delete Email Sending Task | Delete an existing MailUp email sending task record; this does not recall email already delivered. MailUp permits at most 1 combined stop or delete call per 30 seconds. A process-local guard coordinates both actions in this worker only; MailUp remains authoritative across workers and other clients. Never retry automatically after a rejection or ambiguous result. |
| `MAIL_UP_DELETE_SMS_MESSAGE` | Delete SMS Message | Permanently delete one MailUp SMS draft without sending it. Requires SMS service entitlement; observe MailUp's limit of 5 calls per second. |
| `MAIL_UP_DELETE_SOURCE_CONTENT` | Delete Source Content | Permanently delete one keyed content item from a MailUp content-provider source. |
| `MAIL_UP_DELETE_TAG` | Delete Tag | Permanently delete one tag from a MailUp list; messages using it may lose that classification. |
| `MAIL_UP_DISABLE_TRUSTED_SENDER_BY_ID` | Disable Trusted Sender | Disable a trusted sender registration by ID so it is no longer active for sending. The action verifies the sender address because MailUp may return one ID for multiple registrations, then supplies MailUp's required request GUID internally. This feature-gated operation requires Trusted Senders to be enabled by MailUp for the connected platform account. |
| `MAIL_UP_DISASSOCIATE_PERSONALIZATION_ENDPOINT_FROM_LIST` | Disassociate Personalization Endpoint From List | Remove one MailUp personalization endpoint association from a list. This operation requires Personalization to be enabled by MailUp for the connected platform account. |
| `MAIL_UP_EMPTY_AUDIENCE_GROUP` | Empty Audience Group | Remove every recipient membership from one MailUp group. This high-impact operation leaves the group and parent-list recipients intact. |
| `MAIL_UP_ENABLE_DYN_FIELDS_ON_EMAIL_MESSAGE` | Set Email Message Dynamic Fields | Enable or disable dynamic recipient-field substitution on one MailUp email message and return its complete current details. |
| `MAIL_UP_ENABLE_DYN_FIELDS_ON_SMS_MESSAGE` | Set SMS Message Dynamic Fields | Explicitly enable or disable dynamic recipient-field substitution for one MailUp SMS draft. Requires SMS entitlement; limit traffic to 5 calls per second. |
| `MAIL_UP_ENABLE_TRACKING_FOR_EVERY_LIST` | Set Tracking for Every List | Explicitly enable or disable email tracking for one recipient across every MailUp list. The enable boolean is the desired final state. |
| `MAIL_UP_ENABLE_TRACKING_FOR_SINGLE_LIST` | Set Tracking for List | Explicitly enable or disable email tracking for one recipient on one MailUp list. The enable boolean is the desired final state. |
| `MAIL_UP_FIND_RECIPIENTS` | Find Recipients | Find MailUp recipients by email address, mobile number, or both; this endpoint cannot list recipients without a lookup value. |
| `MAIL_UP_GET_ACCOUNT_DETAILS` | Get Account Details | Return the connected MailUp account identity, plan, trial status, expiry, and available credits; use this before credit-dependent sending. |
| `MAIL_UP_GET_ACCOUNT_INFO` | Get Account Info | Return the authenticated MailUp account identity, console version, trial flag, and optional expiry/URL. This is account metadata, not credits or plan details, and is subject to the 5-calls-per-second standard REST limit. |
| `MAIL_UP_GET_ARCHIVED_MAIL_MESSAGES_BY_LIST` | List Archived Email Messages | Return one page of archived email messages from a specific MailUp list. |
| `MAIL_UP_GET_DATE_FOR_DEFERRED_DISPATCH` | Get Deferred Dispatch Date | Get the first useful MailUp date for scheduling a sending task. |
| `MAIL_UP_GET_DATE_FOR_DEFERRED_SMS_DISPATCH` | Get Earliest Deferred SMS Dispatch Date | Return MailUp's earliest useful scheduling date for one SMS sending task. This is a read-only Console API operation: it does not send SMS or consume SMS credits. The connected MailUp account and relevant list must have the SMS channel enabled. MailUp limits Console API traffic to 5 calls per second. |
| `MAIL_UP_GET_DEFERRED_SMS_SENDING_STATUS` | List Deferred SMS Sendings | Return SMS sending tasks scheduled for deferred dispatch. This is a read-only Console API operation: it does not send SMS or consume SMS credits. The connected MailUp account and relevant list must have the SMS channel enabled. MailUp limits Console API traffic to 5 calls per second. |
| `MAIL_UP_GET_EMAIL_MESSAGE` | Get Email Message | Return the content, subject, tracking settings, tags, dynamic fields, and attachments for one MailUp email message. |
| `MAIL_UP_GET_EMAIL_SEND_HISTORY` | List Email Send History for List | Return one page of send-history records across all email messages in one MailUp list. |
| `MAIL_UP_GET_EMAIL_TEMPLATE_DETAILS` | Get Email Template Details | Return metadata and content for one email template in a MailUp list. |
| `MAIL_UP_GET_EMAIL_TEMPLATES` | List Email Templates | Return one page of email templates defined in a specific MailUp list. |
| `MAIL_UP_GET_IMMEDIATE_SMS_SENDING_STATUS` | List Immediate SMS Sendings | Return SMS sending tasks scheduled for immediate dispatch. This is a read-only Console API operation: it does not send SMS or consume SMS credits. The connected MailUp account and relevant list must have the SMS channel enabled. MailUp limits Console API traffic to 5 calls per second. |
| `MAIL_UP_GET_IMPORT_DETAILS` | Get Import Details | Return the complete MailUp import configuration and nested valid/invalid row totals for one import ID. Access follows the connected user's list permissions and standard REST traffic is limited to 5 calls per second. |
| `MAIL_UP_GET_IMPORT_SENDING` | Get Import Sending | Return the sending and message IDs for confirmation requests generated by one MailUp import. Data exists only when that import generated confirmation messages; standard REST traffic is limited to 5 calls per second. |
| `MAIL_UP_GET_IMPORT_STATUS` | Get Import Status | Return completion and recipient outcome counts for an asynchronous MailUp import ID. |
| `MAIL_UP_GET_LAST_SENT_SMS` | List Last Sent SMS Messages | Return the most recently sent SMS messages and their account-billing costs for one list. This is a read-only Console API operation: it does not send SMS or consume SMS credits. The connected MailUp account and relevant list must have the SMS channel enabled. MailUp limits Console API traffic to 5 calls per second. |
| `MAIL_UP_GET_LIST` | Get List | Return configuration and sender details for one MailUp mailing list by ID. |
| `MAIL_UP_GET_LOGIN_URL` | Get MailUp Login URL | Create an ephemeral URL that logs a user into the MailUp platform. This is a feature-gated SSO operation: MailUp must enable SSO for the connected platform account before this action can succeed. |
| `MAIL_UP_GET_MAIL_MESSAGES_BY_USER` | List Current User Email Messages | Return one page of cloned and original email messages across lists for the current MailUp user. |
| `MAIL_UP_GET_MESSAGE_ATTACHMENTS` | List Message Attachments | Return all attachment slots currently configured on one MailUp email message. |
| `MAIL_UP_GET_MESSAGE_STATISTICS` | Get Message Statistics | Return aggregate recipient, view, click, bounce, and unsubscription counts for one MailUp email message using five read-only statistics calls. Counts can be zero after MailUp's message-recipient retention period expires. |
| `MAIL_UP_GET_MESSAGE_STATISTICS_PAGES` | Get Message Statistics Pages | Return MailUp's precompiled public statistics-page URLs for one message: overall, click trend, opens, link tracking, readers, and sent reports, plus the console login URL. These human-facing pages expose less detail than the statistics API; the console URL can also reveal the account host. Legacy click/open filter pages are no longer available and are not returned by the current XSD. |
| `MAIL_UP_GET_NOT_TEMPORARY_SMS_ERRORS` | List Non-Temporary SMS Errors | Return undelivered SMS error totals grouped by originator address. This is a read-only Console API operation: it does not send SMS or consume SMS credits. The connected MailUp account and relevant list must have the SMS channel enabled. MailUp limits Console API traffic to 5 calls per second. |
| `MAIL_UP_GET_PENDING_SMS_RECIPIENTS_BY_LIST` | List Pending SMS Recipients By List | Return recipients whose SMS subscription is pending in one MailUp list. This is a read-only Console API operation: it does not send SMS or consume SMS credits. The connected MailUp account and relevant list must have the SMS channel enabled. MailUp limits Console API traffic to 5 calls per second. |
| `MAIL_UP_GET_PERSONALIZATION_ENDPOINT` | Get Personalization Endpoint | Retrieve one MailUp personalization endpoint including its configured details. This operation requires Personalization to be enabled by MailUp for the connected platform account. |
| `MAIL_UP_GET_PUBLISHED_MAIL_MESSAGES_BY_LIST` | List Published Email Messages | Return one page of email messages currently visible online for a specific MailUp list. |
| `MAIL_UP_GET_RECIPIENT` | Get Recipient | Return contact details, dynamic fields, and list membership states for one MailUp recipient ID. |
| `MAIL_UP_GET_RECIPIENT_STATISTICS` | Get Recipient Statistics | Return aggregate delivery, view, click, bounce, and unsubscription counts for one MailUp recipient using five rate-limited, read-only statistics calls. Counts can be zero after MailUp's message-recipient retention period expires. |
| `MAIL_UP_GET_SMS_CONFIRMATION_CODE` | Request SMS Numeric Sender Confirmation Code | Request the authentication code for a MailUp numeric SMS sender and return whether MailUp accepted the request. This mutates sender-verification state and may cause MailUp to issue a code; never retry automatically after any status or transport failure because the first request may have succeeded. The SMS channel and sender verification must be enabled. MailUp limits Console API traffic to 5 calls per second. |
| `MAIL_UP_GET_SMS_MESSAGE_DETAILS` | Get SMS Message Details | Return the complete XSD-defined content and settings for one MailUp SMS message. This is a read-only Console API operation: it does not send SMS or consume SMS credits. The connected MailUp account and relevant list must have the SMS channel enabled. MailUp limits Console API traffic to 5 calls per second. |
| `MAIL_UP_GET_SMS_MESSAGES_BY_LIST` | List SMS Messages By List | Return SMS campaign message summaries from one MailUp list. This is a read-only Console API operation: it does not send SMS or consume SMS credits. The connected MailUp account and relevant list must have the SMS channel enabled. MailUp limits Console API traffic to 5 calls per second. |
| `MAIL_UP_GET_SMS_MESSAGE_SEND_HISTORY` | List SMS Message Send History | Return sending attempts and recipient counts for one SMS message. This is a read-only Console API operation: it does not send SMS or consume SMS credits. The connected MailUp account and relevant list must have the SMS channel enabled. MailUp limits Console API traffic to 5 calls per second. |
| `MAIL_UP_GET_SMS_MESSAGE_SENDING_REPORT_BY_SMS_ID` | Get SMS Message Sending Report | Return aggregate duration, cost, recipient-message, and billable SMS-part totals for one SMS message. This is a read-only Console API operation: it does not send SMS or consume SMS credits. The connected MailUp account and relevant list must have the SMS channel enabled. MailUp limits Console API traffic to 5 calls per second. |
| `MAIL_UP_GET_SMS_MESSAGE_SENDING_REPORT_DETAILS_BY_SMS_ID` | List SMS Message Sending Report Details | Return per-recipient delivery statuses and errors for one SMS message. A DeliveryId filter returns at most one detail. This is a read-only Console API operation: it does not send SMS or consume SMS credits. The connected MailUp account and relevant list must have the SMS channel enabled. MailUp limits Console API traffic to 5 calls per second. |
| `MAIL_UP_GET_SMS_NUMERIC_SENDER_STATUS` | Get SMS Numeric Sender Status | Return the verification status code and description for one numeric MailUp SMS sender. This is a read-only Console API operation: it does not send SMS or consume SMS credits. The connected MailUp account and relevant list must have the SMS channel enabled. MailUp limits Console API traffic to 5 calls per second. |
| `MAIL_UP_GET_SMS_RECIPIENTS_BY_GROUP` | List SMS Recipients By Group | Return recipients in one MailUp group using the SMS channel projection. This is a read-only Console API operation: it does not send SMS or consume SMS credits. The connected MailUp account and relevant list must have the SMS channel enabled. MailUp limits Console API traffic to 5 calls per second. |
| `MAIL_UP_GET_SMTP_PLUS_PRIORITY_CODES` | Get SMTP+ Priority Codes | List the SMTP+ priority codes available in MailUp. This feature-gated operation requires SMTP+ to be enabled by MailUp for the connected platform account. |
| `MAIL_UP_GET_SUBSCRIBED_SMS_RECIPIENTS_BY_LIST` | List Subscribed SMS Recipients By List | Return recipients subscribed to the SMS channel in one MailUp list. This is a read-only Console API operation: it does not send SMS or consume SMS credits. The connected MailUp account and relevant list must have the SMS channel enabled. MailUp limits Console API traffic to 5 calls per second. |
| `MAIL_UP_GET_TAGS` | List Enabled Tags | Return one page of enabled tags configured for a specific MailUp list. |
| `MAIL_UP_GET_TEMPORARY_SMS_ERRORS` | List Temporary SMS Errors | Return temporary undelivered SMS error totals grouped by originator address. This is a read-only Console API operation: it does not send SMS or consume SMS credits. The connected MailUp account and relevant list must have the SMS channel enabled. MailUp limits Console API traffic to 5 calls per second. |
| `MAIL_UP_GET_TRACKING_STATUS_FOR_EVERY_LIST` | Get Tracking Status for Every List | Get one recipient's email tracking status across every MailUp list. |
| `MAIL_UP_GET_TRACKING_STATUS_FOR_SINGLE_LIST` | Get Tracking Status for List | Get one recipient's email tracking status for a specific MailUp list. |
| `MAIL_UP_GET_TRUSTED_SENDER` | Get Trusted Sender | Get one trusted sender registration by ID. This feature-gated operation requires Trusted Senders to be enabled by MailUp for the connected platform account. |
| `MAIL_UP_GET_TRUSTED_SENDERS` | List Trusted Senders | Return one page of trusted sender registrations. This feature-gated operation requires Trusted Senders to be enabled by MailUp for the connected platform account. |
| `MAIL_UP_GET_UNDEFINED_SMS_SENDING_STATUS` | List Unscheduled SMS Sendings | Return SMS sending tasks that still need a dispatch schedule. This is a read-only Console API operation: it does not send SMS or consume SMS credits. The connected MailUp account and relevant list must have the SMS channel enabled. MailUp limits Console API traffic to 5 calls per second. |
| `MAIL_UP_GET_UNSUBSCRIBED_SMS_RECIPIENTS_BY_LIST` | List Unsubscribed SMS Recipients By List | Return recipients unsubscribed from the SMS channel in one MailUp list. This is a read-only Console API operation: it does not send SMS or consume SMS credits. The connected MailUp account and relevant list must have the SMS channel enabled. MailUp limits Console API traffic to 5 calls per second. |
| `MAIL_UP_IMPORT_AUDIENCE_RECIPIENT_TO_GROUP` | Import Audience Recipient To Group | Synchronously create or update one email recipient and add them to a MailUp group, returning the recipient ID. For a new recipient, the group's owning list becomes the owning list and they receive a Subscribed subscription status by default. confirm_email=true sends a confirmation email automatically and leaves a new recipient Pending; a Pending recipient receives another confirmation email and an Unsubscribed recipient moves to Pending. Never retry an ambiguous result because doing so can send duplicate confirmation email. |
| `MAIL_UP_IMPORT_AUDIENCE_RECIPIENT_TO_LIST` | Import Audience Recipient To List | Synchronously create or update one email recipient in a MailUp list and return the recipient ID. The target list becomes the recipient's owning list; a new recipient receives a Subscribed subscription status by default. confirm_email=true sends a confirmation email automatically and leaves a new recipient Pending; a Pending recipient receives another confirmation email and an Unsubscribed recipient moves to Pending. Never retry an ambiguous result because doing so can send duplicate confirmation email. |
| `MAIL_UP_IMPORT_RECIPIENTS` | Import Recipients | Queue an asynchronous import that adds or updates a non-empty recipient batch in one MailUp list or group. MailUp permits only one account import at a time; use the returned import ID with MAIL_UP_GET_IMPORT_STATUS until it completes. New recipients receive a Subscribed subscription status in the destination list or the group's owning list by default; confirm_email=true instead leaves them Pending and generates confirmation emails for the confirmation-request queue. import_type='asOptout' makes every supplied recipient Optout except recipients already Pending, so it can unsubscribe existing recipients. clear_missing_or_empty_fields can erase stored data and group remove_from_prev_groups can remove memberships. Never retry an ambiguous result because these effects may already have occurred. |
| `MAIL_UP_LIST_AUDIENCE_EMAIL_OPTINS_BY_LIST` | List Audience Email Opt-Ins By List | Return one page of subscribed and unsubscribed email recipients for a MailUp list with complete opt-in and opt-out details. |
| `MAIL_UP_LIST_AUDIENCE_EMAIL_OPTINS_BY_RECIPIENT` | List Audience Email Opt-Ins By Recipient | Return one page of a MailUp recipient's email subscription status and opt-in/opt-out history across lists. |
| `MAIL_UP_LIST_AUDIENCE_SMS_OPTINS_BY_LIST` | List Audience SMS Opt-Ins By List | Return one page of subscribed and unsubscribed SMS recipients for a MailUp list with complete opt-in and opt-out details. |
| `MAIL_UP_LIST_AUDIENCE_SMS_OPTINS_BY_RECIPIENT` | List Audience SMS Opt-Ins By Recipient | Return one page of a MailUp recipient's SMS subscription status and opt-in/opt-out history across lists. |
| `MAIL_UP_LIST_CONTENT_SOURCES` | List Content Sources | Return one page of MailUp content-provider sources. |
| `MAIL_UP_LIST_COUNTRY_CODES` | List Country Codes | Return MailUp's complete unpaged country-code reference for list sender settings. Availability follows console access and the call is subject to the 5-calls-per-second standard REST limit. |
| `MAIL_UP_LIST_DYNAMIC_FIELDS` | List Dynamic Fields | Return one page of recipient dynamic-field definitions and IDs. Supports provider filter/order expressions and an opaque cursor; access follows console permissions and standard REST traffic is limited to 5 calls per second. |
| `MAIL_UP_LIST_EMAIL_MESSAGES` | List Email Messages | Return one page of email campaign messages in a MailUp list, including message IDs used by message editing, sending, and statistics tools. |
| `MAIL_UP_LIST_EMAIL_SEND_HISTORY` | List Email Send History | Return one page of completed send-history records for a specific MailUp email message. |
| `MAIL_UP_LIST_EMAIL_SENDINGS` | List Email Sendings | Return one page of MailUp email sending tasks for one queue state: pending scheduling, immediate, or deferred. |
| `MAIL_UP_LIST_GROUP_RECIPIENTS` | List Group Recipients | Return one page of recipients currently associated with a MailUp group. |
| `MAIL_UP_LIST_GROUPS` | List Groups | Return one page of recipient groups in a MailUp list, including group IDs used by group-scoped tools. |
| `MAIL_UP_LIST_IMAGES` | List Images | Return all full image paths from either the console-wide shared library or one MailUp list. The provider does not paginate these arrays; list access follows console permissions and calls count toward the 5-calls-per-second standard REST limit. |
| `MAIL_UP_LIST_IMPORTS` | List Imports | Return one page of MailUp recipient imports with status codes and row counts. Supports provider filter/order expressions and an opaque cursor; standard REST traffic is limited to 5 calls per second. |
| `MAIL_UP_LIST_IMPORT_STATUS_CODES` | List Import Status Codes | Return MailUp's complete reference table for interpreting import status_code values. This unpaged metadata call is subject to the 5-calls-per-second standard REST limit. |
| `MAIL_UP_LIST_LIST_RECIPIENTS` | List List Recipients | Return one page of recipients in a MailUp list for one subscription state: subscribed, pending, or unsubscribed. |
| `MAIL_UP_LIST_LISTS` | List Lists | Return one page of mailing lists available to the connected MailUp user, including the list IDs required by list-scoped tools. |
| `MAIL_UP_LIST_LIST_SCOPES` | List List Scopes | Return MailUp's complete unpaged list-purpose reference table for scope_code settings. These are provider list-purpose codes, not OAuth scopes; the call is subject to the 5-calls-per-second standard REST limit. |
| `MAIL_UP_LIST_MESSAGE_EVENTS` | List Message Events | Return one page of recipient-level delivery, view, click, bounce, or unsubscription statistics for a sent MailUp email message. View and click rows are recipient rollups with Count, not individual event timestamps. Delivery details are retained for at most 12 months. If a message ID was reused, results aggregate every campaign sent with that ID. |
| `MAIL_UP_LIST_MESSAGE_URL_CLICK_DETAILS` | List Message URL Click Details | Return one page of clicked links for a MailUp message with each link's total and per-recipient click counts. Full click details are retained for the console data-retention period. Reusing one message across campaigns merges its statistics; clone messages when campaign statistics must stay separate. |
| `MAIL_UP_LIST_MESSAGE_URL_CLICKS` | List Message URL Clicks | Return one page of links with at least one click for a MailUp message, with the click total for each URL or MailUp special-link label. Full click details are retained for the console data-retention period. Reusing one message across campaigns merges its statistics; clone messages when campaign statistics must stay separate. |
| `MAIL_UP_LIST_PERSONALIZATION_ENDPOINTS` | List Personalization Endpoints | Return one page of MailUp personalization endpoints. This operation requires Personalization to be enabled by MailUp for the connected platform account. |
| `MAIL_UP_LIST_PERSONALIZATION_ENDPOINTS_BY_LIST` | List Personalization Endpoints By List | Retrieve all personalization endpoints associated with one MailUp list. This operation requires Personalization to be enabled by MailUp for the connected platform account. |
| `MAIL_UP_LIST_RECIPIENT_ACTIVITY` | List Recipient Activity | Return one page of sent-email delivery, view, click, bounce, or unsubscription statistics for one MailUp recipient. View and click rows are message-level rollups with Count, not individual event timestamps. Delivery details are retained for at most 12 months; reused message IDs aggregate campaigns. |
| `MAIL_UP_LIST_RECIPIENT_BOUNCE_DETAILS` | List Recipient Bounce Details | Return one page of messages that bounced for a MailUp recipient, including message subject, notes, and bounce classification when available. Statistics are limited by the account's configured data-retention period. |
| `MAIL_UP_LIST_RECIPIENT_CLICK_DETAILS` | List Recipient Click Details | Return one page of messages in which a MailUp recipient clicked, including each message's total and per-URL click counts. URL values can be normal URLs or MailUp special-link labels. Full click details are retained for the console data-retention period. |
| `MAIL_UP_LIST_RECIPIENT_GROUPS` | List Recipient Groups | Return one page of groups to which a recipient belongs within one MailUp list. |
| `MAIL_UP_LIST_SOURCE_CONTENTS` | List Source Contents | Return one page of content items from one MailUp content-provider source. |
| `MAIL_UP_LIST_TIME_ZONES` | List Time Zones | Return MailUp's complete unpaged time-zone reference for list settings. Availability follows Console access and the call is subject to MailUp's 5-calls-per-second standard REST limit. |
| `MAIL_UP_REGISTER_TRUSTED_SENDER` | Register Trusted Sender | Register an email address as a trusted sender and begin MailUp's authorization process; registration does not itself guarantee authorization. This feature-gated operation requires Trusted Senders to be enabled by MailUp for the connected platform account. |
| `MAIL_UP_RESET_SMTP_PLUS_ACCOUNT` | Reset SMTP+ Account | Reset an existing SMTP+ user account and return a replacement password. The old password stops working; treat the returned password as a secret and store it securely without logging or exposing it. Never retry automatically after an ambiguous result. This feature-gated operation requires SMTP+ to be enabled by MailUp for the connected platform account. |
| `MAIL_UP_SCHEDULE_DEFERRED_DISPATCH` | Schedule Deferred Email Dispatch | Queue an existing MailUp email campaign for deferred dispatch at the supplied UTC date in exact yyyy-MM-dd HH:mm:ssZ format. Dispatch may consume email credits. Never retry automatically after a rejection or ambiguous result; check the sending state before deciding whether to call again. This action is email-only; use SCHEDULE_DEFERRED_SMS_DISPATCH for SMS. |
| `MAIL_UP_SCHEDULE_DEFERRED_SMS_DISPATCH` | Schedule Deferred SMS Dispatch | Explicitly schedule an existing MailUp SMS sending for a supplied future Date. The dispatch can consume SMS credits when it runs and repeating the request may change or duplicate scheduling; never retry an ambiguous result. Requires SMS entitlement and the 5 calls per second limit applies. |
| `MAIL_UP_SCHEDULE_IMMEDIATE_DISPATCH` | Schedule Immediate Email Dispatch | Irreversibly move an existing inactive MailUp email sending task into the immediate sending queue, where delivery can begin. Never automatically retry after an ambiguous timeout or transport failure; inspect the immediate and pending sending queues first. Use SCHEDULE_IMMEDIATE_SMS_DISPATCH for SMS. |
| `MAIL_UP_SCHEDULE_IMMEDIATE_SMS_DISPATCH` | Schedule Immediate SMS Dispatch | Explicitly queue an existing MailUp SMS sending for immediate dispatch. This requires SMS entitlement and credits, may incur charges, and can duplicate a dispatch if repeated; never retry an ambiguous result. Limit traffic to 5 calls per second. |
| `MAIL_UP_SEND_MAIL_MESSAGE_TO_RECIPIENT` | Send Email Message to Recipient | Irreversibly enqueue, defer, or snapshot an existing MailUp email message for one recipient email address. An omitted or `now` datetime starts queued delivery; a UTC datetime creates an immutable schedule; `undefined` creates an inactive recipient snapshot. This can consume credits and produce duplicate email if repeated. Never retry after an ambiguous timeout, connection loss, or unknown outcome; inspect the sending queues first. |
| `MAIL_UP_SEND_MAIL_MESSAGE_TO_RECIPIENT_IN_GROUP` | Send Email Message to Group | Irreversibly enqueue, defer, or snapshot an existing MailUp email message for recipients in one group. An omitted or `now` datetime starts queued delivery; a UTC datetime creates an immutable schedule; `undefined` creates an inactive recipient snapshot. This can consume credits and deliver duplicate email if repeated. Never automatically retry after an ambiguous timeout or transport failure; inspect the sending queues first. |
| `MAIL_UP_SEND_MAIL_MESSAGE_TO_RECIPIENT_IN_LIST` | Send Email Message to List | Irreversibly enqueue, defer, or snapshot an existing MailUp email message for recipients in one list, optionally including or excluding groups. An omitted or `now` datetime starts queued delivery; a UTC datetime creates an immutable schedule; `undefined` creates an inactive recipient snapshot. This can consume credits and deliver duplicate email if repeated; never automatically retry after an ambiguous timeout or transport failure; inspect the sending queues first. |
| `MAIL_UP_SEND_SMS_MESSAGE_TO_RECIPIENT` | Send SMS Message To Recipient | Irreversibly send an existing MailUp SMS message directly to one Prefix/Number. This requires SMS entitlement, a confirmed sender, and credits; it may incur a charge and duplicate delivery if repeated. Never retry an ambiguous result and limit traffic to 5 calls per second. |
| `MAIL_UP_SEND_SMS_MESSAGE_TO_RECIPIENT_IN_GROUP` | Send SMS Message To Group | Irreversibly send or schedule an existing SMS message to recipients in one MailUp group. MailUp uses the SMS sender configured on the group's list, regardless of the message's Sender field. This requires SMS entitlement and credits, may incur charges, and may duplicate delivery if repeated; never retry an ambiguous result. Limit traffic to 5 calls per second. |
| `MAIL_UP_SEND_SMS_MESSAGE_TO_RECIPIENT_IN_LIST` | Send SMS Message To List | Irreversibly send or schedule an existing SMS message to recipients in one MailUp list. MailUp uses the SMS sender configured on the list, regardless of the message's Sender field. This requires SMS entitlement and credits, may incur charges, and may duplicate delivery if repeated; never retry an ambiguous result. Limit traffic to 5 calls per second. |
| `MAIL_UP_STOP_SENDING` | Stop Email Sending Task | Stop an existing MailUp email sending task and prevent its remaining queued email deliveries. MailUp permits at most 1 combined stop or delete call per 30 seconds. A process-local guard coordinates both actions in this worker only; MailUp remains authoritative across workers and other clients. Never retry automatically after a rejection or ambiguous result. |
| `MAIL_UP_SUBSCRIBE_AUDIENCE_RECIPIENT_TO_GROUP` | Subscribe Audience Recipient To Group | Add an existing MailUp recipient to one group. With confirm_subscription=true, also subscribe the recipient to the group's owning list; with confirm_subscription=false, assign the recipient to the group without changing the list subscription. |
| `MAIL_UP_SUBSCRIBE_RECIPIENT_TO_LIST` | Subscribe Recipient To List | Extend an already-subscribed email recipient's membership to one additional MailUp list. This cannot reactivate an email recipient who is unsubscribed. |
| `MAIL_UP_SUBSCRIBE_SMS_RECIPIENT_TO_GROUP` | Subscribe SMS Recipient To Group | Add an existing SMS recipient to one MailUp group. With confirm_subscription=true, also subscribe the recipient to the group's owning list; with confirm_subscription=false, assign the recipient to the group without changing the list subscription. The account must have SMS service entitlement; observe MailUp's limit of 5 calls per second. |
| `MAIL_UP_SUBSCRIBE_SMS_RECIPIENT_TO_LIST` | Subscribe SMS Recipient To List | Subscribe an existing recipient to the SMS channel of one MailUp list. The account must have SMS entitlement; observe the 5 calls per second limit. |
| `MAIL_UP_UNSUBSCRIBE_AUDIENCE_RECIPIENT_FROM_GROUP` | Unsubscribe Audience Recipient From Group | Remove one recipient from a MailUp group without unsubscribing that recipient from the parent list. |
| `MAIL_UP_UNSUBSCRIBE_AUDIENCE_RECIPIENT_FROM_LISTS` | Unsubscribe Audience Recipient From Lists | Unsubscribe one recipient from every explicitly supplied MailUp list ID in one request. This high-impact bulk subscription change does not delete the recipient record and reports both successful and failed list IDs. |
| `MAIL_UP_UNSUBSCRIBE_RECIPIENT_FROM_LIST` | Unsubscribe Recipient From List | Unsubscribe an existing email recipient from one MailUp list and remove the recipient from every group owned by that list, without deleting the global recipient record or changing the SMS channel. |
| `MAIL_UP_UNSUBSCRIBE_SMS_RECIPIENT_FROM_LIST` | Unsubscribe SMS Recipient From List | Remove one recipient's SMS subscription from one MailUp list without deleting the recipient. Requires SMS entitlement; observe the 5 calls per second limit. |
| `MAIL_UP_UNSUBSCRIBE_SMS_RECIPIENT_FROM_LISTS` | Unsubscribe SMS Recipient From Lists | Remove one recipient's SMS subscriptions from an explicit set of MailUp lists and report per-list results. Requires SMS entitlement; limit traffic to 5 calls per second. |
| `MAIL_UP_UPDATE_AUDIENCE_GROUP` | Update Audience Group | Update explicitly supplied fields of a MailUp group; omitted body fields are not sent. |
| `MAIL_UP_UPDATE_AUDIENCE_RECIPIENT_DETAIL` | Update Audience Recipient Detail | Update explicitly supplied contact and dynamic-field details for a MailUp address-book recipient; omitted fields are not sent. |
| `MAIL_UP_UPDATE_CONTENT_SOURCE` | Update Content Source | Update supplied settings of one MailUp content-provider source. |
| `MAIL_UP_UPDATE_EMAIL_MESSAGE` | Update Email Message | Update an existing MailUp email message's subject and content while preserving omitted settings; this changes the draft and does not send it. |
| `MAIL_UP_UPDATE_LIST` | Update List | Update only supplied settings on one MailUp list. This does not change membership or send messages; access depends on list permissions and standard REST traffic is limited to 5 calls per second. |
| `MAIL_UP_UPDATE_ONLINE_EMAIL_MESSAGE_VISIBILITY` | Update Online Email Visibility | Publish or hide one MailUp email message on the list's online archive; this does not send the message. |
| `MAIL_UP_UPDATE_PERSONALIZATION_ENDPOINT` | Update Personalization Endpoint | Replace the configuration of one MailUp personalization endpoint. This operation requires Personalization to be enabled by MailUp for the connected platform account. |
| `MAIL_UP_UPDATE_SMS_MESSAGE` | Update SMS Message | Replace documented fields of one MailUp SMS draft without sending it. The account needs SMS entitlement; observe MailUp's limit of 5 calls per second. |
| `MAIL_UP_UPDATE_SOURCE_CONTENTS` | Update Source Contents | Add or update content items in one MailUp content-provider source and return the activity ID. |
| `MAIL_UP_UPDATE_TAG` | Update Tag | Replace the name and optionally the enabled state of one tag in a MailUp list. |

## Supported Triggers

None listed.

## Installation and MCP Setup

### Path 1: SDK Installation

#### Path 1, Step 1: Install Composio

Install the Composio SDK, the OpenAI provider, and the OpenAI SDK
```python
pip install composio composio_openai openai
```

```typescript
npm install @composio/core @composio/openai openai
```

#### Path 1, Step 2: Create a Composio session

Initialize Composio with the OpenAI Responses provider and create a session scoped to MailUp
```python
import json
from openai import OpenAI
from composio import Composio
from composio_openai import OpenAIResponsesProvider

composio = Composio(provider=OpenAIResponsesProvider())
client = OpenAI()

session = composio.create(user_id="your-user-id", toolkits=["mail_up"])
tools = session.tools()
```

```typescript
import OpenAI from "openai";
import { Composio } from "@composio/core";
import { OpenAIResponsesProvider } from "@composio/openai";

const composio = new Composio({ provider: new OpenAIResponsesProvider() });
const client = new OpenAI();

const session = await composio.create("your-user-id", { toolkits: ["mail_up"] });
const tools = await session.tools();
```

#### Path 1, Step 3: Run MailUp tools with your agent

Send a request, execute the MailUp tool calls through the session, and print the final answer
```python
response = client.responses.create(
    model="gpt-5.6-sol",
    tools=tools,
    input=[{"role": "user", "content": "List all recipients in my MailUp newsletter list"}],
)

while True:
    tool_calls = [o for o in response.output if o.type == "function_call"]
    if not tool_calls:
        break
    results = composio.provider.handle_tool_calls(response=response, session=session)
    response = client.responses.create(
        model="gpt-5.6-sol",
        tools=tools,
        previous_response_id=response.id,
        input=[
            {"type": "function_call_output", "call_id": call.call_id, "output": json.dumps(results[i])}
            for i, call in enumerate(tool_calls)
        ],
    )

print(response.output_text)
```

```typescript
let response = await client.responses.create({
  model: "gpt-5.6-sol",
  tools,
  input: [{ role: "user", content: "List all recipients in my MailUp newsletter list" }],
});

while (response.output.some((o) => o.type === "function_call")) {
  const outputs = await composio.provider.handleToolCalls(session, response.output);
  response = await client.responses.create({
    model: "gpt-5.6-sol",
    tools,
    previous_response_id: response.id,
    input: outputs,
  });
}

console.log(response.output_text);
```

### Path 2: MCP Server Setup

#### Path 2, Step 1: Install Composio

Install the Composio SDK and your agent framework
```python
pip install composio claude-agent-sdk
```

```typescript
npm install @composio/core ai @ai-sdk/mcp @ai-sdk/openai
```

#### Path 2, Step 2: Create a session with MCP enabled

Create a session scoped to MailUp and read its MCP URL and headers
```python
from composio import Composio

composio = Composio()
session = composio.create(user_id="your-user-id", toolkits=["mail_up"], mcp=True)
```

```typescript
import { Composio } from "@composio/core";

const composio = new Composio();
const { mcp } = await composio.create("your-user-id", {
  toolkits: ["mail_up"],
  mcp: true,
});
```

#### Path 2, Step 3: Connect your agent to the MCP server

Pass the session's MCP URL and headers to your agent and run a MailUp request
```python
import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions, AssistantMessage, TextBlock

options = ClaudeAgentOptions(
    mcp_servers={
        "composio": {
            "type": "http",
            "url": session.mcp.url,
            "headers": session.mcp.headers,
        }
    },
    system_prompt="You are a helpful assistant with access to MailUp tools.",
    tools=[],
    allowed_tools=["mcp__composio__*"],
)

async def main():
    async with ClaudeSDKClient(options=options) as client:
        await client.query("List all recipients in my MailUp newsletter list")
        async for message in client.receive_response():
            if isinstance(message, AssistantMessage):
                for block in message.content:
                    if isinstance(block, TextBlock):
                        print(block.text)

asyncio.run(main())
```

```typescript
import { createMCPClient } from "@ai-sdk/mcp";
import { openai } from "@ai-sdk/openai";
import { generateText, stepCountIs } from "ai";

const client = await createMCPClient({
  transport: { type: "http", url: mcp.url, headers: mcp.headers },
});

const { text } = await generateText({
  model: openai("gpt-5.6-sol"),
  tools: await client.tools(),
  prompt: "List all recipients in my MailUp newsletter list",
  stopWhen: stepCountIs(10),
});

console.log(text);
await client.close();
```

## Why Use Composio?

### 1. AI Native MailUp Integration

- Supports both MailUp MCP and direct API based integrations
- Structured, LLM-friendly schemas for reliable tool execution
- Rich coverage for reading, writing, and querying your MailUp data

### 2. Managed Auth

- Built-in OAuth handling with automatic token refresh and rotation
- Central place to manage, scope, and revoke MailUp access
- Per user and per environment credentials instead of hard-coded keys

### 3. Agent Optimized Design

- Tools are tuned using real error and success rates to improve reliability over time
- Comprehensive execution logs so you always know what ran, when, and on whose behalf

### 4. Enterprise Grade Security

- Fine-grained RBAC so you control which agents and users can access MailUp
- Scoped, least privilege access to MailUp resources
- Full audit trail of agent actions to support review and compliance

## Use MailUp with any AI Agent Framework

Choose a framework you want to connect MailUp with:

- [ChatGPT](https://composio.dev/toolkits/mail_up/framework/chatgpt)
- [Claude Cowork](https://composio.dev/toolkits/mail_up/framework/claude-cowork)
- [Hermes](https://composio.dev/toolkits/mail_up/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/mail_up/framework/atomic-agent)

## Related Toolkits

- [Reddit](https://composio.dev/toolkits/reddit) - Reddit is a social news platform with thriving user-driven communities (subreddits). It's the go-to place for discussion, content sharing, and viral marketing.
- [Facebook](https://composio.dev/toolkits/facebook) - Facebook is a social media and advertising platform for businesses and creators. It helps you connect, share, and manage content across your public Facebook Pages.
- [Linkedin](https://composio.dev/toolkits/linkedin) - LinkedIn is a professional networking platform for connecting, sharing content, and engaging with business opportunities. It's the go-to place for building your professional brand and unlocking new career connections.
- [Active campaign](https://composio.dev/toolkits/active_campaign) - ActiveCampaign is a marketing automation and CRM platform for managing email campaigns, sales pipelines, and customer segmentation. It helps businesses engage customers and drive growth through smart automation and targeted outreach.
- [ActiveTrail](https://composio.dev/toolkits/active_trail) - ActiveTrail is a user-friendly email marketing and automation platform. It helps you reach subscribers and automate campaigns with ease.
- [Adobe Marketing Agent MCP](https://composio.dev/toolkits/adobe_marketing_agent_mcp) - Adobe Marketing Agent MCP is Adobe's hosted MCP service that exposes marketing context, preferences, and agent capabilities. Use it to provide agents with campaign, audience, and analytics context via a managed integration.
- [Ahrefs](https://composio.dev/toolkits/ahrefs) - Ahrefs is an SEO and marketing platform for site audits, keyword research, and competitor insights. It helps you improve search rankings and drive organic traffic.
- [AimTell](https://composio.dev/toolkits/aimtell) - AimTell is a web push notification platform for managing websites, subscribers, campaigns, segments, and delivery analytics. Use it to send targeted browser notifications and measure engagement across your web push campaigns.
- [Amcards](https://composio.dev/toolkits/amcards) - AMCards lets you create and mail personalized greeting cards online. Build stronger customer relationships with easy, automated card campaigns.
- [AWeber](https://composio.dev/toolkits/aweber) - AWeber is an email marketing platform for creating campaigns, lists, and landing pages. It helps businesses automate email outreach and measure subscriber engagement.
- [Beamer](https://composio.dev/toolkits/beamer) - Beamer is a news and changelog platform for in-app announcements and feature updates. It helps companies boost user engagement by sharing news where users are most active.
- [Beehiiv](https://composio.dev/toolkits/beehiiv) - Beehiiv is a newsletter platform for creating and managing publications and subscribers. It helps grow audience engagement and monetize your mailing list.
- [Benchmark email](https://composio.dev/toolkits/benchmark_email) - Benchmark Email is a platform for creating, sending, and tracking email campaigns. It's built to help you engage audiences and analyze results—all in one place.
- [Bigmailer](https://composio.dev/toolkits/bigmailer) - BigMailer is an email marketing platform for managing multiple brands with white-labeling and automation. It helps teams streamline campaigns and simplify integration with Amazon SES.
- [Bitly](https://composio.dev/toolkits/bitly) - Bitly is a link management platform for shortening, customizing, sharing, and tracking links and QR codes. It helps teams create branded links and measure engagement across campaigns.
- [BlueFox Email](https://composio.dev/toolkits/bluefox_email) - BlueFox Email is an email API for managing contacts, subscriber lists, and sending transactional and triggered messages. Use it to reliably send transactional and triggered emails and manage subscribers at scale.
- [Brandfetch](https://composio.dev/toolkits/brandfetch) - Brandfetch is an API that delivers company logos, colors, and visual branding assets. It helps marketers and developers keep brand visuals consistent everywhere.
- [Braze](https://composio.dev/toolkits/braze) - Braze is a customer engagement platform for managing user data, messaging, campaigns, and analytics. Use it to deliver targeted, multi-channel messaging and analyze campaign performance.
- [Buffer](https://composio.dev/toolkits/buffer) - Buffer is a social media management platform for planning, creating, scheduling, and publishing posts across connected channels. It helps teams keep content organized and publish consistently without jumping between social apps.
- [BulkPublish](https://composio.dev/toolkits/bulkpublish) - BulkPublish is a social media publishing platform for managing scheduled content across multiple channels. It helps teams plan campaigns, publish consistently, and track performance in one place.

## Frequently Asked Questions

### Do I need my own developer credentials to use MailUp with Composio?

Yes, MailUp requires you to configure your own OAuth credentials. Once set up, Composio handles token storage, refresh, and lifecycle management for you.

### Can I use multiple toolkits together?

Yes! Composio's Tool Router enables agents to use multiple toolkits. [Learn more](https://docs.composio.dev/tool-router/overview).

### Is Composio secure?

Composio is SOC 2 and ISO 27001 compliant with all data encrypted in transit and at rest. [Learn more](https://trust.composio.dev).

### What if the API changes?

Composio maintains and updates all toolkit integrations automatically, so your agents always work with the latest API versions.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)