Intermediate
How to test and save a scenario on Make
Quick Answer
Turn scenario OFF, use
Run once to test with varied data including edge cases, inspect module bubbles for outputs, fix errors via execution history, then switch ON to save and go live. Common issues like invalid connections or data mismatches are caught early with visual indicators (green/yellow/red). Enable advanced settings for hidden validations; total time 15-30 mins.Prerequisites
- Active Make.com account (Core plan recommended for unlimited tests)
- Connected apps with valid API keys or OAuth
- Sample or mock data bundles for triggers
- Basic understanding of scenario modules and data flow
1
Prepare scenario for testing
Review your scenario structure: locate the trigger module (webhook, schedule, or app event), check write operations (create/update/delete), and confirm filters/routers are correct. Ensure all modules are connected and configured properly.
2
Turn scenario OFF
In the Make.com dashboard, open your scenario and switch it to OFF to avoid automatic runs during testing. Verify connections and configurations before proceeding.
Tip
Free tier limits tests; upgrade to Core for unlimited operations.
3
Run manual test with Run once
Click the
Run once button in the scenario editor. Trigger input by sending a webhook request, updating a connected app record, or executing a data-pull module. Use sample/mock data to simulate without live risks.Tip
For webhooks, copy-paste previous run's JSON payload into a test HTTP module.
4
Inspect module outputs
After test completes, click bubbles above each module to view input/output data structures. Verify mapped fields have expected values and check for errors in data flow.
5
Test with varied data and edge cases
Run multiple
Run once tests using different inputs, including edge cases. Confirm branches, filters, and error handling work under various conditions for comprehensive coverage.Tip
Use previous execution bundles or set variables for Slack/app events to avoid waiting for triggers.
6
Check execution history and status icons
Review the bottom execution history panel for logs. Look for green checkmarks (success), yellow warnings, or red X (failures) on modules to identify issues quickly.
Tip
Enable
Show advanced settings to catch hidden validation errors.7
Fix mappings and connections
Remap fields if data mismatches occur, test connections individually, and resolve invalid API tokens or 401 errors. Re-run tests until all modules pass.
8
Turn scenario ON to save and go live
Once tests pass confidently, switch from OFF to ON in the editor. Scenarios auto-save; confirm schedule/timing if applicable. Now it processes real data.
Tip
Use sandbox for production-like tests without live effects.
Troubleshooting
"Connection invalid" or "401 Unauthorized"
Refresh expired API tokens/OAuth, test connections individually, and reauthorize apps.
Module errors (red X) or data mapping fails
Inspect bubbles and execution history logs, remap fields using correct bundle paths, run with sample data.
Quota/credit limits during tests
Upgrade to paid plan, use mock data or previous bundles, avoid loops/pagination in tests.
Filters/routers not behaving correctly
Test edge cases separately, verify conditions with varied inputs, check advanced settings.
Unsaved changes or auto-save issues
Run
Run once after edits (triggers save), duplicate scenario if needed for backups.Ready to get started with Make?
Put this tutorial into practice. Visit Make and follow the steps above.
Visit Make →