Resources · Make integration

PlatoForms Make integrationAutomate PlatoForms with Make.

Can Make fill and fetch your PlatoForms forms for you? The PlatoForms Make integration gives you 6 action modules and no trigger. This guide shows how to link your account, build a first scenario and pick the right module.

Try the PlatoForms integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the PlatoForms Make integration do?

The PlatoForms Make integration links your PlatoForms account to Make so a scenario, the automation you build as a chain of modules, can list your forms, read their fields, send a submission or download a file. Each module is one brick of that chain. PlatoForms has no trigger in Make, so something else has to start the run.

Forms sent without retyping. For a sales team, a new deal in a CRM can start the scenario, and Submit Form pushes the client's details into your PlatoForms form. While you build, Get Form Fields shows you which fields that form holds.

Files that land where they belong. Download File brings a file from PlatoForms into the scenario, and the next module, from a storage or email app, sends it on. An office manager stops saving attachments by hand.

An inventory of your forms. Get Forms returns the forms of the account; paired with a spreadsheet app, it keeps a list your team can read.

What Make does not do here: no module watches PlatoForms on its own, so the scenario runs on its schedule (every 15 minutes by default) or on another app's trigger. The PlatoForms page of the Make documentation also warns that its content is AI-generated and may contain mistakes, so check the result with Run once. Before you commit, compare Make pricing, read n8n vs Make if you hesitate between the two, or learn the editor with Make training.

Connect

How do you connect PlatoForms to Make?

  1. 01

    Add a PlatoForms module

    In your Make account, open a scenario, add any PlatoForms module and click Create a connection. A connection is your PlatoForms account linked to Make once, then reused by every PlatoForms module you add later.

  2. 02

    Name the connection

    The Connection name field is optional. Give it a name you will recognize, such as the account owner or the team, which helps once several PlatoForms accounts sit side by side in Make.

  3. 03

    Paste your credentials

    Enter the credentials copied from PlatoForms, either a non-expiring token or the Client ID and Client secret of an OAuth2 application, or follow the instructions Make shows on screen. For OAuth2, create the app under API Webhooks in your PlatoForms profile.

First scenario

Your first scenario with PlatoForms

GoalWhen a new record shows up in another app, Make sends it to a PlatoForms form with Submit Form.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Since PlatoForms has no trigger, this first module comes from the app where your new records appear.

  2. 02

    Add Submit Form

    Click the + on the right of that first module, search PlatoForms and pick Submit Form. Click Create a connection if your account is not linked yet.

  3. 03

    Map the data

    Fill the module fields with values from the previous module: a name, an email, whatever your form expects. Make lists what it can read once the connection exists.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, a bundle being one item passed along, like one contact. Check the submission in PlatoForms.

  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 counts as one operation, the unit Make counts on your plan.

Modules

What the PlatoForms modules do

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

PlatoForms1

Download File

ActionIn the docs only

Download File pulls a file out of your PlatoForms account and hands it to the next module, so a storage app or an email can receive it without you saving anything by hand.

When to use it
a document kept in PlatoForms has to reach a shared folder or a colleague's inbox.
Watch out
on the Free plan Make handles files up to 5 MB, so a heavier file may stop the run; test with Run once first.
PlatoForms2

Get Form Fields

ActionIn the docs only

With Get Form Fields you see, inside Make, which fields one of your PlatoForms forms contains, so mapping data later becomes a matter of matching names instead of guessing.

When to use it
while you build a scenario around Submit Form and need the field list of the target form.
Watch out
every run of this module costs one operation, so remove it from the scenario once your mapping is settled.
PlatoForms3

Get Forms

ActionIn the docs only

Get Forms gives you the forms of your PlatoForms account inside the scenario, which saves you from copying form references one by one when a later module needs them.

When to use it
you manage several forms and want to find the right one, or feed a list to a spreadsheet app.
Watch out
it is an action, not a trigger, so it only runs when the schedule or an earlier module starts the scenario.
PlatoForms4

Make API Call

ActionIn the docs only

Make API Call is the PlatoForms module for a request the five others do not cover, going by its name; the documentation describes nothing more, so treat it as a lead to test.

When to use it
a PlatoForms feature you rely on has no dedicated module in Make.
Watch out
the Make documentation gives no detail on this module, so read the PlatoForms API reference and test every request with Run once.
PlatoForms5

Submission Watch

ActionIn the docs only

Submission Watch brings PlatoForms submissions into the scenario, judging by its name. Despite the word watch, Make lists it as an action, which changes how you start it.

When to use it
you want the scenario to look at your form submissions each time its schedule fires.
Watch out
it carries no clock or lightning badge, so it never starts a scenario by itself; place it after a schedule or another app's trigger.
PlatoForms6

Submit Form

ActionIn the docs only

Submit Form sends data from your scenario into a PlatoForms form, so a contact from a CRM or a row from a spreadsheet becomes a submission without anyone typing it.

When to use it
a new client appears in another app and their details belong in your PlatoForms form.
Watch out
run Get Form Fields beforehand so each value lands in the right field, and check the first submission after Run once.
Need help

Need help automating PlatoForms with Make?

A person reads every message.

FAQ

PlatoForms and Make: common questions

01Is the PlatoForms Make integration free?
Yes, PlatoForms is a standard app in Make, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution 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 remove the cap on active scenarios. Your PlatoForms subscription is separate: check its own pricing page.
02What does it take to connect PlatoForms to Make?
An active PlatoForms account, plus either a non-expiring token or an OAuth2 application created in PlatoForms. For OAuth2, open your profile photo, go to API Webhooks, click Add Application, enter a name and the callback URI given by Make, then save and copy the Client ID and Client secret. In Make, add a PlatoForms module, click Create a connection and paste those credentials. The connection is then reused by every PlatoForms module you add.
03Does PlatoForms start Make scenarios in real time?
No. PlatoForms has no trigger module in Make, neither scheduled nor instant, so it cannot start a scenario the moment something happens. You start the scenario another way: with the schedule on the first module, every 15 minutes by default and as short as 1 minute on a paid plan, or with a trigger from another app, such as a CRM or a spreadsheet, followed by the PlatoForms modules. A scenario can also start when an app calls Make, but the documentation does not say PlatoForms does.
04What if a PlatoForms module is missing in Make?
It depends on what you need. The app lists a module called Make API Call, and its name suggests a request of your own to PlatoForms; the Make documentation describes nothing about it, so see it as a lead to test with Run once, not a promise. If that route stays blocked, another app from the same category may cover the need, or the team can look at your case with you. Keep in mind that each extra request still counts as one operation.
05Make or n8n for PlatoForms?
It depends on the tool your team already uses. In Make, PlatoForms comes with 6 action modules and no trigger, available from the Free plan, which suits a scenario started by a schedule or by another app. Many apps also have an n8n node, so check whether PlatoForms does before comparing the two. Pick the one whose modules match your use case, not a ranking. Both routes can run the same use case; the fit matters more than the tool.
Same platform

Other docs you might need on this stack.

Browse all integrations