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

46 found

AllContentAlerts and monitoringData collectionIntegrationsLead generationResearch and reportingAI assistantsSchedulingMoney adminDocuments and filesChat assistantsCustomer supportE-commerceCRMHiringSetup and learningStrategy and planningZendesk ✕

Customer supportAIAI-powered auto-tagging for Zendesk tickets with OpenAIStarts on a clock · 7 stepsZendeskLead generationAIGmail to Zendesk: AI-enriched ticket creation with OpenAIStarts on an arriving email · 8 stepsGmailGoogle SheetsZendeskCustomer supportAIPrioritize Zendesk tickets with OpenAI and SlackStarts on another system calling it · 10 stepsSlackZendeskCustomer supportAICreate AI FAQ articles from Slack threads into Notion and ZendeskStarts on an event in a connected app · 11 stepsNotionSlackZendeskCustomer supportAIZendesk ticket summarizer with Pinecone and OpenAIStarts on a clock · 11 stepsPineconeSlackZendeskCustomer supportAIAutomate Zendesk Support replies with Google Sheets and GmailStarts on an event in a connected app · 12 stepsGmailGoogle SheetsZendeskCustomer supportAIIntelligent WhatsApp Support Auto-RouterStarts on an event in a connected app · 13 stepsTwilioZendeskCustomer supportAIAnalyze support screenshots with UploadToURL and OpenAIStarts on another system calling it · 17 stepsJiraSlackZendeskMoney adminAIEscalate payment issues with Azure OpenAI and Google SheetsStarts on another system calling it · 17 stepsGmailGoogle SheetsSlackZendeskLead generationAIAutomate SIEM alert enrichment with MITRE ATT and QdrantStarts on someone opening a chat with it · 23 stepsGoogle DriveQdrantZendeskResearch and reportingAIGenerate continuous PRD updates in Google DocsStarts on someone submitting a form · 23 stepsGoogle DocsJiraZendeskCustomer supportAIAnswer multi-channel support queries with OpenAI RAGStarts on an incoming WhatsApp message · 77 stepsDiscordEmailGoogle SheetsPostgresCustomer supportZendesk Support Ticket to Aqtos TaskStarts on another system calling it · 3 stepsZendeskCustomer supportAuto bug report aggregator: Sync Zendesk bug tickets into GoogleStarts on an event in a connected app · 5 stepsGoogle SheetsZendeskCustomer supportGmail to Zendesk ticket automation with Google SheetsStarts on an arriving email · 5 stepsGmailGoogle SheetsZendeskCustomer supportPost unassigned Zendesk tickets to SlackStarts on a clock · 5 stepsSlackZendeskCustomer supportFast-track VIP tickets with Google Sheets and ClickUpStarts on an event in a connected app · 6 stepsClickUpTelegramZendeskAlerts and monitoringMonitor Zendesk churn risk signals, logStarts on a clock · 6 stepsGoogle SheetsSlackZendeskE-commerceSync Shopify orders with ZendeskStarts on an event in a connected app · 7 stepsZendeskCustomer 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 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 SheetsZendesk

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.