Automations, described by what they do

15,351 working automation workflows. Every description is composed from the workflow's own steps: what starts it, which services it touches, whether it hands judgement to a model, and how much there is to read.

Browse the libraryBrowse by job

Cleaned of credentials and personal data. Ready to import.

Running now3 steps

Send daily Mailchimp subscriber reports to Slack

Waiting for a trigger
Workflows15,351working automations
Call a model7,615hand a step to AI
Services60apps they connect
Small5,286readable in one sitting

What they're for

17 kinds of job

The library

131 found

AllContentAlerts and monitoringData collectionIntegrationsLead generationResearch and reportingAI assistantsSchedulingMoney adminDocuments and filesChat assistantsCustomer supportE-commerceCRMHiringSetup and learningStrategy and planningGmail ✕

Customer supportAISummarize Gmail support emails with GeminiStarts on an arriving email · 4 stepsGmailSlackCustomer supportAIAI support ticket categorizer with Gmail and OpenAIStarts on an arriving email · 5 stepsGmailNotionSlackCustomer supportAITriage support emails and draft replies with Gmail and OpenAIStarts on an arriving email · 6 stepsGmailn8n data tableCustomer supportAICustomer support appointment sechduler FAQ bot with OpenAIStarts on an event in a connected app · 7 stepsAirtableGmailGoogle CalendarCustomer supportAIEmail support agent w/ Gemini & GPT fallback with GmailStarts on an arriving email · 7 stepsGmailGoogle SheetsCustomer supportAIAnswer PDF questions with Gemini and GmailStarts on someone submitting a form · 8 stepsGmailGoogle SheetsCustomer supportAIAutomate support ticket prioritization with Jotform and GeminiStarts on an event in a connected app · 8 stepsClickUpGmailGoogle SheetsSlackCustomer supportAIAutomated Gmail support agent with Gemini and RAGStarts on an arriving email · 8 stepsGmailPineconeCustomer supportAICategorize support emails with OpenAI and GmailStarts on an arriving email · 8 stepsGmailCustomer supportAICreate Linear issues from Gmail support request messagesStarts on a clock · 8 stepsGmailLinearCustomer supportAICreate SAV support tickets and Gmail drafts with OpenAIStarts on an arriving email · 8 stepsAirtableGmailCustomer supportAITriage Gmail support emails with OpenAIStarts on an arriving email · 8 stepsGmailGoogle SheetsCustomer supportAIAI-powered Gmail customer support with OpenRouter and PineconeStarts on an arriving email · 9 stepsGmailPineconeCustomer supportAIAI-powered email support router with Gmail and OpenAIStarts on an arriving email · 9 stepsGmailSlackSupabaseCustomer supportAIAutomated customer support agent - Gmail + OpenAI + RAGStarts on an arriving email · 9 stepsGmailPineconeCustomer supportAIAutomated email support triage with Gmail and TrelloStarts on an arriving email · 9 stepsGmailGoogle SheetsSlackTrelloCustomer supportAICreate a customer support voice agent with OpenAIStarts on another system calling it · 9 stepsGmailGoogle CalendarGoogle SheetsCustomer supportAIExtract customer pain points from support forumsStarts on an event in a connected app · 9 stepsGmailCustomer supportAIRoute and prioritize Gmail support tickets to NotionStarts on an arriving email · 9 stepsGmailNotionSlackCustomer supportAIThis AI voice agent books calls & replaces support with GeminiStarts on another system calling it · 9 stepsGmailGoogle CalendarGoogle SheetsCustomer supportAITriage customer support emails and draft Gmail repliesStarts on an arriving email · 9 stepsGmailCustomer supportAITriage customer support tickets from Gmail and formsStarts on someone submitting a form · 9 stepsGmailGoogle SheetsSlackCustomer supportAIAI Gmail support automation with Gemini and OpenAIStarts on an arriving email · 10 stepsGmailPineconeSlackCustomer supportAIAI-powered email replies with FAQ and OpenAIStarts on an arriving email · 10 stepsGmailPinecone

Start small

A few you can read in one sitting

What we took out

Cleaned before anything was stored

These files carry more of whoever built them than is obvious. All of it is stripped, and every file was checked, not sampled. Where an author left a live document behind, it is replaced with the placeholder the careful ones used, so you can still see what belongs there.

Triggers

What starts them

  1. A clock4,166
  2. An event in a connected app3,946
  3. Another system calling it2,801
  4. An arriving email1,591
  5. Someone submitting a form1,545
  6. Someone opening a chat with it895
  7. A change in a Google Sheet216

Services

What they touch

Google Sheets5,229Gmail3,419Slack2,307Telegram1,809Google Drive1,540Email863Airtable554Google Calendar480Notion471RSS404Postgres306WhatsApp285

Read the workflows

Filter 15,351 automations by what they do, what they connect to and how big they are, and open the definition itself, ready to import.

Q&A

What are these?

Working automations: the definition of each, ready to import, with a description composed from its own steps.

Why are some descriptions unflattering?

Because they say what the workflow does. One that is four steps and a webhook is described as four steps and a webhook, so you can decide from the page whether it is worth your afternoon.

What was removed from the files?

Instance identifiers, canvas notes with personal links and email addresses, saved credential names, and live documents left in by their authors. Every file was checked, not sampled.

What do I need to run them?

A workflow automation tool that imports these definitions. Each imports as it is; you add your own credentials.