How to Import JSON Into Make (Zapier's Competitor)

What JSON import does in Make

Make (formerly Integromat) lets you bring structured data from one tool into your workflows using JSON — a standard format that most apps and databases can export. When you import JSON, you're telling Make to read that data and use it to trigger actions, populate fields, or feed information into your next step. This is how you move contact lists from a spreadsheet into your CRM, pull order data from an API into your project management tool, or sync information between tools that don't have a direct connector.

The import happens in one of two ways: either you paste JSON directly into a module, or you connect to a source that outputs JSON (like a webhook, an API call, or a file storage service). Make then parses that JSON and maps each field to the right place in your workflow.

Key Takeaways

JSON data enters Make through a module — either by pasting it directly, connecting to an API, or uploading a file from Google Drive or Dropbox.
Make automatically detects the structure of your JSON and creates fields you can map to other tools in your workflow.
The JSON must be valid (properly formatted with correct brackets and quotes) or Make will reject it with a parsing error.
Once imported, you reference JSON fields using the dot notation (like data.email or user.name) in later workflow steps.

Pasting JSON directly into a module

The simplest route is to paste JSON into Make's JSON module. Open your Make scenario, click the plus icon to add a module, search for "JSON," and select "Parse JSON." In the "JSON string" field, paste your JSON data directly. Make will read it and show you the structure in the output panel on the right.

This works best for small, one-time imports or testing. If your JSON is large or changes frequently, you'll want to pull it from a source instead. Make will flag any syntax errors — missing commas, unmatched brackets, or quotes — so you can fix them before moving forward.

Importing JSON from an API or webhook

If your data lives in an API or comes in through a webhook, you don't paste anything. Instead, you use Make's HTTP module or a tool-specific connector to fetch the JSON. Click the plus icon, search for "HTTP," and select "Make a request." Enter the API endpoint URL, choose GET as the method, and add any headers or authentication your API requires.

When you run the module, Make fetches the JSON and automatically parses it. You'll see the structure in the output panel. If the API returns an array of objects (like a list of contacts), Make treats each object as a separate item and can loop through them in later steps. This is how you sync data in real time — every time the API updates, your workflow picks up the new information.

Uploading JSON from cloud storage

You can also store JSON files in Google Drive, Dropbox, or OneDrive and have Make read them. Add a module for your storage service (Google Drive, Dropbox, etc.), search for "Get file content," and select the file. Make downloads the file and passes its contents to the next module.

Follow that with a Parse JSON module, and Make will read the file's contents as JSON. This approach works well if you export data regularly from another tool and want Make to process it on a schedule. You can set up a trigger that runs every morning, pulls the latest file, and imports the data into your workflow.

Mapping JSON fields to other tools

Once Make has parsed your JSON, you reference its fields in other modules using dot notation. If your JSON has a structure like {"user": {"email": "name@example.com", "name": "Jane"}}, you would reference the email as user.email and the name as user.name. Click any field in a downstream module, and Make's autocomplete will show you the available fields from your JSON.

If your JSON contains an array (a list of items), Make can iterate through each item automatically. Use the "Iterator" module to loop through the array, and then reference fields from each item in the loop. This is how you import a list of 500 contacts and create a task for each one without writing any code.

Handling JSON errors and validation

Make will stop your workflow if the JSON is malformed. Common errors include missing commas between fields, unmatched curly braces or square brackets, or quotes around strings that aren't properly closed. If you see a parsing error, copy your JSON into a validator like jsonlint.com — it will highlight exactly where the problem is.

If your JSON comes from an API that sometimes returns errors or empty responses, add error handling. Use Make's "Error handler" to catch failed requests and either retry, skip the step, or send you a notification. This keeps your workflow from breaking when the source data is temporarily unavailable.

Frequently Asked Questions

Can I import JSON from a file on my computer?

Not directly — Make can't access files on your local drive. Upload the file to Google Drive, Dropbox, or OneDrive first, then use Make's cloud storage module to fetch it. Alternatively, paste the JSON directly into the Parse JSON module if it's a one-time import.

What's the difference between JSON and CSV?

CSV is a flat list of rows and columns, while JSON can have nested structure (objects inside objects). Make handles both, but JSON is better for complex data with relationships. If you have a CSV file, you can convert it to JSON using an online tool, or use Make's CSV module to read it directly.

How do I loop through a JSON array in Make?

Use the Iterator module. Set its input to your JSON array field, and Make will process each item one at a time. In the modules that follow, reference the fields from the current item using the Iterator's output notation (usually 1.fieldname).

Can I transform JSON before using it in my workflow?

Yes. After parsing, use the "Set variable" module to extract, rename, or restructure fields. You can also use the "Text aggregator" to combine multiple fields, or the "Array aggregator" to rebuild the JSON in a different shape before passing it to the next tool.

What happens if my JSON has fields I don't need?

Make imports all fields, but you only reference the ones you use. Unused fields don't slow down your workflow. If you want to clean up the data, use a Set variable module to extract only the fields you need and pass those forward instead.

This guide is for general information only and is not medical, financial, legal, or other professional advice. For decisions specific to your situation, consult a qualified professional. See our Editorial Policy.