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 supportAIHandle WhatsApp support chats with OpenRouter and PineconeStarts on an incoming WhatsApp message · 44 stepsPineconeWhatsAppCustomer supportAIMulti-department support bot with Pinecone and TelegramStarts on an incoming Telegram message · 46 stepsGoogle DrivePineconePostgresTelegramCustomer supportAICreate a multi-modal Telegram support bot with OpenAIStarts on an incoming Telegram message · 48 stepsGoogle DriveSupabase vectorsTelegramCustomer supportAIRoute WhatsApp customer support with OpenAIStarts on another system calling it · 48 stepsGmailGoogle DriveGoogle SheetsCustomer 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 Customer Service Ticket Creation & NotificationsStarts on someone submitting a form · 3 stepsAsanaWhatsAppCustomer supportCreate Asana ticket from terminal bash-dashStarts on another system calling it · 3 stepsAsanaCustomer supportZendesk Support Ticket to Aqtos TaskStarts on another system calling it · 3 stepsZendeskCustomer supportAssign sequential ticket IDs by category in Google SheetsStarts on an event in a connected app · 4 stepsGoogle SheetsCustomer 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 supportAnswer Notion knowledge base questions with You.com ResearchStarts on an event in a connected app · 5 stepsNotionCustomer supportAnswer questions with Telegram and TavilyStarts on an incoming Telegram message · 5 stepsTelegramCustomer supportAuto bug report aggregator: Sync Zendesk bug tickets into GoogleStarts on an event in a connected app · 5 stepsGoogle SheetsZendeskCustomer supportCustomer support ticket system for SMEs with Google SheetsStarts on another system calling it · 5 stepsEmailGoogle SheetsCustomer supportGmail to Zendesk ticket automation with Google SheetsStarts on an arriving email · 5 stepsGmailGoogle SheetsZendeskCustomer supportJira ticket creation from Google Forms with GmailStarts on a change in a Google Sheet · 5 stepsGmailGoogle SheetsJiraCustomer 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 supportAutomate support escalations with OpenAI and SupabaseStarts on another system calling it · 6 stepsSupabaseCustomer supportCreate HubSpot support tickets from Tally form submissionsStarts on an event in a connected app · 6 stepsHubSpotCustomer supportCreate unique Jira tickets from Splunk alertsStarts on another system calling it · 6 stepsJiraCustomer supportFast-track VIP tickets with Google Sheets and ClickUpStarts on an event in a connected app · 6 stepsClickUpTelegramZendesk

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.