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 supportAIAutomated customer support system with GmailStarts on someone submitting a form · 31 stepsGmailGoogle SheetsQdrantTelegramCustomer supportAIAI-powered WhatsApp support bot with OpenAI and GmailStarts on an incoming WhatsApp message · 32 stepsGmailGoogle SheetsPineconeWhatsAppCustomer supportAIWhatsApp personal AI assistant with PDFStarts on an incoming WhatsApp message · 35 stepsAirtableGmailGoogle CalendarWhatsAppCustomer supportAIAI-powered WhatsApp customer service with OpenAI and GmailStarts on an incoming WhatsApp message · 37 stepsGmailGoogle SheetsSupabaseWhatsAppCustomer supportAIRoute WhatsApp support requests with Claude and SupabaseStarts on an incoming WhatsApp message · 37 stepsGmailGoogle CalendarGoogle DriveHubSpotCustomer supportAIBuild an AI-powered SMS support system with Twilio and OpenAIStarts on another system calling it · 40 stepsGmailPostgresS3Customer supportAIRoute WhatsApp customer support with OpenAIStarts on another system calling it · 48 stepsGmailGoogle DriveGoogle SheetsCustomer supportAIRoute multichannel support tickets with OpenAI and HubSpotStarts on someone submitting a form · 59 stepsGmailSlackCustomer supportAutomated support ticket system with Gmail and TrelloStarts on an arriving email · 4 stepsGmailSlackTrelloCustomer supportGmail to Zendesk ticket automation with Google SheetsStarts on an arriving email · 5 stepsGmailGoogle SheetsZendeskCustomer supportJira ticket creation from Google Forms with GmailStarts on a change in a Google Sheet · 5 stepsGmailGoogle SheetsJiraCustomer supportLabel and triage support emails in Gmail with DeepSeekStarts on an arriving email · 6 stepsGmailCustomer supportGenerate concert ticket PDFs with PDF Generator APIStarts on someone submitting a form · 7 stepsGmailGoogle SheetsSlackCustomer supportDraft cited support replies from public docs with You.comStarts on someone submitting a form · 8 stepsGmailSlackCustomer supportZendesk pending ticket follow-up system with GmailStarts on a clock · 8 stepsClickUpGmailGoogle SheetsZendeskCustomer supportDraft and triage support replies with Gmail and SlackStarts on someone submitting a form · 9 stepsGmailGoogle SheetsCustomer supportGenerate an FAQ MP3 library from form input with OpenAI TTSStarts on someone submitting a form · 9 stepsGmailGoogle DriveGoogle SheetsCustomer supportRoute Gmail support emails to ZendeskStarts on an arriving email · 9 stepsGmailZendeskCustomer supportRoute and prioritize support emails to Slack channelsStarts on an arriving email · 9 stepsGmailSlackCustomer supportTriage and redact support tickets with OpenAIStarts on another system calling it · 9 stepsGmailGoogle SheetsCustomer supportTriage support tickets and draft AI replies with CometAPIStarts on someone submitting a form · 9 stepsGmailSlackCustomer supportAI Customer Support Bot: Telegram + Groq + Google SheetsStarts on an incoming Telegram message · 10 stepsGmailGoogle SheetsTelegramCustomer supportCustomer Support AI Triage Agent with Gmail and Google SheetsStarts on another system calling it · 10 stepsGmailGoogle SheetsSlackCustomer supportCreate Zendesk tickets from Gmail and Slack with Google SheetsStarts on an arriving email · 11 stepsGmailGoogle SheetsSlackZendesk

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.