The 20-minute export guide
Everything the estimate needs, from your own account. No passwords, no API keys. Blueprints and workflow files never contain connection secrets, only connection names.
Make
- Each scenario. Open the scenario. Click the three dots next to the scenario name, then Export Blueprint. Save the
.json. Repeat for each scenario you want in the estimate; the ones that matter are enough to start. - Execution history. Open the scenario's History tab. Where the interface allows, download the last 30 to 90 days. If it does not, the Make API can list executions: in your profile, create an API token with read scope, call
GET https://<zone>.make.com/api/v2/scenarios/<id>/logsfor the date range, save the JSON, then revoke the token. - Operations and plan. Organization, then Subscription: note operations used this month and the plan. A screenshot is fine.
n8n
- Each workflow. Open the workflow, the three-dot menu, Download. On self-hosted:
n8n export:workflow --all --output=./workflows/. - Executions. On cloud, the API:
GET /api/v1/executions?workflowId=<id>&includeData=truewith a read API key, saved as JSON. On self-hosted:n8n export:execution --all --output=./executions/, or the last 30 to 90 days. - Credentials. Do not export them. Names are all we need, and they are already in the workflow file.
Zapier
- Team and Enterprise plans. Settings, Security and data, Export Zaps. A JSON file for your Zaps arrives by email.
- Other plans. There is no Zap export. Export your Zap history as CSV (Zap History, then Export) and add a short description of each Zap, or a screenshot of each editor. The estimate marks those steps for review.
Then
Zip the files, or upload them as they are, on the estimate page. Up to 50 MB. If the execution export is bigger than that, keep the last 30 days.
Get your estimate