Resources · Make integration

Planfix Make integrationAutomate Planfix with Make.

What can the Planfix Make integration take off your plate? Make offers 26 Planfix modules: 1 trigger, 19 actions and 6 searches. This page is for ops leads who already run Planfix, and it walks you from the connection to a first working scenario.

Try the Planfix integration on MakeSee the 26 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Planfix Make integration do?

The Planfix Make integration links your Planfix account to Make so that tasks, contacts, records, actions and files move between Planfix and your other tools on their own. You build a scenario, which is the automation itself: a chain of modules, each one a single brick such as a trigger, an action or a search.

A form that becomes a task. A lead fills in a form in another app, Search Contacts checks whether that person is already in Planfix, then Create a Contact or Update a Contact keeps the card clean, and Create a Task hands the follow-up to the right person.

A follow-up that reacts to activity. Watch Actions picks up new actions in Planfix, Get a Task pulls the task they belong to, and the next module posts a summary wherever your team reads it.

Files that land in the right place. Download a File grabs an attachment from Planfix so another app can archive it, while Add a File pushes a document from elsewhere into Planfix.

What the modules do not cover can still be reached through Make an API Call, with the same connection. The Planfix documentation page on Make is AI-generated and flags that it may contain mistakes, so test each module with Run once before trusting it. If you are still weighing tools, read our Make review and the n8n vs Make comparison; to learn the editor step by step, the Make training starts from zero.

Connect

How do you connect Planfix to Make?

  1. 01

    Grab your API key and token

    In Planfix, open Account management in the main menu, then Access to API. Copy the API key and the API token shown on the screen and keep them at hand. You need a paid or premium Planfix account for this.

  2. 02

    Add a Planfix module

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

  3. 03

    Paste the credentials

    Give it a clear label in Connection name if you like, then paste the key and token you copied, or follow the instructions Make shows on screen. Save, and the module can now read your Planfix data.

First scenario

Your first scenario with Planfix and Make

GoalWhen a new action shows up in Planfix, Make creates a follow-up task for it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to place the first module. The empty canvas is where the chain of modules will sit.

  2. 02

    Place the trigger

    Search for Planfix, pick Watch Actions and pick the connection you made earlier. Make then lists what it can read from your account, so you fill the fields from menus.

  3. 03

    Add the task

    Click the + on the right of the trigger, choose Create a Task and map data from the action into the fields of the task. Each item passed along is called a bundle.

  4. 04

    Test with Run once

    Click Run once, then add an action in Planfix. Read the bundles each module received and confirm the task looks right in Planfix.

  5. 05

    Schedule and switch on

    Open the clock on the first module: a new scenario checks every 15 minutes by default. Keep it or adjust it, then switch the scenario on so it runs without you.

Triggers

What starts a Planfix scenario

1 module starts a scenario when something happens in Planfix. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Planfix as soon as it happens.

Planfix1Watch Actions

Watch Actions

triggerIn the docs only

Watch Actions is the only way a Planfix scenario starts on its own: it picks up actions in your account and hands each one to the next module as a bundle, so the rest of the scenario can react to what your team logs.

How it fires
scheduled, Make checks the app on the scenario's schedule, not the moment the action is saved.
When to use it
you want a task, a message or a record update to follow each new action without anyone copying it by hand.
Watch out
the documentation gives no description of this module, so run it once and read its bundles before building the rest of the chain.
Modules

Everything Make can do in Planfix

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

Planfix1

Add a File

ActionIn the docs only

Add a File puts a document into Planfix from another step of your scenario, so a contract signed elsewhere or a report built by another app ends up where your team already works.

When to use it
a file arrives in email or cloud storage and belongs next to a Planfix task or contact.
Watch out
on the Make Free plan, files are capped at 5 MB, so large scans may need a paid plan.
Planfix2

Create a Contact

ActionIn the docs only

Create a Contact adds a new person or company card to Planfix from data gathered elsewhere, which saves typing names and emails twice.

When to use it
a lead signs up through a form, a shop or a booking tool and should exist in Planfix straight away.
Watch out
nothing stops a duplicate, so place Search Contacts in front and create only when the search comes back empty.
Planfix3

Create a Record

ActionIn the docs only

Create a Record writes a new entry into Planfix from your scenario, handy when the data you collect is not a task or a contact but still needs a home in your account.

When to use it
another tool produces structured data, such as an order line or a request, that your team tracks as records in Planfix.
Watch out
the documentation says nothing about which records are available, so check the lists Make offers once connected.
Planfix4

Create a Task

ActionIn the docs only

Create a Task opens a new task in Planfix with the details mapped from earlier modules, so work that starts in another app gets an owner and a place to be tracked.

