Integration reference

Gmail Trigger and Action reference

Start from received, sent, labeled, searched, or attachment email events and automate common message operations.

Authentication

Connect the Google account that owns the mailbox through OAuth.

• Trigger account type: oauth2; reconnect by oauth.
• Action connection type: oauth2; available modes: Connected Gmail 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

Base Trigger authorization requests: openid, email, profile, https://www.googleapis.com/auth/gmail.readonly.

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 Gmail as a Trigger

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

• New Attachment Received
• New Email Matching Search
• New Email Received
• New Labeled Email
• New Sent Email

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 Gmail Actions

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

• Send Email
• Create Draft
• Reply to Message
• Modify Message Labels
• Move Message to Trash
• Custom API Request

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 Gmail Trigger definition.
2. Create a Workflow with that Source as its Trigger.
3. Add the required Gmail 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 Gmail.

Troubleshooting Gmail

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

• Search and label filters reduce noise before the Workflow starts.
• Attachment and body fields may be large; inspect real Trigger previews before mapping them downstream.

Next

• Explore Gmail integrations
• Trigger configuration
• Action configuration
• Data mapping
• Error handling
• Authentication and permissions
• All automation integrations