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 supportAIDraft customer support email replies with GmailStarts on a clock · 17 stepsGmailGoogle DriveGoogle SheetsTelegramCustomer supportAIHandle chat support and escalate unresolved ticketsStarts on another system calling it · 17 stepsGmailCustomer supportAIRoute urgent Gmail support emails and WhatsApp digestsStarts on a clock · 17 stepsGmailSupabaseWhatsAppCustomer supportAITriage and route support tickets with Gemini and JiraStarts on another system calling it · 17 stepsGmailJiraSlackCustomer supportAIDaily Jira ticket summarizer with OpenAI and Jira APIStarts on a clock · 18 stepsGmailJiraCustomer supportAIPersonalized AI assistant with Claude and OpenAIStarts on someone opening a chat with it · 18 stepsAirtableGmailGoogle CalendarTelegramCustomer supportAIRun a multilingual WhatsApp support assistant with OpenAIStarts on an incoming WhatsApp message · 18 stepsGmailGoogle SheetsWhatsAppCustomer supportAISelf improving email receptionist (FAQ based) with OpenAIStarts on a clock · 18 stepsAirtableGmailCustomer supportAISmart Customer Support System with OpenAI and GmailStarts on an arriving email · 18 stepsGmailGoogle DriveGoogle SheetsPineconeCustomer supportAIRoute multilingual support requests with DeepL and OpenAIStarts on someone submitting a form · 20 stepsGmailCustomer supportAIRun an AI student helpdesk with OpenAI and Google SheetsStarts on someone opening a chat with it · 20 stepsGmailGoogle SheetsSlackCustomer supportAISmart email assistant: automate customer support with SupabaseStarts on an arriving email · 20 stepsGmailGoogle DriveSupabaseSupabase vectorsCustomer supportAIAutomate multi-channel customer support with GmailStarts on an incoming Telegram message · 21 stepsGmailGoogle SheetsTelegramCustomer supportAIBuild a Telegram AI assistant with MemMachine and OpenAIStarts on an incoming Telegram message · 21 stepsGmailGoogle CalendarGoogle SheetsTelegramCustomer supportAIGenerate GEO-optimized support replies from GmailStarts on an arriving email · 21 stepsGmailSlackCustomer supportAIAI email support system: Gmail, Gemini, GPT-4, Slack & GoogleStarts on an arriving email · 23 stepsGmailGoogle DriveGoogle SheetsPineconeCustomer supportAICreate a WhatsApp customer support bot with OpenAIStarts on an event in a connected app · 23 stepsGmailGoogle CalendarSupabase vectorsTwilioCustomer supportAIDraft grounded Gmail support replies from a Notion KBStarts on an arriving email · 23 stepsGmailNotionin-memory vectorsCustomer supportAIRoute and triage multi-channel support tickets with OpenAIStarts on another system calling it · 23 stepsGmailGoogle SheetsSlackCustomer supportAISEO FAQ generator for websites with Google SheetsStarts on a clock · 24 stepsGmailGoogle SheetsCustomer supportAITurn emails into AI-enhanced tasks in Notion (multi-user support)Starts on an arriving email · 25 stepsAirtableGmailCustomer supportAIEmail sorting & drafting for customer support with GeminiStarts on a clock · 26 stepsGmailGoogle SheetsCustomer supportAIRun a WhatsApp customer support chatbot with OpenWA and OpenAIStarts on an event in a connected app · 26 stepsGmailGoogle DriveQdrantCustomer supportAIAutomate customer support with Slack and CRMStarts on another system calling it · 27 stepsGmailGoogle SheetsSlack

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.