Resources · Make integration

Pronnel Make integrationAutomate Pronnel with Make.

Can Make keep your Pronnel board in step with the rest of your tools? The Pronnel Make integration gives you 6 modules: 3 scheduled triggers and 3 actions. This guide links your account, walks you through a first scenario and explains when to pick each module.

Try the Pronnel integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Pronnel Make integration let you automate?

The Pronnel Make integration links your Pronnel account to Make so that a scenario, the automation you build as a chain of modules, can spot new items, fresh comments and changes in Pronnel, then create or update items for you. No code is involved: you pick modules, map data and switch the scenario on.

Capture requests from elsewhere. A sales team collecting leads through a web form can send each submission to Create an Item, so every lead lands in Pronnel without anyone retyping it.

Pass news to the team. Watch Added Comment picks up new comments, and the next module can forward them to a chat or an inbox your colleagues already read. Watch Created Item works the same way for fresh items, for instance to log them in a spreadsheet.

Keep two tools aligned. Watch Updated Item notices edited items, while Update an Item writes changes coming from another system back into Pronnel. When a need falls outside these modules, Make an API Call reaches the rest of the Pronnel API with the same connection.

Know the limits before you start. Make's own documentation for Pronnel is marked as limited, with no official description of any module, so test each step with real data. If you are weighing Make against another tool, read n8n vs Make; to budget operations, see Make pricing; to learn the editor properly, Make training is a good next step.

Connect

How do you connect Pronnel to Make?

  1. 01

    Add a Pronnel module

    Open a scenario, click the + and search for Pronnel. Pick any of its modules, then click Create a connection. A connection is your Pronnel account linked to Make once and reused by every Pronnel module afterward.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it helps when several people or several Pronnel accounts share the same Make workspace. Something like the team or the account owner is enough to tell them apart later.

  3. 03

    Authorize and save

    Depending on what Pronnel asks for, either approve access on the Pronnel page that opens, or paste the key Pronnel gives you into the field Make shows. Then click Save and the module is ready to configure.

First scenario

Your first scenario: turn incoming requests into Pronnel items

GoalWhen a new request arrives in another app, Make creates a matching item in Pronnel.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Here that first module comes from the app where requests arrive, such as your form tool.

  2. 02

    Add Create an Item

    Click the + on the right of that first module, search for Pronnel and choose Create an Item. Click Create a connection if your Pronnel account is not linked yet.

  3. 03

    Map the request data

    Fill the fields of Create an Item with data from the first module. Once the connection exists, Make lists what it can read in Pronnel, so you choose instead of typing names by hand.

  4. 04

    Test with Run once

    Send yourself a test request, then click Run once. Make runs the scenario one time and shows the bundles, the items passed from module to module, that each step received. Check the new item in Pronnel.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. From now on each new request becomes a Pronnel item without you touching it.

Triggers

Pronnel triggers: what starts a scenario

3 modules start a scenario when something happens in Pronnel. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Pronnel as soon as it happens.

Pronnel1Watch Added Comment

Watch Added Comment

triggerIn the docs only

Hands your scenario every new comment posted in Pronnel, so the discussion around an item can reach people who never open the board. Each comment arrives as its own bundle for the modules that follow.

How it fires
scheduled, Make checks Pronnel on the scenario's schedule, so a comment shows up at the next check rather than the moment it is written.
When to use it
a client leaves feedback on a deliverable and the account manager should hear about it in the chat tool the team already uses.
Watch out
Make's documentation lists this module by name only; its scheduled type is inferred from that name, so run it once before relying on it.
Pronnel2Watch Created Item

Watch Created Item

triggerIn the docs only

Gives you a starting point each time someone adds an item in Pronnel, which is the natural hook for anything that should happen right after creation, like a welcome message, a spreadsheet row or a task in another tool.

How it fires
scheduled, Make checks Pronnel on the scenario's schedule and picks up the items created since the previous check.
When to use it
a new deal is entered in Pronnel and finance needs a copy in its own tracking sheet.
Watch out
the documentation gives no description of this trigger, so confirm with Run once which items it returns.
Pronnel3Watch Updated Item

