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

66 found

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

AI assistantsAIEnhance customer chat by buffering messages with TwilioStarts on an event in a connected app · 13 stepsRedisTwilioChat assistantsAIHotel receptionist with WhatsApp and GeminiStarts on an incoming WhatsApp message · 13 stepsGoogle SheetsRedisWhatsAppData collectionAIAutomate Instagram comment replies with OpenAI and RedisStarts on a clock · 14 stepsRedisCustomer supportAICustomer authentication for chat support with OpenAI and RedisStarts on someone opening a chat with it · 14 stepsRedisAI assistantsAIImplement intelligent message buffering for AI chatsStarts on someone opening a chat with it · 16 stepsRedisAlerts and monitoringAITriage security vulnerability alerts with NVD and GeminiStarts on another system calling it · 17 stepsJiraRedisSupabaseAI assistantsAIGenerate creative solutions with RedisStarts on someone opening a chat with it · 18 stepsRedisAlerts and monitoringAIMonitor GitHub releases with Gemini and SlackStarts on a clock · 18 stepsRSSRedisSlackSchedulingAIAutomate meeting intelligence with VEXA and OpenAIStarts on another system calling it · 22 stepsBaserowRedisData collectionAIAutomatic service with Gemini and PostgresStarts on another system calling it · 22 stepsPostgresRedisChat assistantsAIEnd of turn detection for smoother AI agent chatsStarts on an incoming Telegram message · 23 stepsRedisTelegramE-commerceAIRAG eCommerce chatbot with OpenAI and GmailStarts on another system calling it · 23 stepsGmailQdrantRedisShopifyData collectionAIServe a RAG chat backend for Next.js with OpenAI and RedisStarts on another system calling it · 23 stepsPineconePostgresRedisSchedulingAIHandle healthcare appointments on WhatsApp with GeminiStarts on an incoming WhatsApp message · 24 stepsGoogle CalendarGoogle SheetsRedisWhatsAppData collectionAITaxi service provider with Grok and PostgresStarts on someone opening a chat with it · 24 stepsPostgresRedisAI assistantsAIAutomating WhatsApp replies with Go High Level and RedisStarts on another system calling it · 25 stepsGoogle DriveRedisAI assistantsAIWhatsApp unofficial AI bot with Groq and PineconeStarts on another system calling it · 26 stepsPineconeRedisAI assistantsAIAI chatbot call center: Demo call center with Grok and RedisStarts on someone opening a chat with it · 27 stepsRedisDocuments and filesAICreate a WhatsApp chatbot with OpenAI and WhisperStarts on an event in a connected app · 27 stepsRedisChat assistantsAIDebounce and buffer WhatsApp AI replies with Redis and GeminiStarts on an incoming WhatsApp message · 29 stepsRedisWhatsAppCRMAITelegram AI bot-to-human handoff for sales calls with OpenAIStarts on an incoming Telegram message · 30 stepsRedisTelegramSchedulingAIAI secretary for scheduling with WhatsApp and TelegramStarts on an incoming Telegram message · 31 stepsGoogle CalendarRedisTelegramCRMAIAnalyze customer feedback and send AI-written repliesStarts on another system calling it · 31 stepsEmailGoogle SheetsHubSpotPostgresData collectionAIAI chatbot call center: Taxi service with Grok and PostgresStarts on someone opening a chat with it · 33 stepsPostgresRedis

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.