Version approved, tested email templates
Connect
SPIRITT
SendGridSendGrid
Run email from end to end
SPIRITT turns campaign briefs into tested sends, releases transactional templates, and investigates delivery failures. It builds and runs the contact, consent, and delivery workflows behind every send.
What you can do with SendGrid.
Campaigns that reach launch
Carry approved briefs through audience preparation, test emails, scheduling, and results checks without losing the work at a draft handoff.
Controlled template releases
Create and test transactional template versions, activate the intended release, and keep the previous version ready for recovery.
Accountable email operations
Reconcile contact updates, verify unsubscribe changes, and trace delivery failures to a named resolution with a searchable event history.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Create a SPIRITT workspace for the transactional email, marketing campaign, or delivery operation you want to delegate.
02
Connect SendGrid
Connect SendGrid using an API key with permissions for the templates, contacts, sending, or account resources your mission needs.
03
Delegate an outcome
Hand over a campaign launch, template release, or recurring email workflow. SPIRITT builds the system, executes the work, and checks the results.
Hand over a mission.
Choose a mission. Make it yours.
Put SendGrid to work.
Give every send an operator
Questions
SendGrid, with SPIRITT.
01Can SPIRITT launch SendGrid campaigns, not just prepare drafts?+
Yes. SPIRITT can create and update Single Sends, send test marketing emails, and schedule delivery. It can also create, schedule, and send campaigns where those features are available in your account. After launch, it checks send status and statistics rather than treating scheduling as proof of delivery.
02How does a transactional template release work?+
SPIRITT can create and edit template versions, test messages with sample data, and activate the intended version. Activation makes that version the template's default. Your application must use the correct template and supply its required data; a release register preserves the previous version for recovery.
03What access does SendGrid require?+
The connection uses a SendGrid API key with permissions for the delegated operations. Sending, contact maintenance, and account administration can require different scopes. SPIRITT works within those scopes and your account's available features; dedicated IP and subuser missions also depend on access to those resources.
04Can contact updates and unsubscribe requests run continuously?+
Yes. SPIRITT can resolve contacts through email lookup or search, submit updates, follow import processing status, and reconcile completed records. It can retrieve group and global suppressions, apply opt-outs, and verify the resulting state. Request history stays separate from current preferences, and routine contact synchronization preserves opt-outs.
05Can SPIRITT build a delivery console across other tools?+
Yes. It can combine SendGrid message activity with HubSpot tickets, a Supabase event ledger, and Slack ownership updates. SPIRITT can configure an Event Webhook, enable signature verification, retrieve the signing public key, and test delivery to the ledger. The console can connect a failed message to its investigation and verified resolution.
06How is SendGrid email handling different from connecting an inbox?+
SendGrid supports application email, marketing sends, templates, and delivery events rather than a general mailbox workflow. Its Inbound Parse settings can route incoming email for a configured receiving domain to a custom workflow, with the required domain and DNS setup. That is distinct from searching or managing an existing Gmail or Outlook inbox.