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 supportAITriage tenant complaints with Slack and Google SheetsStarts on another system calling it · 15 stepsEmailGoogle SheetsSlackCustomer supportAIAnswer infrastructure questions in Slack with OpenAIStarts on an event in a connected app · 16 stepsQdrantSlackCustomer supportAIAutomate IT support: Convert emails to Jira ticketsStarts on an arriving email · 16 stepsGmailJiraSendGridSlackCustomer supportAIRoute procurement helpdesk tickets from Gmail with GroqStarts on an arriving email · 16 stepsGmailGoogle SheetsSlackCustomer supportAITurn support tickets into developer insights with OpenAIStarts on a clock · 16 stepsEmailJiraPostgresSlackCustomer supportAIValidate concert ticket bookings and orchestrate fan experienceStarts on another system calling it · 16 stepsGmailGoogle SheetsSlackCustomer supportAIAnalyze pentest reports and create remediation ticketsStarts on another system calling it · 17 stepsSlackCustomer supportAIAnalyze support screenshots with UploadToURL and OpenAIStarts on another system calling it · 17 stepsJiraSlackZendeskCustomer supportAITriage and route support tickets with Gemini and JiraStarts on another system calling it · 17 stepsGmailJiraSlackCustomer supportAIAI sentiment-driven priority classificationStarts on another system calling it · 18 stepsGoogle SheetsSlackCustomer supportAIMine pharma complaint trends and trigger CAPA alertsStarts on a clock · 19 stepsSlackCustomer supportAIRun an AI student helpdesk with OpenAI and Google SheetsStarts on someone opening a chat with it · 20 stepsGmailGoogle SheetsSlackCustomer supportAIAutomated Slack IT helpdesk with OpenAI and SupabaseStarts on someone submitting a form · 21 stepsSlackSupabase vectorsCustomer supportAIGenerate GEO-optimized support replies from GmailStarts on an arriving email · 21 stepsGmailSlackCustomer supportAIAI-powered ticket triage with OpenAI and PostgresStarts on another system calling it · 22 stepsPostgresSlackCustomer supportAIAssess GitHub bus-factor risk in GitHub with Claude and SlackStarts on another system calling it · 22 stepsSlackCustomer supportAIAI email support system: Gmail, Gemini, GPT-4, Slack & GoogleStarts on an arriving email · 23 stepsGmailGoogle DriveGoogle SheetsPineconeCustomer supportAIRoute and triage multi-channel support tickets with OpenAIStarts on another system calling it · 23 stepsGmailGoogle SheetsSlackCustomer supportAIAnswer Slack knowledge questions with Notion and Google DriveStarts on a clock · 25 stepsGoogle DriveNotionPineconeSlackCustomer supportAIAutomate customer support with Slack and CRMStarts on another system calling it · 27 stepsGmailGoogle SheetsSlackCustomer supportAIAutomate customer support issue resolution with OpenAIStarts on a clock · 29 stepsJiraNotionSlackCustomer supportAITriage and resolve stale Jira tickets with OpenAI and NotionStarts on a clock · 29 stepsJiraNotionSlackCustomer supportAIAnswer internal policy questions from Google Drive with OpenAIStarts on someone opening a chat with it · 31 stepsGoogle DriveQdrantSlackCustomer supportAIAnswer onboarding questions in Slack with AnthropicStarts on an event in a connected app · 33 stepsGoogle SheetsPineconeSlack

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.