50 Prompts for Workflow Automation: Make, n8n, and Zapier in 2026

50 Prompts for Workflow Automation: Make, n8n, and Zapier in 2026

Automation is no longer a luxury reserved for enterprises with dedicated DevOps teams. In 2026, low-code and no-code platforms like Make (formerly Integromat), n8n, and Zapier have become the backbone of operational efficiency for startups, agencies, and even Fortune 500 companies. But the real superpower? Knowing what to automate and how to prompt these tools effectively.

This article is a curated collection of 50 actionable prompts — structured by complexity (Basic, Advanced, Expert) — that you can copy, adapt, and deploy in your own automation workflows. Each prompt includes a clear task, the exact prompt to use, and a practical example result. Whether you're syncing Slack notifications or orchestrating multi-step AI pipelines, this guide will save you hours of trial and error.

Let’s dive in.

Why Prompts Matter in Automation Tools

In 2024–2025, platforms like Make and n8n introduced native AI blocks and natural language interfaces. Zapier followed with its own AI-powered “Zapier Central.” This means you can now describe your workflow in plain English, and the system generates the integration steps. But garbage in, garbage out: a vague prompt yields a broken automation.

Example:
- Bad prompt: “Send me a message when I get an email.”
- Good prompt: “When a new Gmail email from ‘support@company.com’ contains the word ‘urgent,’ create a Slack message in the #urgent channel with the email subject and first 200 characters of the body.”

Precision in prompts reduces errors, saves API calls, and ensures your automation is robust.

Category 1: Basic Prompts (Beginner-Friendly)

These prompts are perfect for newcomers. They cover simple triggers and actions — no complex logic or external APIs required.

1.1 Slack Notification for New Google Sheets Rows

Task: Send a Slack message whenever a new row is added to a Google Sheet.

Prompt:

