sendgrid-automation
Automate SendGrid email operations including sending emails, managing contacts/lists, sender identities, templates, and analytics via Rube MCP (Composio). Always search tools first for current schemas.
What this skill does
# SendGrid Automation via Rube MCP Automate SendGrid email delivery workflows including marketing campaigns (Single Sends), contact and list management, sender identity setup, and email analytics through Composio's SendGrid toolkit. ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) - Active SendGrid connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `sendgrid` - Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas ## Setup **Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. 1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds 2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `sendgrid` 3. If connection is not ACTIVE, follow the returned auth link to complete SendGrid API key authentication 4. Confirm connection status shows ACTIVE before running any workflows ## Core Workflows ### 1. Create and Send Marketing Campaigns (Single Sends) **When to use**: User wants to create and send a marketing email campaign to a contact list or segment. **Tool sequence**: 1. `SENDGRID_RETRIEVE_ALL_LISTS` - List available marketing lists to target [Prerequisite] 2. `SENDGRID_CREATE_A_LIST` - Create a new list if needed [Optional] 3. `SENDGRID_ADD_OR_UPDATE_A_CONTACT` - Add contacts to the list [Optional] 4. `SENDGRID_GET_ALL_SENDER_IDENTITIES` - Get verified sender ID [Prerequisite] 5. `SENDGRID_CREATE_SINGLE_SEND` - Create the campaign with content, sender, and recipients [Required] **Key parameters for SENDGRID_CREATE_SINGLE_SEND**: - `name`: Campaign name (required) - `email__config__subject`: Email subject line - `email__config__html__content`: HTML body content - `email__config__plain__content`: Plain text version - `email__config__sender__id`: Verified sender identity ID - `email__config__design__id`: Use instead of html_content for pre-built designs - `send__to__list__ids`: Array of list UUIDs to send to - `send__to__segment__ids`: Array of segment UUIDs - `send__to__all`: true to send to all contacts - `email__config__suppression__group__id` or `email__config__custom__unsubscribe__url`: One required for compliance **Pitfalls**: - Setting `send_at` on CREATE does NOT schedule the send; it only prepopulates the UI date; use the Schedule endpoint separately - `send_at: "now"` is only valid with the Schedule endpoint, not CREATE - Must provide either `suppression_group_id` or `custom_unsubscribe_url` for unsubscribe compliance - Sender must be verified before use; check with `SENDGRID_GET_ALL_SENDER_IDENTITIES` - Nested params use double-underscore notation (e.g., `email__config__subject`) ### 2. Manage Contacts and Lists **When to use**: User wants to create contact lists, add/update contacts, search for contacts, or remove contacts from lists. **Tool sequence**: 1. `SENDGRID_RETRIEVE_ALL_LISTS` - List all marketing lists [Required] 2. `SENDGRID_CREATE_A_LIST` - Create a new contact list [Optional] 3. `SENDGRID_GET_A_LIST_BY_ID` - Get list details and sample contacts [Optional] 4. `SENDGRID_ADD_OR_UPDATE_A_CONTACT` - Upsert contacts with list association [Required] 5. `SENDGRID_GET_CONTACTS_BY_EMAILS` - Look up contacts by email [Optional] 6. `SENDGRID_GET_CONTACTS_BY_IDENTIFIERS` - Look up contacts by email, phone, or external ID [Optional] 7. `SENDGRID_GET_LIST_CONTACT_COUNT` - Verify contact count after operations [Optional] 8. `SENDGRID_REMOVE_CONTACTS_FROM_A_LIST` - Remove contacts from a list without deleting [Optional] 9. `SENDGRID_REMOVE_LIST_AND_OPTIONAL_CONTACTS` - Delete an entire list [Optional] 10. `SENDGRID_IMPORT_CONTACTS` - Bulk import from CSV [Optional] **Key parameters for SENDGRID_ADD_OR_UPDATE_A_CONTACT**: - `contacts`: Array of contact objects (max 30,000 or 6MB), each with at least one identifier: `email`, `phone_number_id`, `external_id`, or `anonymous_id` (required) - `list_ids`: Array of list UUID strings to associate contacts with **Pitfalls**: - `SENDGRID_ADD_OR_UPDATE_A_CONTACT` is asynchronous; returns 202 with `job_id`; contacts may take 10-30 seconds to appear - List IDs are UUIDs (e.g., "ca7a3796-e8a8-4029-9ccb-df8937940562"), not integers - List names must be unique; duplicate names cause 400 errors - `SENDGRID_ADD_A_SINGLE_RECIPIENT_TO_A_LIST` uses the legacy API; prefer `SENDGRID_ADD_OR_UPDATE_A_CONTACT` with `list_ids` - `SENDGRID_REMOVE_LIST_AND_OPTIONAL_CONTACTS` is irreversible; require explicit user confirmation - Email addresses are automatically lowercased by SendGrid ### 3. Manage Sender Identities **When to use**: User wants to set up or view sender identities (From addresses) for sending emails. **Tool sequence**: 1. `SENDGRID_GET_ALL_SENDER_IDENTITIES` - List all existing sender identities [Required] 2. `SENDGRID_CREATE_A_SENDER_IDENTITY` - Create a new sender identity [Optional] 3. `SENDGRID_VIEW_A_SENDER_IDENTITY` - View details for a specific sender [Optional] 4. `SENDGRID_UPDATE_A_SENDER_IDENTITY` - Update sender details [Optional] 5. `SENDGRID_CREATE_VERIFIED_SENDER_REQUEST` - Create and verify a new sender [Optional] 6. `SENDGRID_AUTHENTICATE_A_DOMAIN` - Set up domain authentication for auto-verification [Optional] **Key parameters for SENDGRID_CREATE_A_SENDER_IDENTITY**: - `from__email`: From email address (required) - `from__name`: Display name (required) - `reply__to__email`: Reply-to address (required) - `nickname`: Internal identifier (required) - `address`, `city`, `country`: Physical address for CAN-SPAM compliance (required) **Pitfalls**: - New senders must be verified before use; if domain is not authenticated, a verification email is sent - Up to 100 unique sender identities per account - Avoid using domains with strict DMARC policies (gmail.com, yahoo.com) as from addresses - `SENDGRID_CREATE_VERIFIED_SENDER_REQUEST` sends a verification email; sender is unusable until verified ### 4. View Email Statistics and Activity **When to use**: User wants to review email delivery stats, bounce rates, open/click metrics, or message activity. **Tool sequence**: 1. `SENDGRID_RETRIEVE_GLOBAL_EMAIL_STATISTICS` - Get account-wide delivery metrics [Required] 2. `SENDGRID_GET_ALL_CATEGORIES` - Discover available categories for filtering [Optional] 3. `SENDGRID_RETRIEVE_EMAIL_STATISTICS_FOR_CATEGORIES` - Get stats broken down by category [Optional] 4. `SENDGRID_FILTER_ALL_MESSAGES` - Search email activity feed by recipient, status, or date [Optional] 5. `SENDGRID_FILTER_MESSAGES_BY_MESSAGE_ID` - Get detailed events for a specific message [Optional] 6. `SENDGRID_REQUEST_CSV` - Export activity data as CSV for large datasets [Optional] 7. `SENDGRID_DOWNLOAD_CSV` - Download the exported CSV file [Optional] **Key parameters for SENDGRID_RETRIEVE_GLOBAL_EMAIL_STATISTICS**: - `start_date`: Start date YYYY-MM-DD (required) - `end_date`: End date YYYY-MM-DD - `aggregated_by`: "day", "week", or "month" - `limit` / `offset`: Pagination (default 500) **Key parameters for SENDGRID_FILTER_ALL_MESSAGES**: - `query`: SQL-like query string, e.g., `status="delivered"`, `to_email="[email protected]"`, date ranges with `BETWEEN TIMESTAMP` - `limit`: 1-1000 (default 10) **Pitfalls**: - `SENDGRID_FILTER_ALL_MESSAGES` requires the "30 Days Additional Email Activity History" paid add-on; returns 403 without it - Global statistics are nested under `details[].stats[0].metrics`, not a flat structure - Category statistics are only available for the previous 13 months - Maximum 10 categories per request in `SENDGRID_RETRIEVE_EMAIL_STATISTICS_FOR_CATEGORIES` - CSV export is limited to one request per 12 hours; link expires after 3 days ### 5. Manage Suppressions **When to use**: User wants to check or manage unsubscribe groups for email compliance. **Tool sequence**: 1. `SENDGRID_GET_SUPPRESSION_GROUPS` - List all suppression groups [Required] 2. `SENDGRID_RETRIEVE_ALL_SUPPRESSION_GROUPS_FOR_AN_EMAIL_ADDRESS` - Check suppression status for a specific email [Op
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.