Watch Updated Item

triggerIn the docs only

Reacts to changes rather than creations: when an existing item is edited in Pronnel, the scenario receives it at the next check and can pass the new state along. This is the one to pick when the edit, not the birth of the item, is what matters.

How it fires
scheduled, Make checks Pronnel on the scenario's schedule and collects the items modified in between.
When to use it
a deal moves forward in Pronnel and the invoicing tool should reflect it.
Watch out
avoid pairing it with Update an Item on the same items, or each update could start the scenario again.
Modules

Pronnel actions in Make

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

Pronnel1

Create an Item

ActionIn the docs only

Adds a new item to Pronnel from data that arrives in the scenario, so a lead, a request or an order recorded elsewhere appears on your board without manual entry.

When to use it
a form, an email or a shop sends something that deserves its own entry in Pronnel.
Watch out
placed after Watch Created Item, it would feed the trigger with its own items, so start from another app instead.
Pronnel2

Make an API Call

ActionIn the docs only

Opens the rest of the Pronnel API to your scenario, using the connection you already created, for whatever the listed modules do not cover. It is the fallback when no ready module fits.

When to use it
you need an operation of Pronnel that has no dedicated module in Make.
Watch out
you write the request yourself, so check the response with Run once before adding the next module.
Pronnel3

Update an Item

ActionIn the docs only

Changes an item that already exists in Pronnel, which keeps it accurate when the real information lives in another system. Pick it over Create an Item whenever the record is already on the board.

When to use it
a payment is confirmed in your billing tool and the matching Pronnel item should say so.
Watch out
the module has to know which item to change, so carry that reference from an earlier module.
Need help

Need help automating Pronnel with Make?

A person reads every message.

FAQ

Pronnel and Make: frequent questions

01Is the Pronnel Make integration free?
Yes, Pronnel is a standard app in Make, so it works from the Free plan onward. That plan allows 2 active scenarios, a minimum of 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 and Enterprise) bring the interval down to 1 minute, lift the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one execution of one module on one bundle. Any cost on the Pronnel side is outside the scope of this page.
02What do you need to connect Pronnel to Make?
A Pronnel account and a Make account are enough to start. Make's documentation lists no specific prerequisite for Pronnel and gives no dedicated connection steps, so the generic path applies: add a Pronnel module, click Create a connection, optionally name it, then either approve access on the Pronnel page or paste the key Pronnel gives you, and click Save. The connection is then reused by every Pronnel module in your scenarios, so you only do this once per account.
03Do Pronnel triggers in Make fire instantly?
No. All three Pronnel triggers, Watch Added Comment, Watch Created Item and Watch Updated Item, are treated as scheduled triggers: Make checks Pronnel on the scenario's schedule instead of being called by Pronnel. A new scenario checks every 15 minutes by default. On the Free plan 15 minutes is also the shortest interval, while paid plans can go down to 1 minute. Note that these types are inferred from the module names, since the documentation does not describe the modules.
04What if a Pronnel module you need is missing in Make?
It depends on the gap, but Make an API Call is the intended route. This module lets a scenario call any endpoint of the Pronnel API with the connection you already have, so an operation without a dedicated module is still reachable. You do need to write the request yourself. Keep in mind that Make's documentation for Pronnel is marked as limited, with no description of the modules, so test every step with Run once before switching a scenario on.
05Should you use Make or n8n for Pronnel?
It depends on your criteria, not on a winner. On the Make side, the facts are clear: 6 Pronnel modules, a guided editor, a Free plan to try it and Make an API Call for the rest. Many apps also have an n8n node, so check whether one exists for Pronnel and whether it covers the items and comments you need. Compare the two tools on the modules available for your case, the way each counts usage and the tool your team already knows, then pick the one that fits your process.
Same platform

Other docs you might need on this stack.

Browse all integrations