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

110 found

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

Customer 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 WhatsApp support automation system with OpenAIStarts on another system calling it · 12 stepsGoogle SheetsHubSpotSlackCustomer supportAICustomer Support Channel and Ticketing System with SlackStarts on a clock · 12 stepsLinearSlackCustomer supportAIRAG: Support Claim Playbook Assistant with SlackStarts on an event in a connected app · 12 stepsGoogle DriveSlackSupabase vectorsCustomer supportAITriage and log customer inquiries from Gmail and web formsStarts on another system calling it · 12 stepsAirtableGmailSlackCustomer supportAIAI Customer Support Bot: Auto-Classify, RouteStarts on another system calling it · 13 stepsSlackCustomer supportAIAssess churn risk from HubSpot tickets with DeepSeek and SlackStarts on a clock · 13 stepsHubSpotSlackCustomer supportAICollect and theme customer complaints with Apify and OpenAIStarts on a clock · 13 stepsApifyGoogle SheetsNotionSlackCustomer supportAIEscalate VIP Zendesk tickets with OpenAI and SlackStarts on an event in a connected app · 13 stepsAirtableGmailSlackCustomer supportAIRoute customer support chats with OpenAI and SlackStarts on another system calling it · 13 stepsGoogle SheetsSlackCustomer supportAIAnswer code of conduct questions in Slack with OpenAI and RAGStarts on someone submitting a form · 14 stepsGoogle DriveSlackin-memory vectorsCustomer supportAIAutomate API FAQ quality testing with OpenAI and Google SheetsStarts on an event in a connected app · 14 stepsGmailGoogle SheetsSlackCustomer supportAIAutomated customer support with OpenAI and GmailStarts on a change in a Google Sheet · 14 stepsGmailGoogle SheetsSlackCustomer supportAIClassify support emails and send replies with Claude and GmailStarts on an arriving email · 14 stepsGmailGoogle SheetsSlackCustomer supportAICompare iOS and Android review complaints with ApifyStarts on a clock · 14 stepsApifyGoogle SheetsNotionSlackCustomer supportAIConvert support emails to FAQs and triage issues with GmailStarts on an arriving email · 14 stepsGmailGoogle SheetsNotionSlackCustomer supportAISentiment analysis tracking on support issues with LinearStarts on a clock · 14 stepsAirtableSlackCustomer supportAISupport emails into FAQs with OpenAI and GmailStarts on an arriving email · 14 stepsGmailGoogle SheetsNotionSlackCustomer supportAITriage customer inquiries from Gmail and web formsStarts on another system calling it · 14 stepsAirtableGmailSlackCustomer supportAIAnswer Slack knowledge base questions with Notion and PineconeStarts on a clock · 15 stepsNotionPineconeSlackCustomer supportAIAutomate IT support with Telegram and WhisperStarts on an incoming Telegram message · 15 stepsGoogle DriveJiraSlackTelegramCustomer supportAIClassify and route DevOps support messages with SlackStarts on another system calling it · 15 stepsQdrantSlackCustomer supportAITriage support tickets with Claude and Infini AnalyticsStarts on another system calling it · 15 stepsSlack

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.