Skip to content

Make

Map data between apps in a visual scenario, branch when a condition changes and inspect what ran.

Visit Make

How do you map a signup through a Make scenario?

A scenario is Make’s name for a workflow. A module is one step. Start with the fields you receive, then map each field into the place it belongs.

Draw the scenario on paper with no connected account. When you later use an inactive practice scenario, confirm the account and destination before clicking Run once. It can still perform the configured actions.

  1. Start with a fake signup
    Write demo-103, a made-up name and the interest “wants a demo.” Draw the starting module and the record you want at the end.
  2. Map the ID as a record key
    Use demo-103 as the key in your paper Data store. Write the interest as a field. In the actual module, keeping overwrite off makes another add with that key return an error.
  3. Check a repeated input
    Deliver demo-103 twice and look up the saved record. Treat the confirmed duplicate as already recorded. Keep a different error open for investigation.

When should you retry an incomplete execution?

An incomplete execution keeps the input for a failed part of a run. If the error is temporary, the documented retry can start again at the failing module. Turn on incomplete executions before relying on the Retry handler.

Instant webhooks can run in parallel by default. Processing them in order can help one scenario, while a destination key still protects against repeat writes from another path.

Three ways a Make run can continue or stop
ActionWhat to expect
Retry an incomplete executionThe failing module starts with its earlier input. Check whether its destination already changed.
Replay a runThe current scenario receives the old trigger input. Earlier modules can run again.
Use RollbackMake can reverse changes made by supported transaction modules under the configured commit settings. Confirm anything an outside app already did.

What is a Make credit?

A standard operation on a non-AI module generally uses one credit. Make’s Free plan listed 1,000 credits per month in November 2026.

Count the operations that actually run on the chosen path. AI modules and features may use credits differently, and an outside AI provider may charge separately. Make lists 1 MB of Data store space on Free, so check the space left before relying on it.

What does a Make blueprint carry to another account?

A scenario blueprint carries modules, settings and mapped values as JSON. When you import it, create the account connections for the destination account again.

Review the mapped values before sharing a blueprint. Keep a separate copy of any data you need and verify the imported modules point to the intended accounts and data stores before enabling a schedule.