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

134 found

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

Lead generationAISocial inbox to Jira + Slack: lead capture & notificationStarts on another system calling it · 6 stepsJiraSlackAI assistantsAIThe AI QA Suite: Agentic Test Case Generation for JiraStarts on a clock · 7 stepsJiraAlerts and monitoringAIAI-powered bug triage system with OpenAI and JiraStarts on another system calling it · 8 stepsJiraSlackCustomer supportAIAuto-sort support emails with OpenAI and JiraStarts on an arriving email · 8 stepsEmailJiraCustomer supportAIClassify and convert GitHub issues to Jira tickets with OpenAIStarts on an event in a connected app · 8 stepsJiraCustomer supportAICreate Jira issues from Outlook email support requestsStarts on a clock · 8 stepsJiraOutlookCustomer supportAIReview Jira ticket quality with OpenRouter GPTStarts on an event in a connected app · 8 stepsJiraData collectionAIRoute Jira tasks to experts with Google Sheets and OpenAIStarts on a change in a Google Sheet · 8 stepsGoogle SheetsJiraAlerts and monitoringAITriage AML alerts with OpenSanctions and OpenAIStarts on another system calling it · 8 stepsJiraChat assistantsAIWebhook OpenAI Jira “Bug suspicion” Slack QA escalationStarts on another system calling it · 8 stepsJiraSlackResearch and reportingAIConvert Slack whiteboard images into Jira tasksStarts on an event in a connected app · 9 stepsJiraNotionCustomer supportAICreate knowledge base from Jira tickets with OpenAIStarts on a clock · 9 stepsJiraPineconeCustomer supportAIAI-powered email to Jira ticket creation with LlamaStarts on an arriving email · 10 stepsGmailJiraAlerts and monitoringAIAutomate ETL error monitoring with Sheets and JiraStarts on another system calling it · 10 stepsGmailGoogle SheetsJiraSlackAlerts and monitoringAIAutomate GitHub, Jira release notes with GeminiStarts on an event in a connected app · 10 stepsEmailJiraResearch and reportingAIAutomate feature request collection & analysisStarts on an event in a connected app · 10 stepsJiraSchedulingAICreate Jira tasks from Slack with OpenAI and GmailStarts on an event in a connected app · 10 stepsGmailGoogle CalendarJiraSlackResearch and reportingAICustomer feedback automation with OpenAI and JiraStarts on another system calling it · 10 stepsJiraSlackResearch and reportingAIGenerate lessons learned reports from Jira epicsStarts on an event in a connected app · 10 stepsGoogle DocsJiraAlerts and monitoringAIGitHub to Jira bug sync with OpenAIStarts on another system calling it · 10 stepsDiscordGitHubJiraSlackMoney adminAIHandle failed payment renewals with Jira and SlackStarts on another system calling it · 10 stepsJiraSlackResearch and reportingAIDependency update risk analysis with OpenAI and SlackStarts on an event in a connected app · 12 stepsGoogle SheetsJiraSlackAlerts and monitoringAINotify new Jira tasks with OpenAI and SlackStarts on an event in a connected app · 12 stepsGmailGoogle CalendarJiraSlackChat assistantsAIOrchestrate security vulnerability remediation with PortStarts on another system calling it · 12 stepsJiraSlack

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.