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 supportAIRoute WhatsApp support requests with Claude and SupabaseStarts on an incoming WhatsApp message · 37 stepsGmailGoogle CalendarGoogle DriveHubSpotCustomer supportAIRoute RAG customer support across WhatsApp and OutlookStarts on an incoming WhatsApp message · 41 stepsGoogle SheetsOutlookPineconeSlackCustomer supportAIRoute multichannel support tickets with OpenAI and HubSpotStarts on someone submitting a form · 59 stepsGmailSlackCustomer supportAIAnswer multi-channel support queries with OpenAI RAGStarts on an incoming WhatsApp message · 77 stepsDiscordEmailGoogle SheetsPostgresCustomer supportAutomated support ticket system with Gmail and TrelloStarts on an arriving email · 4 stepsGmailSlackTrelloCustomer supportSend Slack alert for high-priority Zendesk ticketsStarts on an event in a connected app · 4 stepsSlackCustomer supportPost unassigned Zendesk tickets to SlackStarts on a clock · 5 stepsSlackZendeskCustomer supportReal-time error detection with Slack and JiraStarts on another system calling it · 5 stepsJiraSlackCustomer supportEscalate negative Facebook Page reviewsStarts on another system calling it · 7 stepsSlackSupabaseCustomer 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 supportMonitor and report FAQ freshness from NotionStarts on a clock · 8 stepsGoogle SheetsNotionSlackCustomer supportSync Zendesk tickets to Slack threadStarts on another system calling it · 8 stepsSlackZendeskCustomer supportRoute and prioritize support emails to Slack channelsStarts on an arriving email · 9 stepsGmailSlackCustomer supportTriage support tickets and draft AI replies with CometAPIStarts on someone submitting a form · 9 stepsGmailSlackCustomer supportBuild a multi-agent support triage systemStarts on someone opening a chat with it · 10 stepsSlackCustomer supportCustomer Support AI Triage Agent with Gmail and Google SheetsStarts on another system calling it · 10 stepsGmailGoogle SheetsSlackCustomer supportError log monitor with SSH and SlackStarts on a clock · 10 stepsJiraSlackCustomer supportNotify user in Slack of quarantined emailStarts on another system calling it · 10 stepsJiraSlackCustomer supportQuick HubSpot contact lookup in Slack for sales & support teamsStarts on another system calling it · 10 stepsHubSpotSlackCustomer supportAutomated product price tracking with ScrapeGraphAI and SlackStarts on another system calling it · 11 stepsJiraSlackCustomer supportBuild a support ticket analytics dashboard with ScrapeGraphAIStarts on another system calling it · 11 stepsGoogle SheetsSlackCustomer supportCreate Zendesk tickets from Gmail and Slack with Google SheetsStarts on an arriving email · 11 stepsGmailGoogle SheetsSlackZendeskCustomer supportManage customer inquiries from email & web forms with SlackStarts on another system calling it · 11 stepsEmailGmailGoogle 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.