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

39 found

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

Alerts and monitoringAutomate change request approvals with Monday.com and JiraStarts on a clock · 12 stepsGmailGoogle SheetsJiraSlackAlerts and monitoringAutomate change request workflow: Monday.com to JiraStarts on a clock · 12 stepsGmailGoogle SheetsJiraSlackAlerts and monitoringAutomate incident response with Jira and SlackStarts on an event in a connected app · 12 stepsGoogle DriveGoogle SheetsJiraSlackAlerts and monitoringMonitor and report OKR variance from Monday.com and JiraStarts on a clock · 12 stepsJiraOutlookSlackAlerts and monitoringMonitor SSL certificate expiry with Google Sheets and SlackStarts on a clock · 13 stepsGmailGoogle SheetsJiraSlackAlerts and monitoringReal-time IoT incident management with Jira and SlackStarts on another system calling it · 13 stepsJiraSlackAlerts and monitoringAutomate vulnerability triage from Snyk with Jira and SlackStarts on another system calling it · 15 stepsAirtableJiraSlackAlerts and monitoringAutomated failed login detection with Jira and SlackStarts on another system calling it · 15 stepsJiraNotionSlackAlerts and monitoringOrchestrate employee onboarding with Google Sheets and DriveStarts on another system calling it · 15 stepsGmailGoogle DriveGoogle SheetsJiraAlerts and monitoringCompany Review Monitor with SendGrid and HubSpotStarts on a clock · 16 stepsEmailHubSpotJiraSendGridAlerts and monitoringAggregate error alerts and send consolidated reportsStarts on a clock · 17 stepsEmailJiraAlerts and monitoringNotify customers of resolved Jira bugs with Gmail and HubSpotStarts on an event in a connected app · 18 stepsGmailGoogle SheetsHubSpotJiraAlerts and monitoringMonitor futures trades and send risk alerts with BinanceStarts on a clock · 19 stepsGmailGoogle SheetsJiraSlackAlerts and monitoringGenerate multi-pass Seedance AI roto mattes with NukeStarts on a change in a Google Sheet · 20 stepsGmailGoogle SheetsJiraSlackAlerts and monitoringAuto-create GitHub PRs & Jira updatesStarts on another system calling it · 21 stepsJiraNotionSlack

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.