When to use it
a support ticket, a signed quote or a form reply should turn into something a colleague has to act on.
Watch out
each run creates one task per bundle, so a search placed before it can multiply tasks if it returns several items.
Planfix5

Create an Action

ActionIn the docs only

Create an Action logs a new action in Planfix from your scenario, which keeps the history of a piece of work complete even when the event happened in another tool.

When to use it
a call ends in your phone system or a reply arrives by email and the team should see it in Planfix.
Watch out
if the same scenario starts with Watch Actions, the new action can trigger it again, so filter out what the scenario itself wrote.
Planfix6

Delete a Contact

ActionIn the docs only

Delete a Contact removes a contact card from Planfix when the same person disappears from your source of truth, so your base stays tidy without manual cleanup.

When to use it
someone asks to be forgotten, or a CRM elsewhere marks the record as removed.
Watch out
a deletion cannot be undone from Make, so test it on a dummy contact with Run once and add a filter before it goes live.
Planfix7

Delete a File

ActionIn the docs only

Delete a File takes a document out of Planfix, which helps when a file was only a temporary copy or has been replaced by a newer version.

When to use it
after Download a File has archived an attachment in another app and the Planfix copy is no longer needed.
Watch out
make sure the archive step succeeded first, because once gone the file cannot be brought back from Make.
Planfix8

Delete an Action

ActionIn the docs only

Delete an Action removes an action from Planfix, useful for clearing entries that a scenario logged by mistake or that were created as tests.

When to use it
you have been building with Run once and want to erase the test actions left in a real task.
Watch out
this is permanent, so pass the exact action from Get an Action or Search Actions rather than guessing which one to target.
Planfix9

Download a File

ActionIn the docs only

Download a File pulls the content of a Planfix file into the scenario, so the next module can store it, attach it to an email or send it to a signature tool.

When to use it
an attachment in Planfix has to reach a drive, an accounting app or a client.
Watch out
each download counts toward your data transfer, and the Free plan allows 512 MB, so heavy files add up fast.
Planfix10

Get a Contact

ActionIn the docs only

Get a Contact fetches one contact card from Planfix when you already know which one you need, giving later modules its details to reuse.

When to use it
a task or an action points to a person, and you want their details for an email or an invoice.
Watch out
it needs a precise reference; when all you have is a name or an email, start with Search Contacts instead.
Planfix11

Get a File

ActionIn the docs only

Get a File reads the information about one file stored in Planfix, so the scenario can check what it is dealing with before acting on it.

When to use it
you want to look at a file first, then decide whether to download, replace or delete it.
Watch out
reading the details is not the same as getting the content; to move the file itself, follow up with Download a File.
Planfix12

Get a Record

ActionIn the docs only

Get a Record retrieves a single Planfix record you can point to, and hands its data to the modules that follow so they can build on it.

When to use it
an earlier step gives you the reference of a record and you need its content for a quote, a message or a report.
Watch out
to find records by what they contain rather than by reference, Search Records is the right module.
Planfix13

Get a Task

ActionIn the docs only

Get a Task loads one Planfix task in full, so a scenario that starts from an action or a message can see the task behind it.

When to use it
Watch Actions returns a new action and you need the task it relates to before notifying someone.
Watch out
each call is one operation, meaning one run of one module, and those are what Make counts on your plan.
Planfix14

Get an Action

ActionIn the docs only

Get an Action opens one specific action in Planfix and exposes its content to the rest of the scenario, ready to be copied, summarized or passed on.

When to use it
you hold the reference of an action and want its full text for a message or a report.
Watch out
when several actions could match, you need Search Actions first, because this module works on one action only.
Planfix15

List File History

SearchIn the docs only

List File History returns the past versions of a Planfix file, which lets a scenario show who changed a document or keep an older copy somewhere else.

When to use it
a contract or a spec goes through several versions and you want a trace outside Planfix.
Watch out
it is a search, so it can return zero, one or several bundles, and every following module runs once per version.
Planfix16

Make an API Call

ActionIn the docs only

Make an API Call reaches any endpoint of the Planfix API from your scenario, reusing the connection you already made, for the cases none of the other modules cover.

When to use it
you need a Planfix feature that has no dedicated module on this page.
Watch out
you write the request yourself, so keep the Planfix API documentation open and test with Run once before switching the scenario on.
Planfix17

Search Actions

SearchIn the docs only

Search Actions finds the Planfix actions that match your criteria and hands them one by one to the next module, so you can act on a whole set at once.

When to use it
you want to gather the actions on a task to build a recap or to spot what is still open.
Watch out
an empty result stops the chain for that run, so a filter or a fallback route keeps the scenario from silently doing nothing.
Planfix18

Search Contacts

