Triage Gmail support emails into Linear and Slack
When a support email arrives, this automation summarizes it, creates a prioritized Linear issue, and posts the issue link to Slack. The team can track the request from there.
Paste the prompt into your coding agent. It will set up the example and guide you through connecting your accounts.

Integrations used in this example
Put support requests where the team works
When support arrives in Gmail but the team tracks work in Linear, someone has to read the email, write an issue, judge its urgency, and share it with the team. That handoff can leave requests sitting in the inbox. This automation uses AI to summarize the email and choose a priority, creates a Linear issue, and posts its link in Slack. The team sees the request in its work queue and can decide what to do next.
Use a dedicated support Gmail account: the automation watches every new Inbox message, not a filtered subset. A teammate still needs to review the AI summary and priority and assign an owner. This example does not reply to the customer, process attachments, or close the email.
What you'll give the agent
- The dedicated Gmail support account to watch.
- The Linear team that should receive issues.
- The Slack channel where the team wants handoffs.
- Account authorization.
Start with the prompt; the agent will guide the account connections during setup. It gets the example code, creates your Automate.ax project, checks the code, and turns on the automation. If it needs a team or channel detail it cannot find, it will show you how to get it. You can change the team or channel later without editing the code.
Automate.ax's built-in AI reads the sender address, subject, and up to 6,000 characters of the email body to write the summary and choose the priority. Its use counts toward your organization's monthly AI allowance. You do not need a separate AI account.
The automation
The code requires the AI to return a title, summary, category, and priority. The Linear issue also records the sender, subject, and Gmail message ID. That ID lets the team find the original email without copying its full body into Linear or Slack.
import { automation, generate, t } from "automate.ax"
import { gmail } from "automate.ax/gmail"
import { linear } from "automate.ax/linear"
import { slack } from "automate.ax/slack"
import { z } from "zod"
export default automation(
"Triage support email into Linear and Slack",
{
parameters: [
{ label: "Linear team ID", name: "linearTeamId", type: "text" },
{
label: "Slack conversation ID",
name: "slackConversationId",
type: "text",
},
],
},
({ parameters }) => {
const email = gmail.onNewEmail()
const message = email.transform(
({ from, messageId, subject, text, snippet }) => ({
from: from?.address ?? "Unknown sender",
messageId,What one handoff looks like
Here is a possible handoff for a made-up support email. AI generates the title, summary, and priority, so your result may differ.
Gmail input
From customer@example.com: “Can I change the billing address on my next invoice?”
Possible Linear issue
“Support: Change billing address for next invoice” in the selected team, category billing, priority 3 (medium). The description includes the summary and a sample Gmail message ID.
Slack message
New support issue: https://linear.app/example/issue/EX-123
Customer asks how to change the billing address on the next invoice.
Set it up
- Copy the setup prompt above into your coding agent.
- Tell it which support account, Linear team, and Slack channel to use. The agent will create your Automate.ax project from the example.
- When Automate.ax asks you to connect accounts, authorize Gmail, Linear, and Slack. Check that the chosen team and channel are correct before the automation goes live.
The automation starts with new Inbox messages after setup. It does not go back through older mail.
Check it with a test email
Send a clearly labeled test email with made-up details to the connected support inbox. Each email starts a run, which records what the automation did. Open that run in Automate.ax, then check the new Linear issue and confirm that Slack contains the issue link and summary. Review the generated priority yourself; AI triage can be wrong.
If the handoff stops, check the failed step in that run and verify the account connections, selected Linear team, and Slack channel access. Automate.ax ignores repeat Gmail notifications for the same message. Later steps can still fail or retry, so check the run before assuming each email produced one handoff.
More automation examples
Source code
The GitHub repository contains the source code and steps for setting it up yourself.
View the GitHub example