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 supportAITriage customer support emails with OpenAI and GmailStarts on another system calling it · 11 stepsGmailGoogle SheetsCustomer supportAITriage support emails and draft Gmail replies with OpenAIStarts on an arriving email · 11 stepsGmailGoogle SheetsCustomer supportAITriage support emails with Gmail and OpenAIStarts on an arriving email · 11 stepsGmailGoogle SheetsNotionSlackCustomer supportAITurn customer emails into FAQ drafts with Gmail and GeminiStarts on an arriving email · 11 stepsGmailGoogle DocsGoogle SheetsCustomer supportAIWhatsApp AI customer service bot with GmailStarts on an incoming WhatsApp message · 11 stepsGmailWhatsAppCustomer supportAIWhatsApp support agent with OpenAIStarts on an incoming WhatsApp message · 11 stepsWhatsAppCustomer supportAIZendesk ticket summarizer with Pinecone and OpenAIStarts on a clock · 11 stepsPineconeSlackZendeskCustomer supportAIAI WhatsApp Support Agent: GPT-4o + Persistent Memory (Supabase)Starts on another system calling it · 12 stepsSlackSupabaseCustomer supportAIAI-Powered LINE Bot: Automate Customer Support & Task AutomationStarts on another system calling it · 12 stepsAirtableGmailGoogle CalendarCustomer supportAIAI-powered WhatsApp support automation system with OpenAIStarts on another system calling it · 12 stepsGoogle SheetsHubSpotSlackCustomer supportAIAnswer backlog questions from Slack with Supabase and GeminiStarts on someone submitting a form · 12 stepsSupabase vectorsCustomer supportAIAnswer support questions from a knowledge base with OpenAIStarts on someone opening a chat with it · 12 stepsin-memory vectorsCustomer supportAIAutomate Zendesk Support replies with Google Sheets and GmailStarts on an event in a connected app · 12 stepsGmailGoogle SheetsZendeskCustomer supportAIAutomate internal complaint resolution with Jotform and GeminiStarts on a clock · 12 stepsGmailGoogle SheetsCustomer supportAIAutomated product email support with OpenAI and Pinecone RAGStarts on an arriving email · 12 stepsGmailPineconeCustomer supportAICustomer Support Channel and Ticketing System with SlackStarts on a clock · 12 stepsLinearSlackCustomer supportAIDetect and score refund risk with Webhook and OpenAIStarts on another system calling it · 12 stepsDiscordGmailGoogle SheetsCustomer supportAIGenerate weekly client FAQ updates with NewsAPI and OpenAIStarts on a clock · 12 stepsGoogle SheetsCustomer supportAIRAG-powered AI voice customer support agent with SupabaseStarts on another system calling it · 12 stepsGoogle DocsSupabaseCustomer supportAIRAG: Support Claim Playbook Assistant with SlackStarts on an event in a connected app · 12 stepsGoogle DriveSlackSupabase vectorsCustomer supportAIScore Zoho support tickets with OpenAIStarts on another system calling it · 12 stepsGmailCustomer supportAITriage and draft support email replies with Gmail and OpenAIStarts on an arriving email · 12 stepsGmailCustomer supportAITriage and log customer inquiries from Gmail and web formsStarts on another system calling it · 12 stepsAirtableGmailSlackCustomer supportAITriage support emails and draft AI replies with GmailStarts on an arriving email · 12 stepsGmailGoogle Sheets

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.