Gmail¶
Configures a Carbon data connector for Gmail. This node identifies the Gmail integration and delegates all processing to the shared Carbon data node base, which handles authentication, configuration, and data retrieval/sync behavior.
Usage¶
Use this node when you want to ingest or synchronize Gmail content as a data source in your Salt AI workflows. Place it where a Gmail data connection is required for downstream search, retrieval, or enrichment steps. You typically pair it with nodes that manage Carbon service access tokens and with downstream nodes that consume the resulting data handle.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| configuration | False | Not specified | Optional parameters for how the Gmail connector should operate (e.g., filters, scopes, or sync options). Exact fields depend on the shared Carbon base implementation. | {"labels": ["INBOX"], "max_emails": 500} |
| authorization | False | Not specified | Authentication or token details used by the Carbon service to access Gmail. The base Carbon node typically manages token retrieval and validation. | {"access_token": " |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| data | Not specified | A reference or handle to the Gmail-connected data set prepared by the Carbon service, suitable for downstream retrieval or indexing steps. | {"data_source_id": "gmail-connection-123", "status": "ready"} |
Important Notes¶
- This node strictly targets the Gmail integration; all core behavior (inputs, outputs, and processing) is inherited from the base Carbon data node.
- You must have the Carbon service configured and accessible, and the user/account must have granted Gmail permissions to allow data access.
- Large Gmail mailboxes can take time to index or sync; plan for asynchronous availability and check status before downstream usage.
- Exact input/output schemas are defined by the base Carbon implementation and may vary across versions.
Troubleshooting¶
- Authentication errors: Ensure a valid Carbon access token is provided and that the Gmail account is properly authorized.
- Insufficient permissions: Verify that Gmail scopes and account permissions allow reading the necessary labels/folders.
- No data returned: Confirm filters or configuration settings are correct (e.g., labels, date ranges) and that the mailbox contains matching messages.
- Sync delays: For large mailboxes, allow additional time for ingestion. Check job or sync status in the Carbon service logs or monitoring.