SendGrid
Transactional email send + delivery events
SendGrid is the transactional email infrastructure most companies eventually need, order receipts, password resets, account confirmations, all the messages that have to land in the right inbox. Tiny Command exposes three triggers that close the loop on delivery: Email Delivered (it reached the inbox or a server accepted it), Email Opened (the recipient opened it), Email Link Clicked (they clicked a link in it). Eleven actions cover both transactional sending and the audience side: Send Email (custom HTML/text), Send Template Email (using a SendGrid dynamic template ID), Add Contact, Get Contact, List Contacts, Delete Contact, Create List, List Lists, Update List, Delete List, Get List. The integration authorizes with a SendGrid API key. Common pattern: Stripe Checkout Completed fires Send Template Email with the order receipt template, the SendGrid Email Delivered trigger writes a delivery confirmation back to a Sheet, and Email Opened triggers a downstream nurture workflow for engagement scoring.
Workflows start when SendGrid does.
3 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
Fires when an email is successfully delivered to the recipient mail server via SendGrid. Use to reconcile sends or to advance a sequence once the previous mail has actually landed.
Fires when a recipient clicks a link in an email sent via SendGrid. Common use: lead-scoring, sales-rep alerts, or branch automation based on engagement.
Fires when a recipient opens an email sent via SendGrid. Note that Apple Mail Privacy Protection prefetches images, so open events from Apple Mail users are unreliable.
Do anything SendGrid can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Add or Update Contact | Adds or updates (upserts) a contact in SendGrid marketing with email, name, custom fields, and list memberships. Used to keep your audience in sync with your CRM or product DB. |
| Create List | Creates a new contact list in SendGrid. Use to spin up campaign-scoped audiences from your CRM segments. |
| Delete Contact | Deletes one or more SendGrid contacts by ID. Used for GDPR/CCPA right-to-delete requests or for unsubscribe cleanup. |
| Delete List | Deletes a SendGrid contact list (the contacts themselves are not deleted, just removed from the list). Use to retire one-off campaign audiences. |
| Find Contact by Email | Searches for a SendGrid contact by email and returns the record with custom fields and list memberships. The standard upsert lookup before deciding to add or update. |
| Get List | Returns a SendGrid contact list by ID with name and contact count. Use to render a list-detail view or to validate a list reference. |
| Search Contacts | Searches contacts using SGQL (SendGrid Query Language), which supports filters on email, custom fields, and list membership. Useful for building dynamic audiences. |
| List All Lists | Returns all contact lists in SendGrid marketing. Used to populate a list picker. |
| Send Email | Sends a transactional email via SendGrid with from, to, subject, HTML/plain content, and optional CC/BCC/attachments/reply-to. The bread-and-butter SendGrid action. |
| Send Template Email | Sends an email using a SendGrid dynamic template, passing in the Handlebars data substitutions. Use templates so design lives in SendGrid and code only ships data. |
| Update List | Updates a SendGrid contact list's name. Use to keep list names aligned with your campaign naming convention. |
Pre-built SendGrid workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect SendGrid once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every SendGrid field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the SendGrid integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect SendGrid to Tiny Command?
What SendGrid triggers does Tiny Command support?
What SendGrid actions can I run from a workflow?
Is the SendGrid integration real-time?
Do I need to write code to use SendGrid with Tiny Command?
How much does the SendGrid integration cost?
More marketing apps people connect.
Same category as SendGrid, ordered by how often teams pair them. Hover the carousel to pause.
Do more with SendGrid.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
