Make Setup Guide
Free
Connect a small test workflow and inspect how data moves between modules.
BEGINNER / VISUAL AUTOMATION
1. Set the stage
A Make scenario is a series of modules. Begin with two practice apps or a small test dataset, not an unattended production workflow.
1. Create a practice scenario
Sign in at make.com and create a scenario in the intended team. Name it clearly as a test before adding connections.
2. Choose the first module
Select the event or data source that starts the scenario. Connect a test account and provide one predictable record to work with.
3. Map the next action
Add a second module and map the needed fields. Review exactly where data will be written; avoid unnecessary fields or permissions.
4. Run once & inspect
Use Run once, inspect the module results, and confirm the destination record. Configure schedule and failure handling only after the test works.
2. Lean working stack
| Stage | Role | | --- | --- | | Test source | Provide one record | | Make | Map & transform | | Test destination | Write once | | Run history | Inspect the result |
Arrows in the visual sheet show the order of work. External connections require separate setup. Optional tools may be replaced with ones you already use. This is a suggested stack for this task, not a universal optimum.
Map fields intentionally
A visible field name is not proof of the correct value. Inspect the test bundle and confirm the destination gets the intended data type and content.
Start without AI
Prove the trigger and action first. Add an AI module later only for a task that cannot be handled more clearly by ordinary mapping or logic.
3. First practice task
In a test scenario, take one sample request from a practice sheet and write a summary to a separate test sheet. Run once, compare the fields, and leave scheduling off until the result is correct.
Your setup is working when
Exactly the intended test record appears, its mapped fields are correct, and you can locate the run result and understand how to stop the scenario.
Troubleshooting
Wrong value? Inspect the mapped bundle. No trigger data? Add a fresh test record. Repeated writes? Review trigger behavior and duplicate handling.
Series 38 / 40