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

44 found

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

Customer supportAIBuild a customer support RAG agent with OpenAI and TelegramStarts on an incoming Telegram message · 7 stepsPineconeTelegramCustomer supportAIAutomated Gmail support agent with Gemini and RAGStarts on an arriving email · 8 stepsGmailPineconeCustomer supportAIAI-powered Gmail customer support with OpenRouter and PineconeStarts on an arriving email · 9 stepsGmailPineconeCustomer supportAIAutomated customer support agent - Gmail + OpenAI + RAGStarts on an arriving email · 9 stepsGmailPineconeCustomer supportAICreate knowledge base from Jira tickets with OpenAIStarts on a clock · 9 stepsJiraPineconeCustomer supportAIRun a Telegram support bot with OpenAI and PineconeStarts on an incoming Telegram message · 9 stepsGoogle SheetsPineconeTelegramCustomer supportAIAI Gmail support automation with Gemini and OpenAIStarts on an arriving email · 10 stepsGmailPineconeSlackCustomer supportAIAI-powered email replies with FAQ and OpenAIStarts on an arriving email · 10 stepsGmailPineconeCustomer supportAIAnswer WhatsApp support chats with OpenRouter and PineconeStarts on an incoming WhatsApp message · 10 stepsGmailPineconeWhatsAppCustomer supportAIAutomate FAQ replies and follow-ups in n8n with OpenAIStarts on someone opening a chat with it · 10 stepsAirtablePineconeCustomer supportAIGmail customer support auto-responder with Ollama LLMStarts on an arriving email · 10 stepsGmailPineconeCustomer supportAIAnswer employee HR questions on Telegram with OpenAIStarts on an incoming Telegram message · 11 stepsPineconeTelegramCustomer supportAICustomer Support Chat Agent with OpenAI and Google DriveStarts on an event in a connected app · 11 stepsGoogle DrivePineconeCustomer supportAIZendesk ticket summarizer with Pinecone and OpenAIStarts on a clock · 11 stepsPineconeSlackZendeskCustomer supportAIAutomated product email support with OpenAI and Pinecone RAGStarts on an arriving email · 12 stepsGmailPineconeCustomer supportAIAutomated Jira ticket responses with OpenAI and PineconeStarts on a clock · 13 stepsJiraPineconeCustomer supportAICreate AI support assistant for any device with OpenAIStarts on another system calling it · 13 stepsPineconeCustomer supportAICustomer support chatbot with RAG and OpenAIStarts on someone opening a chat with it · 13 stepsGoogle DrivePineconeCustomer supportAIQ&A AI agent: The future of customer service and supportStarts on someone opening a chat with it · 13 stepsGoogle DrivePineconeCustomer supportAIAnswer WhatsApp questions from PDF documents with RAGStarts on an incoming WhatsApp message · 14 stepsGoogle DrivePineconeWhatsAppCustomer supportAICreate a travel support RAG chatbot with Google DriveStarts on another system calling it · 14 stepsGoogle DrivePineconeCustomer supportAIIT support chatbot with Google Drive and PineconeStarts on someone opening a chat with it · 14 stepsGoogle DrivePineconeCustomer supportAIAnswer Slack knowledge base questions with Notion and PineconeStarts on a clock · 15 stepsNotionPineconeSlackCustomer supportAIAnswer document questions with OpenAI and PineconeStarts on another system calling it · 15 stepsGoogle DrivePinecone

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.