Resources · Make integration

JsonCut Make integrationAutomate JsonCut with Make.

Can Make send files to JsonCut, start a job and pick up the result without you clicking through it? The JsonCut Make integration gives you 10 modules: 8 actions and 2 searches, built around jobs and files. This page walks a first-time Make user from connection to a live scenario.

Try the JsonCut integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the JsonCut Make integration do for you?

The JsonCut Make integration links your JsonCut account to Make so that a scenario, the automation you build in Make, can upload files, create and check jobs, and download files in JsonCut. Each step is a module, one brick of the scenario, and none of it needs code.

Hand files over as they appear. When another app in your scenario produces a file, Upload File sends it to JsonCut and Create a Job starts the work on it, so nobody has to repeat the upload by hand.

Get the output back in one pass. Wait for a Job to Complete holds the scenario until JsonCut is done, then Download a File brings the file into Make, ready for the next module of another app.

Keep your JsonCut storage in order. List Files and List Jobs show what is sitting in the account, and Delete a File removes what you no longer need.

Know the limit before you start: Make's documentation for JsonCut is marked as limited, with no official description of the fields, so test every module with a real file. Costs depend on your plan, see Make pricing, and when a run fails, Make troubleshooting covers the usual causes. Weighing another tool? The n8n vs Make comparison lays out the criteria.

Connect

How do you connect JsonCut to Make?

  1. 01

    Add a JsonCut module

    In your scenario, click the +, search for JsonCut and pick any of its modules. In the module panel, click Create a connection. A connection is your JsonCut account linked to Make once, then reused by every JsonCut module.

  2. 02

    Name the connection

    This step is optional but useful. Give the connection a name you will recognize later, such as the workspace or the client it belongs to, so you pick the right account when several are linked.

  3. 03

    Authorize and save

    Follow what Make asks for: either approve access on the JsonCut page that opens, or paste the key JsonCut gives you. Then click Save. The module can now read your account.

First scenario

Your first scenario with JsonCut

GoalWhen another app hands over a new file, Make uploads it to JsonCut and creates a job for it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. JsonCut has no trigger of its own, so the first module comes from the app where your files come from.

  2. 02

    Set the starting module

    Pick the trigger of that other app and connect it. Every file it finds becomes a bundle, one item passed from a module to the next, and the rest of the scenario runs once per bundle.

  3. 03

    Send the file to JsonCut

    Click the + on the right, search for JsonCut and add Upload File. Create the connection, then map the file coming from the first module into its fields.

  4. 04

    Start the job

    Add Create a Job after the upload and map what the previous module returned. Fill the remaining fields the module shows, since the doc does not describe them for you.

  5. 05

    Test with Run once

    Click Run once, drop a test file in the source app, and open the bubbles above each module to read the bundles it received. Fix the mapping until the job appears in JsonCut.

  6. 06

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default; the Free plan cannot go lower. Then switch the scenario on so it keeps running without you.

Modules

What each JsonCut module does

JsonCut gives you 10 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

JsonCut1

Create a Job

ActionIn the docs only

You get a new job started in JsonCut straight from the scenario, using the files or data earlier modules passed along. Validate a Job, Wait for a Job to Complete and Get the Job Details all work on what it starts.

When to use it
right after Upload File, when a fresh file should be processed without anyone opening JsonCut.
Watch out
the doc gives no field list, so run the module once and check the job in JsonCut before trusting it.
JsonCut2

Delete a File

ActionIn the docs only

This one frees your JsonCut storage by removing a file the scenario no longer needs, usually once its result has been downloaded elsewhere.

When to use it
as the last module, after Download a File has handed the output to another app.
Watch out
treat the delete as final, since nothing says a file can be restored, and place it only after the step that saved the file has succeeded.
JsonCut3

Download a File

ActionIn the docs only

Your file comes back from JsonCut into Make as data the next module can use, so you can attach it to an email, store it in a drive or send it to a client tool.

When to use it
after Wait for a Job to Complete, to collect what the job produced.
Watch out
on the Free plan Make handles files up to 5 MB, so large outputs need a paid plan.
JsonCut4

Get the Job Details

ActionIn the docs only

You receive the current information on one job, which lets the scenario decide what to do next based on where that job stands.

