Resources · Make integration

2ploon.com - JSON to Ploon Converter Make integrationAutomate 2ploon.com - JSON to Ploon Converter with Make.

Need JSON turned into Ploon without leaving your automation? The 2ploon.com - JSON to Ploon Converter Make integration gives you 2 action modules. This guide shows how to link your account, build a first scenario and pick the right module.

Try the 2ploon.com - JSON to Ploon Converter integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the 2ploon.com - JSON to Ploon Converter Make integration do?

The integration lets a Make scenario, the automation you build as a chain of modules, send JSON data to 2ploon.com and get it back in Ploon format. A module is one brick of that chain. Here there are two, both actions, so something else has to start the flow.

Convert data a form or a database just produced. Put another app's module first, then Transform JSON to Ploon right after it. Each bundle, meaning one item passing from one module to the next, arrives as JSON and leaves converted.

Feed the converted output to the rest of your stack. Once the conversion step exists, click the + next to it and map its result into whatever app should receive it, a file storage tool or a message, for example.

Reach the parts of the 2ploon.com API that have no module. Make an API Call reuses your connection to call any endpoint of the API, which covers what the converter module leaves out.

Know the limits before you start: Make says the public documentation for this app is limited, so it lists no prerequisites, fields or quotas. Test with Run once and read what comes back. If you are still weighing platforms, the same app may also have an n8n node, and our n8n vs Make comparison lays out how the two work. For plan details see Make pricing, and if a run fails, Make troubleshooting is the place to start.

Connect

How do you connect 2ploon.com to Make?

  1. 01

    Add a module and open the connection

    In your scenario, add any 2ploon.com module, then click Create a connection. A connection is your 2ploon.com account linked to Make once, and every module of the app reuses it afterwards.

  2. 02

    Give it a name you will recognize

    Naming the connection is optional, but it helps as soon as you own more than one account or share the scenario with a teammate. Something like the project or client name is enough to tell them apart later.

  3. 03

    Authorize Make and save

    Either approve access on the 2ploon.com page that opens, or paste the key 2ploon.com gives you, depending on what the window asks for. Then click Save and the module is ready to fill.

First scenario

Your first scenario with 2ploon.com and Make

GoalWhen another app hands Make a JSON record, Make converts it to Ploon with 2ploon.com.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to place the first module. Pick the app whose data you want to convert, since 2ploon.com has no trigger of its own.

  2. 02

    Add the converter

    Click the + on the right of that first module, search for 2ploon.com and choose Transform JSON to Ploon. Click Create a connection if your account is not linked yet.

  3. 03

    Map the JSON in

    Fill the module by mapping the JSON produced by the previous module. Make shows the data it received from that module, so you pick values instead of typing them.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time, and you can open each module to read the bundles it received and check that the Ploon output looks right.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Modules

What each 2ploon.com module does

2ploon.com - JSON to Ploon Converter gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

2ploon.com - JSON to Ploon Converter1

Make an API Call

ActionIn the docs only

You get direct access to any 2ploon.com API endpoint from your scenario, signed in with the connection you already created.

When to use it
pick it when the conversion module does not offer the request you need and the 2ploon.com API does.
Watch out
Make's documentation for this app is limited, so check the endpoint on the 2ploon.com side before you rely on it.
2ploon.com - JSON to Ploon Converter2

Transform JSON to Ploon

ActionIn the docs only

This module gives you your JSON back in Ploon format, ready for the next module to use. It is the core of the integration and the one most scenarios need.

When to use it
right after the module that produces the JSON, such as a form submission or a record fetched from another app.
Watch out
no fields or limits are documented, so run it once and inspect the output bundle before mapping it further.
Need help

Need help automating 2ploon.com - JSON to Ploon Converter with Make?

A person reads every message.

FAQ

2ploon.com and Make: common questions

01Is the 2ploon.com - JSON to Ploon Converter Make integration free?
Yes, on the Make side. It is a standard app, available from the Free plan onward. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, runs of up to 5 minutes, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow runs of up to 40 minutes. Usage is counted in operations each month, and whatever 2ploon.com itself charges sits outside this answer.
02What do you need to connect 2ploon.com to Make?
A 2ploon.com account and a Make account. The documentation lists no other prerequisite. In a module, click Create a connection, optionally name it, then either authorize Make on the 2ploon.com page or paste the key the service gives you, and click Save. The connection is stored once and every module of the app reuses it, so you do not repeat this step when you add Make an API Call later in the same scenario.
03Does 2ploon.com trigger Make scenarios in real time?
No, because the app has no trigger module at all. Both of its modules are actions, so the scenario has to start somewhere else. You can open it with a trigger from the app that produces your JSON, and then it fires when that app does. Or you can rely on the schedule of the first module, which is every 15 minutes by default, down to 1 minute on paid plans. Either way, the converter then runs on each bundle that reaches it.
04What if a 2ploon.com module is missing in Make?
Use Make an API Call. It reaches any endpoint of the 2ploon.com API with the connection you already set up, so you are not limited to the conversion module. Keep in mind that Make describes its documentation for this app as limited, so it does not list fields, formats or quotas. Check the 2ploon.com API on the service side before you build on it, and test each call with Run once before switching the scenario on.
05Should you use Make or n8n for 2ploon.com?
It depends on the platform you already work in. On Make, 2ploon.com gives you 2 action modules: Transform JSON to Ploon and Make an API Call, which is enough to slot a conversion step into a scenario. The same app may also have an n8n node. Whichever tool your team already uses is usually the sensible place to add a conversion step, and checking which modules each side offers is the fairest way to decide.
Same platform

Other docs you might need on this stack.

Browse all integrations