- Documentation
Gmail integration
Send, read, and manage Gmail messages on behalf of your clients.
What it does
The Gmail integration lets your agency move email work into TaskJuice without juggling a client's inbox by hand. Connect a client's Google account once and you can list and read messages with a Gmail search query, send brand-new emails, reply inside an existing thread, create drafts for review, send approved drafts, delete a message, and start a workflow whenever a new message lands in a watched mailbox.
Connect a Gmail account
- Open your workspace in TaskJuice and navigate to Connections.
- Choose Gmail and click Connect.
- Sign in with the Google account whose mailbox you want to manage on behalf of your client.
- Grant the requested scopes (read and modify access to Gmail, plus the send scope for outgoing messages).
- TaskJuice returns you to the workspace with the connection ready to use in any workflow.
To revoke access at any time, visit Google Account permissions and remove the TaskJuice entry.
Triggers
gmail/new-messagepolls the connected mailbox on a configurable interval and emits one activation per cycle containing every message that matches the configured Gmail search query and label filters. Drop a Loop node downstream to process each message individually, or feed the array straight into a digest.
Actions
gmail/list-messagesreturns the message IDs in the mailbox that match an optional Gmail search query, label filter, and spam or trash inclusion flag, with cursor pagination.gmail/get-messagereturns a single message by ID in the chosen format (minimal, full, raw, or metadata).gmail/send-emailsends a new email message with To, CC, BCC, subject, and HTML body fields.gmail/reply-to-messagesends a reply that keeps the response inside the original conversation thread.gmail/create-draftcreates a draft email under the connected account for later review or sending.gmail/send-draftsends an existing draft by its draft ID.gmail/delete-messagepermanently removes a message from the mailbox.
Known limitations
- Gmail does not publish a webhook that fires on every incoming message in the declarative envelope. The
new-messagetrigger polls on a configurable interval (60 seconds minimum, five minutes by default), so latency is bounded by the chosen interval rather than instant. - The Gmail API enforces per-user and per-project quotas measured in quota units. When a 429 is returned, TaskJuice surfaces it as a retryable rate-limit error and respects the recommended backoff.
- Sending a message requires the
gmail.sendscope and is subject to Google's daily sending limits for the connected account type.
Was this helpful?