Integrations
Gmail
Send an email or create a draft from workflow data.
What this guide covers
- A Google account through OAuth for the Gmail mailbox that should send or store drafts.
- 2 supported workflow actions.
- The connection can act only within the authorized mailbox and granted scopes. Use a dedicated business mailbox when appropriate.
- A sent email is an external side effect; Workflow Test should not be treated as permission to send live.
What Gmail connects
A Google account through OAuth for the Gmail mailbox that should send or store drafts.
Send an email or create a draft from workflow data.
Prerequisites and permissions
- Google account with Gmail access
- Valid recipient, subject, and body values
- Approval to send the intended business email
The connection can act only within the authorized mailbox and granted scopes. Use a dedicated business mailbox when appropriate.
Connect and configure
- Open the intended Agent Project → Integrations.
- Find Gmail and select Connect.
- Complete authorization with the correct external identity.
- Confirm the returned connection status is active.
- In the workflow builder, add App Action.
- Select Gmail, choose one supported action, select the connection, and complete the fields Yanola displays.
- Save and test with controlled data before activation.
Supported actions
| Action ID | What it does |
|---|---|
send_email | Send an email. |
create_draft | Create an email draft. |
Example workflow
Create a draft escalation email with extracted customer details for a human to review.
Workflow Trigger → Validate inputs → App Action (Gmail) → Condition → Notify or End FlowReconnection and token expiration
- Open Integrations when a workflow reports a missing, expired, revoked, or error connection.
- Select Reconnect for Gmail.
- Authorize the intended identity again.
- Validate access to the exact resource used by the workflow.
- Retest every dependent App Action.
Troubleshooting
| Symptom | What to check |
|---|---|
Connection is expired, revoked, or error | Reconnect from Integrations and complete provider consent. |
Action cannot find a resource | Grant the connected identity access and use the exact provider ID. |
Action input is rejected | Match the action-specific fields and data types shown in the node. |
Test and live behavior differ | Check provider environment, current permissions, external rate limits, and live data. |
Limitations and security
A sent email is an external side effect; Workflow Test should not be treated as permission to send live.
The catalog does not expose inbox search, reply, attachment management, or mailbox administration.
Never place provider access tokens or secrets in workflow text, logs, screenshots, or AI prompts. Remove unused connections and reconnect only through Yanola.