Automate SendGrid Marketing Campaigns and Contact Management

SendGrid Automation via Rube MCP automates SendGrid email delivery - marketing campaigns (Single Sends), contact and list management, sender identity setup, and email analytics - through Composio's SendGrid toolkit. It requires Rube MCP connected (https://rube.app/mcp, no API keys needed) with an active SendGrid connection via RUBE_MANAGE_CONNECTIONS, and RUBE_SEARCH_TOOLS must be called first for current tool schemas.

Use it across five workflows: creating and sending marketing campaigns (SENDGRID_CREATE_SINGLE_SEND, requiring either a suppression_group_id or custom_unsubscribe_url for compliance, and a verified sender checked via SENDGRID_GET_ALL_SENDER_IDENTITIES), managing contacts and lists (SENDGRID_ADD_OR_UPDATE_A_CONTACT, SENDGRID_IMPORT_CONTACTS for bulk CSV, SENDGRID_REMOVE_LIST_AND_OPTIONAL_CONTACTS which is irreversible and needs explicit confirmation, and list names which must be unique - duplicates return a 400 error), managing sender identities (SENDGRID_CREATE_A_SENDER_IDENTITY requiring a physical address for CAN-SPAM compliance, up to 100 sender identities per account, avoiding strict-DMARC domains like gmail.com as from-addresses), viewing email statistics/activity (SENDGRID_RETRIEVE_GLOBAL_EMAIL_STATISTICS, returned nested under details[].stats[0].metrics rather than flat; SENDGRID_FILTER_ALL_MESSAGES which requires a paid 30-day activity history add-on; category-level stats limited to the previous 13 months and max 10 categories per request), and managing suppression groups for unsubscribe compliance.

All nested parameters use double-underscore notation (e.g. email__config__subject, from__email). A key gotcha: setting send_at on SENDGRID_CREATE_SINGLE_SEND only prepopulates a UI date field and does not schedule the send - actual scheduling requires the separate Schedule endpoint. Contact operations (ADD_OR_UPDATE_A_CONTACT, IMPORT_CONTACTS) are asynchronous, returning HTTP 202 with a job_id, and contacts may take 10-30 seconds to appear - always verify with a follow-up lookup rather than assuming immediate consistency. Bulk contact upserts are capped at 30,000 contacts or 6MB per request.

ID resolution is a recurring pattern: list name to list_id via SENDGRID_RETRIEVE_ALL_LISTS, sender name to sender_id via SENDGRID_GET_ALL_SENDER_IDENTITIES, contact email to contact_id via SENDGRID_GET_CONTACTS_BY_EMAILS. Pagination style also varies by endpoint: SENDGRID_RETRIEVE_ALL_LISTS uses token-based paging (page_token, page_size up to 1000), while SENDGRID_RETRIEVE_GLOBAL_EMAIL_STATISTICS uses offset-based paging (limit up to 500, offset). The legacy SENDGRID_ADD_A_SINGLE_RECIPIENT_TO_A_LIST tool takes a Base64-encoded lowercase-email recipient_id rather than a plain identifier. ID formats vary by resource: marketing list and contact IDs are UUIDs, legacy list IDs are integers and must not be mixed with Marketing API endpoints, sender identity IDs are integers, and dynamic template IDs start with "d-" while legacy templates are UUIDs. Some tools use the legacy Contact Database API (/v3/contactdb/), which can return 403 on newer accounts - Marketing API tools (SENDGRID_ADD_OR_UPDATE_A_CONTACT, SENDGRID_RETRIEVE_ALL_LISTS, SENDGRID_CREATE_SINGLE_SEND) are preferred. Rate limits return HTTP 429 with a Retry-After header, and CSV activity exports are limited to one request per 12 hours with a 3-day link expiry.

Marketing operations teams automating SendGrid campaigns, contact/list management, sender verification, and delivery analytics through an MCP-connected agent, with the async-timing, ID-format, and legacy-vs-Marketing-API gotchas already documented to avoid silent failures. Suppression groups also matter for read accuracy: suppressed addresses stay undeliverable even when present on a marketing list, so a campaign's actual send count can legitimately be lower than the target list's contact count.