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

485 found

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

Customer supportAIAnswer FAQ questions from Google Sheets with GeminiStarts on someone opening a chat with it · 10 stepsGoogle SheetsCustomer supportAIAnswer WhatsApp support chats with OpenRouter and PineconeStarts on an incoming WhatsApp message · 10 stepsGmailPineconeWhatsAppCustomer supportAIAutomate FAQ replies and follow-ups in n8n with OpenAIStarts on someone opening a chat with it · 10 stepsAirtablePineconeCustomer supportAIAutomate customer support triage with Gmail and SlackStarts on an arriving email · 10 stepsAirtableGmailGoogle SheetsSlackCustomer supportAIClient FAQ bot with Google Drive PDFs and Azure GPT-4o-miniStarts on another system calling it · 10 stepsGoogle DriveCustomer supportAIDraft and approve Gmail support replies with Gemini and SlackStarts on an arriving email · 10 stepsGmailGoogle SheetsSlackCustomer supportAIDraft personalized Outlook support email repliesStarts on an event in a connected app · 10 stepsGoogle SheetsOutlookSupabaseSupabase vectorsCustomer supportAIGmail customer support auto-responder with Ollama LLMStarts on an arriving email · 10 stepsGmailPineconeCustomer supportAIPrioritize Zendesk tickets with OpenAI and SlackStarts on another system calling it · 10 stepsSlackZendeskCustomer supportAITranslate Telegram audio messages with OpenAIStarts on an incoming Telegram message · 10 stepsTelegramCustomer supportAITriage Gmail support inquiries with Gemini and CalendarStarts on an arriving email · 10 stepsDiscordGmailGoogle CalendarGoogle SheetsCustomer supportAIWhatsApp support assistant with Google SheetsStarts on another system calling it · 10 stepsGoogle SheetsCustomer supportAIWhatsApp support bot with OpenAIStarts on an incoming WhatsApp message · 10 stepsWhatsAppCustomer supportAIAI chatbot call center: Taxi booking support with GrokStarts on a clock · 11 stepsGoogle CalendarPostgresCustomer supportAIAI customer support assistant with WhatsAppStarts on an incoming WhatsApp message · 11 stepsWhatsAppCustomer supportAIAnswer Telegram support questions with Google Docs and ClaudeStarts on an incoming Telegram message · 11 stepsGoogle DocsGoogle SheetsTelegramCustomer supportAIAnswer employee HR questions on Telegram with OpenAIStarts on an incoming Telegram message · 11 stepsPineconeTelegramCustomer supportAIAutomate FAQ generation from Stack Overflow to NotionStarts on an event in a connected app · 11 stepsGoogle SheetsNotionRSSSlackCustomer supportAIAutomated customer support & feedback triage with GeminiStarts on an arriving email · 11 stepsGmailCustomer supportAICreate AI FAQ articles from Slack threads into Notion and ZendeskStarts on an event in a connected app · 11 stepsNotionSlackZendeskCustomer supportAICustomer Support Chat Agent with OpenAI and Google DriveStarts on an event in a connected app · 11 stepsGoogle DrivePineconeCustomer supportAIDraft and send AI customer support email replies with GmailStarts on a clock · 11 stepsGmailGoogle SheetsCustomer supportAIQuery support docs with Dropbox and SlackStarts on an event in a connected app · 11 stepsDropboxSlackCustomer supportAITriage customer complaint emails from Gmail with OpenAIStarts on an arriving email · 11 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.