Sendgrid Skills

**Quick judgement**: A focused, practical integration for SendGrid that cleanly routes email-related tasks to appropriate sub-skills. Well-suited for transactional email sending and programmatic email ingestion, but relies heavily on correct external configuration (SendGrid account, API key, webhooks). **Strengths & fit** - Good fit for: apps that already use or plan to use SendGrid for transactional mail and need both outbound and inbound flows within OpenClaw. - Works best when you have stable SendGrid infrastructure: API key configured as `SENDGRID_API_KEY`, domains and DNS set up, and Inbound Parse Webhook configured. - The routing abstraction (send-email vs sendgrid-inbound) simplifies how agents/systems decide which email operation to invoke. **Key risks / limitations** - **Security & abuse risk**: Mismanaged API keys or insufficient access control can allow unauthorized email sending (spam, phishing) from your domain. Emails may contain PII; ensure encryption at rest and careful logging. - **Configuration fragility**: Requires correct SendGrid setup (DNS, MX, webhooks). Misconfiguration can lead to silent failures (e.g., inbound emails not reaching your handler). - **Scope of functionality**: Focused on transactional and inbound parse—marketing campaigns, bulk sends, and SMTP relay are explicitly *out of scope* and must be handled via other tools/services. - **Operational reliability**: Overall robustness depends on SendGrid’s uptime and network conditions; the page doesn’t document retries, error classification, or fallback strategies in the skill itself. **Recommended scenarios** - You need **transactional email** from agents or workflows (password resets, notifications, receipts) and want a standard, well-known provider. - You want to **receive and parse incoming emails** (e.g., support@, reply-to comment threads) programmatically via SendGrid’s Inbound Parse and surface them to your agents. - You’re consolidating email logic behind a single OpenClaw abstraction so that higher-level logic doesn’t need to know SendGrid’s API details. Avoid or augment this skill if you need advanced marketing automation, bulk campaign management, or strict compliance and auditing controls that go beyond basic SendGrid integration.