SearchIn the docs only

Search Contacts looks up people or companies in Planfix and tells you whether they are already there, which is the safest first step before writing anything.

When to use it
a new lead arrives and you want to update the existing card instead of creating a second one.
Watch out
several matches mean several bundles, so the next module would run for each unless you keep only the first result.
Planfix19

Search Handbooks

SearchIn the docs only

Search Handbooks looks through the handbooks in your Planfix account and returns what it finds, so a scenario can use reference data your team already maintains there.

When to use it
a value such as a product or a category has to be matched against a list kept in Planfix.
Watch out
the documentation does not describe the results, so read the bundles returned by Run once before mapping anything from them.
Planfix20

Search Records

SearchIn the docs only

Search Records finds Planfix records by what they contain and passes each match along, which lets a scenario work on many records without knowing their references.

When to use it
you need every record linked to a client or a status to feed a report or a spreadsheet.
Watch out
each result is a separate bundle, so follow it with an aggregator in Make if you want a single summary instead of one message per record.
Planfix21

Search Tasks

SearchIn the docs only

Search Tasks brings back the Planfix tasks matching your criteria, one bundle each, so a scenario can chase, update or report on them in a batch.

When to use it
you want to list the tasks tied to a project to post a digest in a team chat.
Watch out
a broad search can return many tasks and each one costs operations in the modules after it, so narrow the criteria first.
Planfix22

Update a Contact

ActionIn the docs only

Update a Contact changes an existing Planfix contact with fresh data from another tool, so phone numbers, emails or company names stay current without retyping.

When to use it
a customer edits their profile in your shop or billing app and Planfix should follow.
Watch out
fields you map empty may overwrite good data, so map only what actually changed and test on one contact first.
Planfix23

Update a Record

ActionIn the docs only

Update a Record rewrites parts of a Planfix record from your scenario, keeping it aligned with the tool where the information really changes.

When to use it
an order moves forward in another system and the matching record in Planfix should show the new state.
Watch out
you need the reference of the record, so place Search Records or Get a Record before it when the scenario does not already carry it.
Planfix24

Update a Task

ActionIn the docs only

Update a Task edits a task that already exists in Planfix, which lets another app move work forward without anyone opening Planfix to do it.

When to use it
a payment clears, a document gets signed, and the related task should change to reflect it.
Watch out
if Watch Actions starts the same scenario, check that the update does not create an action that restarts the loop.
Planfix25

Update an Action

ActionIn the docs only

Update an Action corrects or completes an action already logged in Planfix, useful when details arrive after the first entry was written.

When to use it
a scenario logged a call with Create an Action and later receives the recording link or the outcome.
Watch out
keep the reference returned by Create an Action in the same run, otherwise you will need Search Actions to find it again.
Need help

Need help automating Planfix with Make?

A person reads every message.

FAQ

Questions about the Planfix Make integration

01Is the Planfix Make integration free?
Yes on the Make side: Planfix is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution and files up to 5 MB. Paid plans such as Core, Pro, Teams and Enterprise lower the interval to 1 minute and remove the cap on active scenarios. On the Planfix side, the documentation requires a paid or premium account to connect, so check your own subscription.
02What do you need to connect Planfix to Make?
A paid or premium Planfix account and two values from it. In Planfix, go to Account management, then Access to API, and copy both the API key and the API token. In Make, add a Planfix module, click Create a connection, name it if you wish and paste those values. That connection is then reused by all 26 Planfix modules, so you only do this once per account. If the connection fails, the key and token are the first thing to check.
03Does the Planfix Make integration react in real time?
No. Watch Actions, the only Planfix trigger, is a scheduled trigger: Make checks Planfix on the scenario's schedule, every 15 minutes by default for a new scenario. On the Free plan, 15 minutes is also the shortest interval, while paid plans go down to 1 minute. The clock badge on the module in the editor shows this type, and it is worth confirming there since the documentation does not describe the module.
04What if the Planfix module you need is missing?
Use Make an API Call. It sends a request to any endpoint of the Planfix API with the connection you already have, so you can reach what the 19 actions and 6 searches leave out. Keep in mind that the Planfix documentation page on Make is AI-generated and warns it may contain mistakes, so test every module with Run once and check with Planfix directly when something looks off. When a result looks wrong, check the bundles each module received.
05Should you use Make or n8n for Planfix?
It depends on what you compare. On Make, Planfix comes with 26 modules and one scheduled trigger, so most task, contact, record and file work needs no code, and Make an API Call covers the rest. The same app often has an n8n node too. Look at which modules each tool offers for the jobs you plan, and at which editor your team already knows, rather than at a general ranking.
Same platform

Other docs you might need on this stack.

Browse all integrations