Connecting Gmail to action builder
Before you can include external actions in your action flows, you must connect the action builder to the external system.
- All external actions performed by an action flow are attributed to the user who connected the external system. Therefore, it's a best practice to use a dedicated service account rather than personal credentials when connecting to each external system.
- All integrations request access to necessary scopes. However, it's important that you review and validate the scopes before authorizing the connection to the external system.
- When managing credentials for API key-based tools, such as OpenAI, it's best to store keys in a secure vault or credential manager.
- In Admin Center, click
Apps and integrations in the sidebar, then select Actions > Action
flows. - Create or edit an action flow.
- Open the step sidebar.
- Under External actions, click Gmail.
- Click Connect.
- Follow Gmail's prompts to authenticate and complete the connection.
You'll log into a Google Workspace or Gmail account, and admin approval might be required in managed environments.
The following scope is required for the account you authenticate with:
https://www.googleapis.com/auth/gmail.send.Note: All external actions performed by an action flow are attributed to the user who connected the external system. Therefore, it is a best practice to use a dedicated service account rather than personal credentials when connecting to each external system.
After you've connected to the system, you'll see an indicator that it's connected and details about the instance you're connected to, as well as the actions available for Gmail.
Using Gmail actions in action flows
Gmail action steps can be used to send new emails.
Sending emails in Gmail
Use the Send email action to send a new email.
This action has the following inputs and outputs:
| Variables | |
|---|---|
| Inputs | Required: Recipient's email,
Subject,
BodyOptional: |
| Output |
threadID, ID,
labelIds
|
Recipe: Sending emails to your Inside Sales team when a Zendesk ticket is identified as a lead
The following example action flow uses ticket tags added by agents to automatically send notification emails to the Inside Sales team when a ticket is identified as a lead.
- Add an action flow trigger with the following details:
- Click Add trigger.
- In the step sidebar, under Zendesk, click Tickets.
- Click Lifecycle and select Ticket is tagged.
- Click Add condition.
- Under Variable, click Ticket tags changed and select Tags (added).
- Set the Operator to Contains at least 1 of.
- Under Value, enter sales_lead.
- Add a step to look up ticket details:
- In the action builder, beneath the action flow trigger, click the
Add step icon (
). - In the step sidebar, under Zendesk actions, click Look up ticket.
- Under Ticket ID, click into the field and then click Select a variable instead.
- Within the variable menu, select Ticket is tagged as the step that outputs the variable you want to use, and then select Ticket ID.
- In the action builder, beneath the action flow trigger, click the
Add step icon (
- Add a step to look up user details about the ticket requester:
- In the action builder, click the Add step icon (
). - In the step sidebar, under Zendesk actions, click Look up user.
- Under User ID type, select Zendesk user ID.
- For User ID, click Add variable.
- Within the variable menu, select Look up ticket as the step that outputs the variable you want to use, and then select Requester ID.
- In the action builder, click the Add step icon (
- Add a step to lookup details about the ticket requester's organization:
- In the action builder, click the Add step icon (
). - In the step sidebar, under Zendesk actions, click Look up organization.
- Under Organization ID type, select Zendesk organization ID.
- For Organization ID, click Add variable.
- Within the variable menu, select Look up user as the step that outputs the variable you want to use, and then select Organization ID.
- In the action builder, click the Add step icon (
- Add a step that sends an email based on the information you collected for
the ticket, user, and organization:
- In the action builder, click the Add step icon (
). - In the step sidebar, under External actions, click Gmail and then select Send email.
- Under Recipient's email, enter the Inside sales team distribution list. For example, sales@yourcompany.com.
- Under Subject, enter Ticket Ticket ID Identified as
Lead, where Ticket ID is a variable.
Click Add variable, select Look up ticket, and select Ticket ID, to insert the Ticket ID variable into the subject.
- Under Body, enter the message you want to send to the Inside
sales team for new prospects. Include relevant ticket and user
information as variables from the Look up ticket and Look up user
steps, respectively, to streamline their ability to follow up. In
the following example, all variables are
italicized:
Hi Sales Team, Ticket Ticket ID has been identified as a lead. Can you please follow up with User Name as soon as possible? User contact information: - Email: User Email - Phone: User Phone - Locale and timezone: User Locale - User IANA timezone - Notes: User Notes Here's more context on the ticket: - Ticket subject: Ticket Subject - Ticket description: Ticket Description - Last ticket update: Ticket's Latest agent update
- In the action builder, click the Add step icon (
- Click Save.
- Click Test to test the action flow.
- Click the options menu (
) and select Activate to begin sending
emails to the sales team when Zendesk tickets are identified as sales
leads.