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 supportAISummarize Gmail support emails with GeminiStarts on an arriving email · 4 stepsGmailSlackCustomer supportAIAI support ticket categorizer with Gmail and OpenAIStarts on an arriving email · 5 stepsGmailNotionSlackCustomer supportAIAnalyze Customer Feedback Sentiment & Alert Support TeamStarts on another system calling it · 5 stepsGoogle SheetsSlackCustomer supportAIAuto-ticket maker: Convert Slack conversations into structuredStarts on another system calling it · 6 stepsSlackCustomer supportAITriage support tickets and send AI replies with OpenAIStarts on another system calling it · 7 stepsEmailGoogle SheetsSlackCustomer supportAIAnalyze customer feedback sentiment and alert support teamStarts on someone submitting a form · 8 stepsGoogle SheetsSlackCustomer supportAIAnalyze workflow errors with OpenAI and FreshDeskStarts on an event in a connected app · 8 stepsSlackCustomer supportAIAutomate support ticket prioritization with Jotform and GeminiStarts on an event in a connected app · 8 stepsClickUpGmailGoogle SheetsSlackCustomer supportAIAI-powered email support router with Gmail and OpenAIStarts on an arriving email · 9 stepsGmailSlackSupabaseCustomer supportAIAuto-answer GitHub PR questions with OpenAI and NotionStarts on an event in a connected app · 9 stepsGoogle SheetsNotionSlackCustomer supportAIAutomated email support triage with Gmail and TrelloStarts on an arriving email · 9 stepsGmailGoogle SheetsSlackTrelloCustomer supportAIRoute and prioritize Gmail support tickets to NotionStarts on an arriving email · 9 stepsGmailNotionSlackCustomer supportAITriage customer support tickets from Gmail and formsStarts on someone submitting a form · 9 stepsGmailGoogle SheetsSlackCustomer supportAITriage support tickets by GPT-4o sentimentStarts on another system calling it · 9 stepsSlackCustomer supportAIAI Gmail support automation with Gemini and OpenAIStarts on an arriving email · 10 stepsGmailPineconeSlackCustomer supportAIAI customer support chatbot with OpenAI and Google SheetsStarts on another system calling it · 10 stepsGoogle SheetsSlackCustomer supportAIAutomate customer support triage with Gmail and SlackStarts on an arriving email · 10 stepsAirtableGmailGoogle SheetsSlackCustomer supportAIDraft and approve Gmail support replies with Gemini and SlackStarts on an arriving email · 10 stepsGmailGoogle SheetsSlackCustomer supportAIPrioritize Zendesk tickets with OpenAI and SlackStarts on another system calling it · 10 stepsSlackZendeskCustomer supportAIAutomate FAQ generation from Stack Overflow to NotionStarts on an event in a connected app · 11 stepsGoogle SheetsNotionRSSSlackCustomer supportAICreate AI FAQ articles from Slack threads into Notion and ZendeskStarts on an event in a connected app · 11 stepsNotionSlackZendeskCustomer supportAIQuery support docs with Dropbox and SlackStarts on an event in a connected app · 11 stepsDropboxSlackCustomer supportAITriage customer complaint emails from Gmail with OpenAIStarts on an arriving email · 11 stepsGmailGoogle SheetsSlackCustomer supportAITriage support emails with Gmail and OpenAIStarts on an arriving email · 11 stepsGmailGoogle SheetsNotionSlack

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.