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

45 found

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

Customer supportAIAutomate multi-channel customer support with GmailStarts on an incoming Telegram message · 21 stepsGmailGoogle SheetsTelegramCustomer supportAIBuild a Telegram AI assistant with MemMachine and OpenAIStarts on an incoming Telegram message · 21 stepsGmailGoogle CalendarGoogle SheetsTelegramCustomer supportAIHR & IT helpdesk chatbot with OpenAI and TelegramStarts on an incoming Telegram message · 21 stepsTelegramCustomer supportAIRun a customer support RAG chatbot with OpenAIStarts on someone opening a chat with it · 21 stepsGoogle DriveTelegramin-memory vectorsCustomer supportAIAnswer Telegram data questions with DeepSeek and Open-MeteoStarts on an incoming Telegram message · 25 stepsGoogle SheetsTelegramCustomer supportAITelegram request router with DeepSeek and OpenAIStarts on an incoming Telegram message · 25 stepsTelegramCustomer supportAIAutomated customer support system with GmailStarts on someone submitting a form · 31 stepsGmailGoogle SheetsQdrantTelegramCustomer supportAIAutomate Telegram support handover from AI to humans with GPT4Starts on an incoming Telegram message · 33 stepsEmailTelegramn8n data tableCustomer supportAIMulti-department support bot with Pinecone and TelegramStarts on an incoming Telegram message · 46 stepsGoogle DrivePineconePostgresTelegramCustomer supportAICreate a multi-modal Telegram support bot with OpenAIStarts on an incoming Telegram message · 48 stepsGoogle DriveSupabase vectorsTelegramCustomer supportAnswer questions with Telegram and TavilyStarts on an incoming Telegram message · 5 stepsTelegramCustomer supportFast-track VIP tickets with Google Sheets and ClickUpStarts on an event in a connected app · 6 stepsClickUpTelegramZendeskCustomer supportReal-time Vtiger support tickets to TelegramStarts on a clock · 6 stepsTelegramCustomer supportCreate ticket on specific customer messages in TelegramStarts on an incoming Telegram message · 8 stepsTelegramCustomer supportBuild a Telegram mental health support bot with OpenAIStarts on an incoming Telegram message · 9 stepsTelegramCustomer supportPublish Telegram messages to LinkedIn postsStarts on an incoming Telegram message · 9 stepsLinkedInTelegramCustomer supportZendesk ticket escalation to ClickUp with TelegramStarts on an event in a connected app · 9 stepsClickUpTelegramZendeskCustomer supportAI Customer Support Bot: Telegram + Groq + Google SheetsStarts on an incoming Telegram message · 10 stepsGmailGoogle SheetsTelegramCustomer supportCreate a two-way WhatsApp + Telegram integrationStarts on an incoming WhatsApp message · 18 stepsSupabaseTelegramWhatsAppCustomer supportAnswer FAQs and route Telegram users to support with PostgresStarts on an incoming Telegram message · 29 stepsPostgresTelegramCustomer supportAdvanced Telegram bot, ticketing system, liveChat, userStarts on an incoming Telegram message · 31 stepsRedisTelegram

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.