Integration reference

SendGrid Trigger and Action reference

Send email through SendGrid and start Workflows from signed delivery, engagement and account events.

12 Triggers9 ActionsManifests: Trigger v— · Action v1

Authentication

Connect a scoped SendGrid API key. Identity needs user.username.read; managed webhooks need Event Webhook settings read/create/update/delete permissions. Sending needs mail.send. FastHook stores the key encrypted. This integration uses an API key, not OAuth.

  • Trigger account type: api_key; reconnect by replace_credentials.
  • Action connection type: api_key; available modes: Connected account.

Create or reuse the account from a Trigger or Action dialog, or manage it under Settings → Connected accounts. See Authentication and permissions for scopes and access diagnostics, or Connected accounts for reuse, reconnect, revocation, and credential rotation.

Scopes and permissions

The Trigger manifest does not declare a fixed base OAuth scope list. Installation access, API credentials, or the selected event configuration can still control available resources.

Operation-specific requirements appear in the tables below. Custom event selections can add scopes dynamically, so the current Trigger or Action dialog remains authoritative for the exact consent request.

Use SendGrid as a Trigger

The current provider manifest contains 12 available Trigger definitions. Representative definitions include:

  • Email Delivered
  • Email Bounced
  • Email Opened
  • Email Link Clicked
View all 12 available Trigger definitions
TriggerManifest keyDeliveryAdditional scopes
Email Processedsendgrid.processed.instantinstantNone declared
Email Droppedsendgrid.dropped.instantinstantNone declared
Email Deliveredsendgrid.delivered.instantinstantNone declared
Email Deferredsendgrid.deferred.instantinstantNone declared
Email Bouncedsendgrid.bounce.instantinstantNone declared
Email Openedsendgrid.open.instantinstantNone declared
Email Link Clickedsendgrid.click.instantinstantNone declared
Spam Reportedsendgrid.spamreport.instantinstantNone declared
Recipient Unsubscribedsendgrid.unsubscribe.instantinstantNone declared
Recipient Unsubscribed from Groupsendgrid.group_unsubscribe.instantinstantNone declared
Recipient Resubscribed to Groupsendgrid.group_resubscribe.instantinstantNone declared
Account Status Changedsendgrid.account_status_change.instantinstantNone declared

Choose the narrowest event definition that fits the Workflow. Configure provider-specific resource and event filters in the Source dialog before adding broader Workflow Filters.

Use SendGrid Actions

The current Action manifest contains 9 operations. Representative Actions include:

  • Send Email
  • Get Credit Balance
  • List Verified Senders
  • List Event Webhooks
View all 9 available Action definitions
ActionManifest keyAccess and authManifest rate limit
Send Emailsendgrid.send_emailNone declared
FastHook-managed account
1/second
Create Batch IDsendgrid.create_batch_idNone declared
FastHook-managed account
1/second
Validate Batch IDsendgrid.validate_batch_idNone declared
FastHook-managed account
1/second
Get Account Identitysendgrid.get_accountNone declared
FastHook-managed account
1/second
Get Credit Balancesendgrid.get_creditsNone declared
FastHook-managed account
1/second
Get API Key Permissionssendgrid.get_scopesNone declared
FastHook-managed account
1/second
List Verified Senderssendgrid.list_verified_sendersNone declared
FastHook-managed account
1/second
List Event Webhookssendgrid.list_event_webhooksNone declared
FastHook-managed account
1/second
Custom API Requestsendgrid.custom_api_requestNone declared
FastHook-managed account
1/second

The Action editor reads its required permissions, fields, remote resource pickers, output schema, and rate limit from the provider manifest. Available fields can change with the selected operation and authentication mode.

Build a Workflow

  1. Create a Source using a SendGrid Trigger definition.
  2. Create a Workflow with that Source as its Trigger.
  3. Add the required SendGrid Action and select the connected account.
  4. Map Trigger or earlier-Step data into the Action fields with the field picker.
  5. Add a Filter, Paths, Delay, or Transformation when the route needs it.
  6. Activate the Workflow, produce a controlled event, and verify the run in Audit and in SendGrid.

Troubleshooting SendGrid

The account is missing or cannot be selected
Confirm the active FastHook team, provider, account status, and authentication mode. A disabled or revoked account cannot execute an Action.
A resource picker is empty
Verify that the connected provider identity can access the resource itself. OAuth consent does not add workspace, repository, channel, drive, project, base, or record permissions.
The editor asks for additional scopes
Reconnect the same account from the affected Trigger or Action so FastHook can request its current manifest scopes. Then reopen the editor and select the resource again.
An active Workflow returns 401, 403, or a permission error
Compare the selected operation’s access requirements below with the account recorded in Audit. Check provider-side membership and object access before repeating the Action.
The provider returns 429 or a temporary 5xx
Inspect the Step attempt and retryability in Audit. FastHook can retry temporary failures, but provider quotas and idempotency rules still apply.

Provider-specific checks

  • Email Delivered means acceptance by the recipient mail server. It does not prove inbox placement or reading. Open and click events require the sender's tracking settings.
  • FastHook creates a signed Event Webhook and verifies P-256 ECDSA against the timestamp and exact request body. It accepts up to 1,000 events and 2 MiB per request, with a separate deduplication receipt for each event.
  • An eligible Email API plan and verified sender are required for real email sending. Sample data verifies mappings only; it is not evidence that a message was delivered.
  • Mail Send accepts the official structured body, including base64 attachments. Only the global api.sendgrid.com endpoint is supported; EU regional subusers and Inbound Parse are not included.
  • Disconnect removes the owned webhook and FastHook credentials. Revoke the API key separately in SendGrid if it should no longer be usable elsewhere.

Next