Google Gmail
Askel connects to your customer's Gmail account, letting your product send transactional emails from their own address, read relevant threads, and react to incoming messages without building a custom email integration per customer.
What you can do
Send emails from the customer's address
Use the Gmail messages.send endpoint to deliver messages that appear to come from the connecting user's address, complete with HTML body, plain-text fallback, and attachments.
Read and search threads
Fetch threads and messages matching a Gmail search query, such as from:invoicing@vendor.com is:unread, to surface relevant emails without reading the entire inbox.
Create and send drafts
Create a draft message first, let your product or the customer review it, then call send to deliver it, useful for workflows that include a human approval step.
Add and remove labels
Apply or remove Gmail labels on specific messages to track processing state, for example marking a message as Processed after your workflow handles it.
Watch for new messages via push notifications
Register a Gmail push notification using the users.watch endpoint. Google notifies Askel when new messages arrive, triggering downstream workflow steps.
Read attachment content
Fetch message parts with MIME type application/pdf or text/csv and download the attachment bytes for your product to process.
Sending personalised onboarding emails from the customer's sales rep address
You sell a sales-enablement platform. Redpine Technologies wants onboarding emails to new users to come from their account executive's Gmail address, not a generic no-reply. Each email should include the new user's first name, a login link, and the AE's calendar link.
- 1
Connect once
Redpine's account executive clicks Connect Gmail in your product. Google's consent screen lists the gmail.send and gmail.compose scopes; the AE approves. Askel stores the refresh token.
- 2
Configure the template
Your CS team sets up an email template with merge fields for the new user's first name, login URL, and calendar link. The From address is populated from the connected Gmail account.
- 3
Trigger on user provisioning
When your product provisions a new Redpine user, it fires the Send Onboarding Email workflow. Askel substitutes the merge fields and prepares the message payload.
- 4
Send via Gmail API
Askel calls messages.send using the AE's OAuth token. The email lands in the recipient's inbox from the AE's real Gmail address, not a platform relay.
- 5
Log the send
Askel records the Gmail message ID and delivery timestamp on the user record in your product. Your team can look up the exact message ID if a recipient reports issues.
OAuth 2.0
The connecting user completes Google OAuth and approves the gmail.send scope, or the broader mail.google.com scope if your workflow also needs to read messages. Askel stores the refresh token and renews it silently. For read-only use cases like scanning incoming invoices, Askel can request gmail.readonly instead to limit the access footprint.
How Askel sits between your product and the customer's system
FAQ for Google Gmail
Will emails sent through this integration pass SPF and DKIM?+
What scopes does Askel request?+
Can we read all emails in the inbox, or only ones we sent?+
Does this work with Google Workspace accounts only, or also personal Gmail?+
catching drift before it breaks, and hitting go-live dates.
© 2025 Askel.ai. All rights reserved.