When to use it
when you already have a job reference, for example from Create a Job or List Jobs, and need to check it before going further.
Watch out
it reads one job at a time; to scan several, pair it with List Jobs.
JsonCut5

List Files

SearchIn the docs only

With this search you see which files sit in your JsonCut account. Each file comes out as its own bundle, so later modules run once per file.

When to use it
for a cleanup scenario that reviews stored files before sending some of them to Delete a File.
Watch out
a search can return zero, one or many bundles, and every module after it counts operations for each one.
JsonCut6

List Jobs

SearchIn the docs only

You get the jobs of your JsonCut account back as separate bundles, a quick way to see what was launched without opening the app.

When to use it
to build a report of jobs in a spreadsheet, or to feed Get the Job Details with each reference.
Watch out
like any search, it may return nothing; add a filter after it so an empty result does not break the next module.
JsonCut7

Make an API call

ActionIn the docs only

This module reaches any endpoint of the JsonCut API with the connection you already set up, which covers what the 9 other modules leave out.

When to use it
when the JsonCut documentation offers an operation that no listed module handles.
Watch out
you write the request yourself, path and body included, so keep the JsonCut API reference open while you fill it.
JsonCut8

Upload File

ActionIn the docs only

A file from any earlier module lands in your JsonCut account, ready for a job, without you downloading and re-uploading it by hand.

When to use it
first JsonCut step when the file comes from another app, such as a form attachment or a shared folder.
Watch out
map the file data itself, not only its name, or JsonCut receives nothing to work on.
JsonCut9

Validate a Job

ActionIn the docs only

Before anything starts, this module lets you check a job definition, so mistakes surface in the test run instead of in a failed job later.

When to use it
while you build the scenario, placed just before Create a Job with the same mapped values.
Watch out
the doc does not say what the check covers, so read the bundle it returns during Run once.
JsonCut10

Wait for a Job to Complete

ActionIn the docs only

Your scenario pauses on a job until JsonCut reports it done, so the next modules only run once there is something to pick up.

When to use it
between Create a Job and Download a File, in the same scenario.
Watch out
a run on the Free plan lasts 5 minutes at most, against 40 on paid plans, so a long job may outlast it.
Need help

Need help automating JsonCut with Make?

A person reads every message.

FAQ

JsonCut and Make: frequent questions

01Is the JsonCut Make integration free?
Yes, on the Make side. JsonCut is a standard app, available from the Free plan. That plan allows 2 active scenarios, a scheduled run every 15 minutes at most, 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and count usage in monthly credits. Your JsonCut account itself is a separate matter that this page does not cover.
02What do you need to connect JsonCut to Make?
A JsonCut account and a Make account. Make's documentation lists no specific prerequisite for JsonCut, so the standard steps apply: add a JsonCut module, click Create a connection, optionally name it, then either authorize Make on the page that opens or paste the key JsonCut provides, and save. The connection is then shared by every JsonCut module. Give the connection a clear name if you link more than one JsonCut account, so each scenario uses the right one.
03Does the JsonCut Make integration have a trigger?
No. JsonCut has no trigger module in Make, so a scenario cannot start from an event inside JsonCut. You have two ways to start. Use a trigger of another app, for example when a file arrives in your storage, then add the JsonCut modules after it. Or start directly on a JsonCut module and let Make's schedule run it, every 15 minutes by default. If you go with the schedule, remember that every run of that first module counts as an operation, even when there is nothing new to process.
04What if a JsonCut module is missing in Make?
Use Make an API call. It reaches any endpoint of the JsonCut API through the connection you already have, so an operation missing from the 10 modules can still be covered. Keep in mind that Make's documentation for JsonCut is flagged as limited, with no field descriptions, so check the JsonCut API reference and test each request with Run once. When a request works, keep it in its own scenario first so you can check the bundles it returns before chaining other modules.
05Should you use Make or n8n for JsonCut?
It depends on where the rest of your automations live. In Make, JsonCut comes with 10 ready modules covering jobs and files, plus an API call module for the rest, and a visual editor where each step is a bubble. This page has no information on a JsonCut node in n8n, so check that before choosing it. If your other scenarios already run in one of the two tools, keeping JsonCut there is the simplest path.
Same platform

Other docs you might need on this stack.

Browse all integrations