sendgrid-integration_skill

Overview

This skill integrates SendGrid to manage email campaigns, suppression lists, contacts, and templates through a unified interface. It leverages Membrane to handle authentication and provides both pre-built actions and a proxy for raw API calls. Use it to list, create, update, or delete SendGrid resources without handling API keys locally.

How this skill works

The skill calls SendGrid endpoints via the Membrane CLI or API connector. Membrane manages the OAuth/auth lifecycle, pagination, and error handling so actions like listing bounces, sending email, or updating contacts are simple commands. When a needed action is not available, the skill proxies arbitrary HTTP requests to SendGrid while injecting authentication and base URL automatically.

When to use it

• Manage suppression lists (bounces, blocks, spam reports, global unsubscribes).
• Create, list, or retrieve marketing contact lists and individual contacts.
• Create, fetch, or send using transactional templates.
• Send transactional or marketing emails through SendGrid without storing credentials locally.
• Run raw or custom SendGrid endpoints when pre-built actions do not cover a use case.

Best practices

• Use Membrane pre-built actions before crafting custom API calls to benefit from built-in pagination and error handling.
• Never ask users for SendGrid API keys — create a Membrane connection so credentials are handled server-side.
• List actions with intent (QUERY, MUTATE) to discover available operations and required input schemas.
• Prefer actions like add-or-update-contacts and send-email-with-template to reduce token usage and complexity.
• Use the proxy request feature only for endpoints not exposed as actions; include proper headers and query params using Membrane flags.

Example use cases

• Remove a bounced or blocked email from the suppression list to restore deliverability.
• Create a marketing contact list and bulk add contacts or update existing profiles.
• Search contacts using SendGrid Query Language to segment users for a campaign.
• Send a transactional email using a dynamic template and template data via the send-email-with-template action.
• Retrieve spam reports or global unsubscribes before launching a new campaign to reduce complaints.