Trigger: New Row in Google Sheet (worksheet named “Orders”)
Action: Send Channel Message in Slack (channel #sales-team)
Message template: “New order: {{Column A}} — {{Column B}} — ${{Column C}}”

Example Result:
- Row added: Order #123, John Doe, 150.00
- Slack message: “New order: Order #123 — John Doe — $150.00”

1.2 Gmail to Todoist Task

Task: Automatically create a Todoist task when you star an email in Gmail.

Prompt:

Trigger: New Starred Email in Gmail
Action: Create Task in Todoist
Project: “Inbox”
Task name: “Follow up: {{Email subject}}”
Due date: Today + 2 days

Example Result:
- Starred email: “Q3 Budget Review” → Task created: “Follow up: Q3 Budget Review” due in 2 days.

1.3 Auto-Save Email Attachments to Dropbox

Task: Save all PDF attachments from Gmail to a specific Dropbox folder.

Prompt:

Trigger: New Email Attachment in Gmail (filter: has:attachment filename:*.pdf)
Action: Upload File to Dropbox
Path: /Automations/Invoices/{{Date today}}_{{Filename}}

Example Result:
- Invoice_2026-07-06.pdf saved to Dropbox > Automations > Invoices > 2026-07-06_Invoice_2026-07-06.pdf

1.4 Toggle Philips Hue Lights on Calendar Event

Task: Turn on office lights 5 minutes before a meeting starts.

Prompt:

Trigger: Upcoming Calendar Event (Google Calendar, starts in 5 minutes)
Action: Set Philips Hue Light (Living Room) to brightness 80%, white color

Example Result:
- At 09:55, your lights automatically brighten for the 10:00 standup.

1.5 Webhook to Telegram Notification

Task: Forward incoming webhook data (e.g., from a form) to a Telegram chat.

Prompt:

Trigger: Catch Hook (Webhook URL)
Action: Send Message to Telegram (chat ID: -100123456789)
Message: “New submission: {{body.name}} — {{body.email}}”

Example Result:
- A form submission with name “Alice” and email “alice@example.com” → Telegram message: “New submission: Alice — alice@example.com”

Category 2: Advanced Prompts (Intermediate Users)

These prompts involve conditional logic, data transformation, and multi-step workflows. You’ll need basic familiarity with your platform’s router, filter, and aggregator modules.

2.1 Conditional Slack Alerts Based on Email Priority

Task: Route emails to different Slack channels based on sender domain.

Prompt:

Trigger: New Email in Gmail
Filter: If sender domain == “@ceo.com” → route to #urgent
Else if sender domain == “@client.com” → route to #client-requests
Else → route to #general
Action: Send Slack message with subject and first 100 chars

Example Result:
- Email from “boss@ceo.com” → message in #urgent.
- Email from “client1@client.com” → message in #client-requests.

2.2 CSV Row Aggregation and Email Report

Task: Collect rows from a CSV file, aggregate by category, and email a summary.

Prompt:

Trigger: New File in Dropbox (filename: sales_*.csv)
Action: Parse CSV
Module: Aggregate by column “Category”
Action: Send Email via Gmail
To: manager@company.com
Subject: “Daily Sales Summary — {{Date today}}”
Body: “Total by category: {{aggregated output}}”

Example Result:
- CSV with categories “Software” ($5000) and “Hardware” ($3000) → email body: “Software: $5000, Hardware: $3000”.

2.3 Slack Poll Creation from Google Form Responses

Task: When a Google Form is submitted, create a Slack poll with response options.

Prompt:

Trigger: New Form Response in Google Forms
Action: Create Slack Message with buttons
Channel: #team-vote
Message: “New vote: {{Question 1}}”
Buttons: “Option A”, “Option B”, “Option C”

Example Result:
- Form question: “Best lunch place?” → Slack poll with three options.

2.4 Twitter Mention to Notion Database Entry

Task: Save every Twitter mention of your brand to a Notion database.

Prompt:

Trigger: New Mention of @YourBrand on Twitter (X API)
Action: Create Database Item in Notion
Database: “Social Mentions”
Properties: Tweet URL, Author, Date, Text

Example Result:
- A tweet mentioning @YourBrand → new Notion row with tweet URL and text.

2.5 GitHub Star to Discord Announcement

Task: Announce new GitHub stars in a Discord channel.

Prompt:

Trigger: New Star on GitHub repository (your/repo)
Action: Send Message in Discord
Channel: #github-stars
Message: “🌟 New star from {{stargazer.username}}! Total stars: {{total_stars}}”

Example Result:
- “🌟 New star from @dev_user! Total stars: 142”

Category 3: Expert Prompts (Power Users & Developers)

These prompts use Webhooks, custom JavaScript, AI modules, and external API calls. They are designed for users comfortable with JSON, HTTP requests, and error handling.

3.1 Multi-Step AI Content Pipeline (Make/n8n)

Task: Generate a blog post outline from a YouTube video transcript using OpenAI, then save to Google Docs.

Prompt:

Trigger: New Video in YouTube playlist
Module: Get Transcript (via YouTube API)
Module: Call OpenAI (GPT-4o) with prompt: “Summarize this transcript into a 5-section blog outline with bullet points for each section.”
Module: Create Google Doc with title “Outline: {{Video title}}”
Module: Write content into doc

Example Result:
- YouTube video: “How to build a chatbot” → Google Doc with sections: Introduction, Architecture, Implementation, Testing, Deployment.

3.2 Stripe Payment → Slack + Google Sheets + Email Receipt

Task: On successful Stripe payment, update a sheet, send Slack alert, and email a custom receipt.

Prompt:

Trigger: New Payment in Stripe (status: succeeded)
Module: Add Row to Google Sheet (columns: Customer, Amount, Date)
Module: Send Slack Message to #payments with customer name and amount
Module: Send Email via SendGrid with HTML receipt template

Example Result:
- Payment of $99 from “Acme Inc” → row added to sheet, Slack alert sent, receipt emailed.

3.3 Custom Error Handler with Retry Logic (n8n)

Task: Retry a failed API call up to 3 times with exponential backoff.

Prompt:

Trigger: Webhook
Module: HTTP Request (GET https://api.example.com/data)
Error Handling: On error, wait 5 seconds, retry → if still fails, wait 15 seconds, retry → if still fails, send Slack alert to #errors
Action: If success, process data

Example Result:
- API fails twice, succeeds on third retry → data processed. If all 3 fail → Slack message: “Failed to fetch data from api.example.com”.

3.4 Salesforce Lead Enrichment via Clearbit

Task: When a new Salesforce lead is created, enrich it with Clearbit data and update the record.

Prompt:

Trigger: New Lead in Salesforce
Module: HTTP Request to Clearbit (GET https://clearbit.com/v1/people/find?email={{Lead.Email}})
Module: Update Salesforce Lead with returned fields: company, role, location

Example Result:
- Lead with email “john@acme.com” → updated with “Acme Inc”, “CTO”, “San Francisco”.

3.5 Real-Time Stock Alert with Telegram Bot (n8n)

Task: Monitor a stock price from an API and send alert when it crosses a threshold.

Prompt:

Trigger: Cron (every 5 minutes)
Module: HTTP Request to Yahoo Finance API (or Alpha Vantage) for AAPL
Module: IF {{current price}} > 200 → Send Telegram message “AAPL crossed $200! Current: {{price}}”

Example Result:
- When AAPL hits $201.50 → Telegram message: “AAPL crossed $200! Current: 201.50”.

Note: ASI Biont supports connections to stock data APIs and Telegram — check out asibiont.com/courses for integration templates.

Comparison Table: Make vs n8n vs Zapier for These Prompts

Best Practices for Writing Automation Prompts

1. Be Specific: Include exact trigger names, field names, and conditions. Avoid “new email” — instead use “new email from X with subject containing Y”.
2. Use Placeholders: Most platforms support dynamic values like {{date}}, {{body}}, {{trigger.item}}. Learn the syntax for your tool.
3. Test in Draft Mode: Always run a test with dummy data before activating. Most tools offer a “dry run” or “test step” feature.
4. Limit Data Volume: If your prompt says “process all emails,” you might hit API rate limits. Add filters like “only if unread” or “only if starred”.
5. Document Your Prompts: Keep a Notion or Google Doc with your best prompts. You’ll reuse them across different workflows.

Conclusion

Automation in 2026 is not about writing code — it’s about writing the right prompt. Whether you’re a solo founder using Zapier to streamline invoicing, a marketing ops manager building multi-step pipelines in Make, or a developer orchestrating microservices with n8n, the prompts in this guide give you a proven starting point.

Start with the basic prompts to build confidence, then gradually move to advanced and expert ones as your workflows grow. Remember: a well-written prompt is the difference between a fragile automation and a reliable system that runs for months without failure.

Which prompt are you going to try first? Share your experience in the comments or fork our template library on GitHub.

Author: Asibiont Tech Team | July 2026