Skip to main content
Promptivo logoPromptivo
Build a prompt

Prompt to build a Make scenario

A Make (formerly Integromat) prompt: the trigger module (instant webhook or scheduled), the modules in order, routers and filters for branches, iterators and aggregators, error handlers, and how operations are counted.

Open in the builder →

Part of the workflow automation prompts collection: Power Automate, Logic Apps, Power Apps, Office Scripts, VBA, PowerShell, Copilot Studio, Zapier, Make and n8n. Writing your own? Read the automation prompt guide.

Ready-to-use prompt

# Role
You are an experienced workflow-automation architect who designs reliable, maintainable automations on the platform in use: a precise trigger, exact connector and action names, explicit conditions, error handling, and a test plan.

# Context
Build a Make scenario that watches a Typeform for new responses, creates a row in Airtable, and sends a Slack message with a router for high-priority answers.


# Task
Design the automation described in the context above for the stated platform: the trigger, each action in order with exact connector or action names, the conditions and approvals, error handling and retries, and how to test it before it goes live.

# How to approach this
Work the problem internally, then give only the result. Do not narrate your reasoning unless it is part of the deliverable.

- Lay the automation out in order: trigger, each action, the conditions and branches, error handling, then a test plan.

Before you finalize, verify that the trigger fires on exactly the intended event and nothing else; every action names the real connector, action, or command for the stated platform; the first failure has a handling path: retry, notify, or stop; the test plan covers the main path and that first failure.

# Constraints
- Do not invent connector, action, or command names. If unsure one exists, say so and use the closest real alternative.
- Follow the requested format exactly. Default to clean markdown. Be concise — no filler, no restating the question.
- Deliver the single best answer rather than hedging across several.
- When uncertain about a fact, API method, library name, or function signature, say so explicitly. Do not produce a plausible guess.
- Do not invent citations, URLs, or package names. If you don't know one, omit it or flag that you don't.
- Deliver the result directly — no apologies or meta-commentary about the prompt itself.

# Output format
Return only the requested output. If multiple distinct variants would clearly help, label them (e.g., "Option A", "Option B").

# Done when
- the output fully answers the goal in the Context section with no missing parts

Tuned for your model

Get a version optimized for the AI you actually use:

Why this prompt works

Make scenarios are built from modules and routes, so the prompt asks for the exact module names and the filter on each route.

Errors in Make are handled per module with handlers (Resume, Ignore, Rollback, Break, Commit). The prompt asks which handler goes where.

Operations drive cost. The prompt asks about volume and where an aggregator can cut operations.

Questions, answered

What should a Make scenario prompt include?
The trigger module and whether it is instant or scheduled, each module in order with its app and action, router routes with filters, iterators or aggregators for arrays, error handlers, and the expected volume.
How do I handle errors in Make?
Attach an error handler to the module that can fail and pick Resume, Ignore, Rollback, Break or Commit depending on whether the run should continue. The prompt asks for that choice.
Make or Zapier?
Make for visual branching, cheaper operations and data transformation in one scenario; Zapier for the widest app catalog and the quickest setup. The prompt designs for either.

Related prompts