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 supportLabel and triage support emails in Gmail with DeepSeekStarts on an arriving email · 6 stepsGmailCustomer supportReal-time Vtiger support tickets to TelegramStarts on a clock · 6 stepsTelegramCustomer supportAnswer WhatsApp keyword FAQs with Twilio and Google SheetsStarts on an event in a connected app · 7 stepsGoogle SheetsTwilioCustomer supportAutomated e-Ticket PDF Generation with QR CodesStarts on a change in a Google Sheet · 7 stepsGoogle DocsGoogle DriveGoogle SheetsCustomer supportEscalate negative Facebook Page reviewsStarts on another system calling it · 7 stepsSlackSupabaseCustomer supportGenerate and email event e-tickets with Google WorkspaceStarts on a change in a Google Sheet · 7 stepsEmailGoogle DocsGoogle DriveGoogle SheetsCustomer supportGenerate concert ticket PDFs with PDF Generator APIStarts on someone submitting a form · 7 stepsGmailGoogle SheetsSlackCustomer supportRoute FAQ and catalog replies in WhatsApp BusinessStarts on an incoming WhatsApp message · 7 stepsWhatsAppCustomer supportStructure gym FAQ data for AI chatbot matchingStarts on an event in a connected app · 7 stepsGoogle SheetsCustomer supportSync Zendesk tickets with AsanaStarts on another system calling it · 7 stepsAsanaZendeskCustomer supportSync Zendesk tickets with GitHubStarts on another system calling it · 7 stepsGitHubZendeskCustomer supportSync Zendesk tickets with JiraStarts on another system calling it · 7 stepsJiraZendeskCustomer supportTurn new Jira tickets into CloudCLI AI coding sessionsStarts on an event in a connected app · 7 stepsJiraCustomer supportCreate Teams notifications for new tickets in ConnectWiseStarts on a clock · 8 stepsRedisCustomer supportCreate ticket on specific customer messages in TelegramStarts on an incoming Telegram message · 8 stepsTelegramCustomer 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 supportZendesk pending ticket follow-up system with GmailStarts on a clock · 8 stepsClickUpGmailGoogle SheetsZendeskCustomer supportAuto-resolve Jira tickets with GitHub Copilot and Port ContextStarts on an event in a connected app · 9 stepsGitHubJiraCustomer supportBuild a Telegram mental health support bot with OpenAIStarts on an incoming Telegram message · 9 stepsTelegramCustomer supportDraft and triage support replies with Gmail and SlackStarts on someone submitting a form · 9 stepsGmailGoogle SheetsCustomer supportGenerate an FAQ MP3 library from form input with OpenAI TTSStarts on someone submitting a form · 9 stepsGmailGoogle DriveGoogle SheetsCustomer supportPublish Telegram messages to LinkedIn postsStarts on an incoming Telegram message · 9 stepsLinkedInTelegram

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.