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 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.

Is Gemini good for make scenario?

Yes. Gemini handles make scenario well thanks to its concise, factual output and precise instruction-following, and Promptivo tunes the prompt to match — precise phrasing with brief reasoning cues where they improve accuracy. Paste it into gemini.google.com.

Gemini 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.

Tuned for Gemini · structured role / context / task / output

Open in the builder →

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
Be precise and literal about the requirements. Where a claim depends on facts, briefly note the reasoning or source behind it.

- 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.
- Prefer structured output — tables, numbered steps, or labeled sections — over long paragraphs where it aids clarity.
- Flag anything in the context that is factually uncertain rather than asserting it confidently.
- Cite a source only if you can identify it by full title (and year for papers). Never fabricate a URL.
- Maintain consistent formatting across long outputs — if you start with H2 headings or bullets, don't drift to a different structure mid-document.
- 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

Customize this prompt

Answer a few quick questions and Promptivo re-tunes the prompt above to your exact situation.

Start the interview →

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.

Using this prompt in Gemini

For make scenario, Gemini is a strong choice — it's especially good at concise, factual output and precise instruction-following. Promptivo formats this prompt the way Gemini works best: precise phrasing with brief reasoning cues where they improve accuracy.

Paste it into gemini.google.com, then replace any bracketed details with your own. Gemini is sensitive to wording, so this prompt pins down the exact terms and structure to keep the result from drifting.

Tuned for Gemini: how it differs

Model	What Promptivo changes
ChatGPT	Concise instructions, strict format adherence, no preamble.
Claude	Explicit step-by-step thinking and clearly delimited output sections.
Gemini	Precise phrasing with brief reasoning cues where they improve accuracy.
Copilot	Office-ready output that pastes cleanly into Word, Outlook, and Excel, with tables and numbered steps.

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.
Is Gemini good for make scenario?: Yes. Gemini handles make scenario well thanks to its concise, factual output and precise instruction-following, and Promptivo tunes the prompt to match — precise phrasing with brief reasoning cues where they improve accuracy. Paste it into gemini.google.com.