Resources · Make integration

PLANTA pulse Make integrationAutomate PLANTA pulse with Make.

Can Make keep your PLANTA pulse boards in step with the rest of your tools? The PLANTA pulse Make integration brings 76 modules: 1 trigger, 53 actions and 22 searches. This guide shows project leads who know PLANTA pulse how to link the account, build a first scenario, and pick the right module.

Try the PLANTA pulse integration on MakeSee the 76 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the PLANTA pulse Make integration do?

The PLANTA pulse Make integration links your PLANTA pulse account to Make, a no-code tool where you chain apps into a scenario (the automation you build). Each brick of that chain is a module: here, one trigger that watches activity, plus actions and searches on projects, boards, lists, cards, users and groups.

Cards that appear on their own. A request arrives from a form or another app, and Create a Card places it on the right board, then Add a Card Member hands it to someone. Nobody retypes the ticket.

A project skeleton in one pass. Create a Project, Create a Board, Create a List and Create a Swimlane can lay out the same structure every time a new engagement starts, so each team works from an identical frame.

A readable feed of what changed. Watch All Activities picks up activity in PLANTA pulse on the scenario's schedule, and Get a Card fetches the details you then send to another tool.

Know the limits before you start. PLANTA pulse has no instant trigger in Make, so nothing reacts the very second a card moves. The Make documentation page for this app also warns that it was generated with AI from the vendor's documentation, so check important details with PLANTA pulse directly. For a wider view of the platform, read the Make review; if you also consider n8n, the n8n vs Make comparison sets out the criteria, and the Make pricing page covers plans.

Connect

How do you connect PLANTA pulse to Make?

  1. 01

    Create an API user in PLANTA pulse

    In PLANTA pulse, open Administration, then Users, and add a new user. Pick API User in the User Type list, type a username and click Create.

  2. 02

    Generate and copy the token

    In the API User column of that new user, click Create Token, then Create. Copy the key PLANTA pulse shows as the token: it is the bearer token Make asks for.

  3. 03

    Add the connection in Make

    Add any PLANTA pulse module to your scenario and click Create a connection. A connection is your account linked to Make once, then reused by every module of the app. Name it if you like and paste the token.

First scenario

Build your first scenario with PLANTA pulse

GoalWhen a request lands in another app, Make creates a card in PLANTA pulse and assigns it to a teammate.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app where requests arrive, such as your form tool, and choose its module that fires on a new entry.

  2. 02

    Add Create a Card

    Click the + to the right of that first module, search PLANTA pulse and pick Create a Card. Click Create a connection and paste your API token.

  3. 03

    Map the request into the card

    Fill the module fields. Once the connection exists, Make lists what it can read in PLANTA pulse, so you choose the board from a list and map the title from the request of the first module.

  4. 04

    Assign the card

    Add Add a Card Member after it. Map the card that the previous module just created, then pick the teammate who should own the request.

  5. 05

    Test with Run once

    Click Run once, then send one test request. Open each module to read the bundle it received (one item passed along, here one request, then one card) and check the card on your board.

  6. 06

    Schedule and switch on

    Set the schedule on the first module: every 15 minutes by default. Switch the scenario on. Each module run counts as an operation, the unit Make counts on your plan.

Triggers

What starts a PLANTA pulse scenario

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

PLANTA pulse1Watch All Activities

Watch All Activities

triggerIn the docs only

Watch All Activities turns what happens in your PLANTA pulse workspace into bundles, one per activity, that the rest of your scenario can act on. It is the only trigger this app offers in Make, so any flow that starts from PLANTA pulse itself begins here.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, so activity reaches your scenario at the next check, not the moment it happens.
When to use it
to feed a digest or another tool with what your team changed, then add a filter so only the activity you care about goes further.
Watch out
avoid writing back into PLANTA pulse from this flow without a filter, or your own changes come back as new activity.
Modules

What PLANTA pulse can do in a scenario

PLANTA pulse gives you 75 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

PLANTA pulse1

Add a Board Member

ActionIn the docs only

Your colleague gets access to a board without anyone opening the board settings by hand. The scenario seats the right person as soon as the board is ready.

When to use it
right after Create a Board, to seat the project lead on the new board in the same run.
Watch out
if the person may not exist yet in PLANTA pulse, check with Get a User or List All Users earlier in the flow.
PLANTA pulse2

Add a Card Label

ActionIn the docs only

Tagging a card with a label makes it stand out on the board, so the team spots its category or urgency at a glance, without a human sorting the column.

When to use it
when the incoming request already says what it is, for example a bug report versus a change request, and the label should follow.
Watch out
the label has to exist on the board; List Board Labels shows which ones you can pick.
PLANTA pulse3

Add a Card Member

ActionIn the docs only

Someone ends up in charge of the card the moment it is created, which is the difference between a ticket that waits and a ticket that moves.

When to use it
after Create a Card, when your routing rule already knows who handles this kind of request.
Watch out
map the card from the module that created it, not a card chosen once in the list, or every run assigns the same card.
PLANTA pulse4

Add a Group Member

ActionIn the docs only

New hires land in the right PLANTA pulse group without a separate admin task, so they inherit what the group already sees from their first login.

When to use it
when your HR or onboarding tool records a new team member, right after Create a User in the same scenario.
Watch out
List Groups helps you pick the group from a list instead of typing its identifier by hand.
PLANTA pulse5

Create a Board

ActionIn the docs only

A fresh board appears in PLANTA pulse from a signal elsewhere, ready for lists and cards, so a project never starts on an empty screen someone forgot to set up.

When to use it
when a deal is marked as won in your CRM and delivery needs its own board.
Watch out
run Create a Board once per project; if the scenario runs twice on the same deal, you end up with twin boards, so filter on a status first.
PLANTA pulse6

Create a Card

ActionIn the docs only

This is the module that turns an outside request into work on your board: an email, a form entry or a support ticket becomes a card the team can pick up.

When to use it
as the first PLANTA pulse step behind any intake channel, as in the first scenario above.
Watch out
keep the card title mapped from the request so each card stays recognizable on a busy board.
PLANTA pulse7

Create a Card Comment

ActionIn the docs only

Context from another tool lands right on the card as a comment, so whoever works on it reads the latest update without switching apps.

When to use it
when a customer replies by email or a deployment finishes and the card owner should see it in PLANTA pulse.
Watch out
in a scenario started by Watch All Activities, a new comment is itself activity, so filter to avoid a loop.
PLANTA pulse8

Create a Checklist

ActionIn the docs only

A card gets its to-do list attached automatically, so a repeatable task arrives with its steps already spelled out instead of relying on memory.

When to use it
behind Create a Card for standard requests such as onboarding a client, where the steps never change.
Watch out
map the card created earlier in the run; a checklist needs a card to live on, and Make will not guess which one.
PLANTA pulse9

Create a Custom Field

ActionIn the docs only

Your boards gain a new field to track something PLANTA pulse does not cover out of the box, and the scenario adds it the same way everywhere.

When to use it
when you roll out a new tracking rule across boards and want every board to carry the field under the same name.
Watch out
check List Custom Fields by Board first, so a second run does not create a duplicate field.
PLANTA pulse10

Create a Group

ActionIn the docs only

A new group gives a team or department its own place in PLANTA pulse, and the scenario creates it as soon as the team exists in your other systems.

When to use it
when a new department or client team is opened in your directory and should mirror in PLANTA pulse.
Watch out
follow it with Add a Group Member, otherwise the group sits empty until someone fills it by hand.
PLANTA pulse11

Create a List

ActionIn the docs only

Columns on a board show up without manual setup, so each board carries the stages your process expects, in the order you decided.

When to use it
right after Create a Board, once per stage, to build the same workflow columns on every new project.
Watch out
if the column order matters to your team, run a first test with Run once and check the board before you duplicate the pattern.
PLANTA pulse12

Create a Project

ActionIn the docs only

Projects are born in PLANTA pulse from the tool where they are decided, so the project record exists before the first meeting and nobody retypes its name.

When to use it
when a quote is signed or a request is approved in another app, as the opening move of a project setup scenario.
Watch out
filter on the approval status so a draft or a declined request never becomes a project.
PLANTA pulse13

Create a Swimlane

ActionIn the docs only

Horizontal lanes split a board by team, client or priority, and the scenario draws them the same way on every board it builds.

When to use it
when your boards are shared by several squads and each one needs its own lane from day one.
Watch out
List Swimlanes by Board tells you what already exists, which spares you duplicate lanes on a second run.
PLANTA pulse14

Create a User

ActionIn the docs only

An account for a new colleague appears in PLANTA pulse straight from your onboarding flow, so access no longer waits for an admin ticket.

When to use it
when your HR tool records an arrival, followed by Add a Group Member or Add a Board Member.
Watch out
run List All Users or Get a User first if the person might already have an account, to avoid a duplicate profile.
PLANTA pulse15

Create a Webhook Config

ActionIn the docs only

This module registers a webhook configuration in PLANTA pulse from inside a scenario, which lets you manage that setup the same way as the rest of your automation.

When to use it
when you script the setup of a PLANTA pulse workspace and want its webhook settings created in the same pass.
Watch out
PLANTA pulse has no instant trigger in Make, so Watch All Activities stays a scheduled trigger whatever this module sets up.
PLANTA pulse16

Create a Workload

ActionIn the docs only

Planned effort gets recorded on a board without a manual entry, so capacity planning in PLANTA pulse reflects what was decided elsewhere.

When to use it
when a staffing decision is made in another tool and the matching workload should appear on the project board.
Watch out
List Workloads by Board shows what is already there; check it before adding, so the same effort is not counted twice.
PLANTA pulse17

Delete a Board

ActionIn the docs only

A board disappears from PLANTA pulse as part of a cleanup flow, which keeps closed projects from cluttering everyone's view.

When to use it
when a project is marked as cancelled in your source tool and its board has no reason to stay.
Watch out
treat this as permanent. Put a filter before it and test with Run once on a throwaway board before switching the scenario on.
PLANTA pulse18

Delete a Board Label

ActionIn the docs only

Labels you no longer use leave the board, so the picker stays short and cards are tagged with categories that still mean something.

When to use it
when you retire a category across boards and want the cleanup done in one scenario rather than board by board.
Watch out
expect cards tagged with it to lose that tag; List Board Labels helps you target the exact one before deleting.
PLANTA pulse19

Delete a Board Member

ActionIn the docs only

Access to a board is withdrawn the moment someone leaves the project, so the member list mirrors reality without a manual review.

When to use it
when a person is taken off a project in your staffing tool, or their contract ends.
Watch out
this removes one person from one board; to take someone out of PLANTA pulse entirely, Remove a User from the System is the module to look at.
PLANTA pulse20

Delete a Card

ActionIn the docs only

Cards that should never have existed, such as spam requests or test entries, vanish from the board without anyone hunting for them.

When to use it
behind a filter that recognizes junk requests, or to clean up the cards left by your own test runs.
Watch out
treat it as final. When in doubt, Move a Card to an archive list keeps the history available.
PLANTA pulse21

Delete a Card Comment

ActionIn the docs only

A comment that went to the wrong card, or was posted twice, gets removed so the card thread stays clean for whoever reads it next.

When to use it
to undo comments that one of your own scenarios posted by mistake, found with List Card Comments.
Watch out
target the comment by its identifier from the list, never by position, or the wrong message may go.
PLANTA pulse22

Delete a Checklist

ActionIn the docs only

Checklists that no longer apply come off the card, so the team is not asked to tick steps from an outdated process.

When to use it
when a request changes type and its standard checklist has to be swapped for another one.
Watch out
assume the progress on it is lost too; use List Card Checklists to pick the right checklist when a card carries several.
PLANTA pulse23

Delete a Custom Field

ActionIn the docs only

Fields nobody fills any more disappear from a board, which keeps card forms short and the data people enter meaningful.

When to use it
when you retire a tracking rule and want the field gone from every board in one scenario.
Watch out
assume the values people entered in it are lost as well, so confirm nobody still reports on that field.
PLANTA pulse24

Delete a Group

ActionIn the docs only

Groups for teams that no longer exist leave PLANTA pulse, so the group list keeps matching your actual organization.

When to use it
when a department or a client team is closed in your directory and the mirror group should follow.
Watch out
check List Group Members first; anyone still inside could lose what the group gave them, so move them first.
PLANTA pulse25

Delete a Group Member

ActionIn the docs only

Someone leaves a group without leaving the company, and the access that came with the group ends at the same time.

When to use it
when a colleague changes team in your HR tool and should stop seeing the old team's boards.
Watch out
follow it with Add a Group Member for the new team in the same scenario, so the person is never left without access.
PLANTA pulse26

Delete a List

ActionIn the docs only

A column that no longer fits your process is removed from the board, keeping the view limited to the stages your team really uses.

When to use it
when you redesign a workflow and roll the new column layout out across several boards.
Watch out
check List Cards by List first and move any remaining cards elsewhere with Move a Card before the column goes.
PLANTA pulse27

Delete a Project

ActionIn the docs only

A project record is removed from PLANTA pulse, the strongest cleanup this app offers in Make, reserved for projects that should leave no trace.

When to use it
when a project was created by mistake, for instance by a test run of your setup scenario.
Watch out
treat it as irreversible and keep it out of any scenario that runs unattended until Run once has proven the filter.
PLANTA pulse28

Delete a Swimlane

ActionIn the docs only

A lane that no longer matches a team or a client is taken off the board, so the layout keeps reflecting how work is really split.

When to use it
when a squad is merged into another or a client contract ends and its lane has become useless.
Watch out
List Swimlanes by Board helps you pick the exact lane, since several boards may reuse the same lane names.
PLANTA pulse29

Delete a User

ActionIn the docs only

A user record is deleted from PLANTA pulse when an account should not remain, which closes a door your offboarding checklist might forget.

When to use it
for test accounts or duplicates your own scenarios created, found with List All Users.
Watch out
Remove a User from the System is a separate module; compare both in PLANTA pulse before choosing which one fits your offboarding.
PLANTA pulse30

Delete a Webhook Config

ActionIn the docs only

Webhook configurations you no longer need are removed from PLANTA pulse, so nothing keeps sending data to an address that stopped listening.

When to use it
when you retire an integration and want its configuration gone, after checking with List Webhook Configs.
Watch out
pick the configuration by its identifier from the list; another tool may still rely on a similar one.
PLANTA pulse31

Get a Board

ActionIn the docs only

You receive the details of one board as a bundle, ready to map into later modules, when you already know which board you are after.

When to use it
after Watch All Activities, to turn a board reference into a readable name before you post an update elsewhere.
Watch out
it reads one board you point to; to browse or find a board, List All Boards is the better start.
PLANTA pulse32

Get a Card

ActionIn the docs only

The full card lands in your scenario, so a message, a report or a record in another tool can carry its details instead of a bare reference.

When to use it
right behind Watch All Activities, as in the hero example, to enrich an activity before sending it to your team.
Watch out
it needs the card's identifier; map it from the previous module rather than choosing one card once.
PLANTA pulse33

Get a Checklist

ActionIn the docs only

One checklist and its content come back into the scenario, useful when a step of your process depends on where that checklist stands.

When to use it
to check a card's checklist before moving the card to a done column with Move a Card.
Watch out
a card can carry several checklists; List Card Checklists shows which one you need before you read it.
PLANTA pulse34

Get a Custom Field by ID

ActionIn the docs only

You get the definition of a single custom field, handy when a later module must know how that field is set up before writing to it.

When to use it
ahead of Update Custom Fields On Card, when the scenario needs to confirm which field it is about to fill.
Watch out
it works from the field's identifier; List Custom Fields by Board is where you find it.
PLANTA pulse35

Get a List

ActionIn the docs only

A single board column comes back with its details, so the scenario can use its name in a message or confirm it before placing a card.

When to use it
when an activity points to a list and your team update should read like a sentence, not an identifier.
Watch out
to see every column of a board at once, List Lists by Board fits better.
PLANTA pulse36

Get a Project

ActionIn the docs only

One project's record arrives in the scenario, ready to feed a status report, an invoice line or a message to a client team.

When to use it
when another app holds the project reference and needs its name and details from PLANTA pulse.
Watch out
it returns one project you point to; List Projects is the module for browsing or finding one.
PLANTA pulse37

Get a Swimlane

ActionIn the docs only

You read one lane of a board and its details, so a notification can say which team or client a card belongs to.

When to use it
after Get a Card, when your boards are split by lanes and the lane decides who hears about the change.
Watch out
lanes live on a board, so List Swimlanes by Board helps you find the identifier first.
PLANTA pulse38

Get a User

ActionIn the docs only

A person's PLANTA pulse profile comes back into the scenario, which is how an activity by a user ID becomes a name your team recognizes.

When to use it
to check whether an account already exists before Create a User, or to address an alert to the right colleague.
Watch out
map the user from the previous module; picking one user once makes every run read the same profile.
PLANTA pulse39

List All Boards

SearchIn the docs only

Every board you can reach comes back, one bundle per board, which gives the scenario a map of your PLANTA pulse workspace to work through.

When to use it
for a cross-board cleanup or report, such as adding a new label or custom field everywhere.
Watch out
each board becomes a bundle, and the modules after it run once per board, which adds operations on your plan.
PLANTA pulse40

List All Users

SearchIn the docs only

The full user list lands in the scenario, one bundle per person, so you can compare PLANTA pulse accounts with your HR tool or directory.

When to use it
in an access review scenario, to spot accounts that no longer match anyone on the payroll.
Watch out
a search can return zero, one or many bundles; add a filter so only the people you care about continue.
PLANTA pulse41

List Board Groups by Project

SearchIn the docs only

The board groups under one PLANTA pulse project come back, so the scenario knows how that project is organized before it touches anything. Each group arrives as its own bundle, one item handed to the next module.

When to use it
a new project kicks off and a later module needs to place boards in the right group.
Watch out
a search can return zero groups, so plan the path for an empty project.
PLANTA pulse42

List Board Labels

SearchIn the docs only

The labels already defined on a board come back, which gives the scenario the exact label it needs instead of a guess typed by hand. The result is a set of bundles, one per label.

When to use it
right before Add a Card Label, when an incoming request should be tagged as urgent or blocked on that board.
Watch out
every label found runs the following modules once, and each run counts as an operation on your plan.
PLANTA pulse43

List Board Members

SearchIn the docs only

You find out who belongs to a board. Make returns each member as a separate bundle, which turns a team roster into something the scenario can loop over, filter or send elsewhere.

When to use it
a card needs an owner and you want to check that the person is already on the board before assigning them.
Watch out
on a large board, the modules placed after this one run for every member it finds.
PLANTA pulse44

List Boards by Project

SearchIn the docs only

Only the boards of a single project come back, not the whole workspace. The scenario then works on a narrow, predictable set, which keeps the following steps focused and cheaper in operations.

When to use it
a project manager wants a digest of every board in their project posted to a chat tool.
Watch out
List All Boards covers every project; pick this one when only one project matters.
PLANTA pulse45

List Card Checklists

SearchIn the docs only

The checklists attached to one card come back, so the scenario can see what is still open on a piece of work before acting on it. One bundle comes back per checklist.

When to use it
before moving a card to a done list, to confirm the acceptance steps really exist on it.
Watch out
a card without any checklist returns nothing; add a filter so the next module does not run on empty data.
PLANTA pulse46

List Card Comments

SearchIn the docs only

The discussion thread of a card enters the scenario. The scenario gets each comment as a bundle, ready to archive, summarize or forward to people who never open PLANTA pulse.

When to use it
a client report should include the latest exchanges on a deliverable, copied into a document or an email.
Watch out
a busy card can hold many comments, and each one triggers the modules that follow.
PLANTA pulse47

List Cards by Board

SearchIn the docs only

Every card on a board comes back in a single step, whatever list or swimlane it sits in. This is the widest view of the work on that board that the scenario can get.

When to use it
exporting a whole board to a spreadsheet so a steering committee can review progress outside the tool.
Watch out
List Cards by List is narrower; start there when only one column of the board matters.
PLANTA pulse48

List Cards by List

SearchIn the docs only

Only the cards sitting in one list of a board come back, such as a review column. The scenario receives just the work at that stage, not the whole board.

When to use it
a quality lead wants every card waiting for review sent to them as a single message.
Watch out
a list can be empty at the moment the scenario runs, and then nothing happens downstream; that is expected, not an error.
PLANTA pulse49

List Cards of a User

SearchIn the docs only

You see the cards assigned to one person, across boards. It answers the question every manager asks before a one-to-one: what is actually on this person's plate?

When to use it
someone announces leave and their open cards need to be reviewed or handed over.
Watch out
pair it with Remove a Card Member and Add a Card Member to reassign, and test with Run once before switching the scenario on.
PLANTA pulse50

List Custom Field Listbox Items

SearchIn the docs only

You get the choices offered by a dropdown custom field. With that list in hand, the scenario can match a value coming from a form or a CRM to an option that really exists in PLANTA pulse.

When to use it
before Update Custom Fields On Card, when a request type from another tool must land on the right option.
Watch out
a value with no matching option will not fit; route it to a fallback.
PLANTA pulse51

List Custom Fields by Board

SearchIn the docs only

You learn which custom fields a board uses. Handy when boards were set up by different teams and the scenario cannot assume they share the same fields.

When to use it
a template scenario runs on several boards and has to check that a budget or priority field is present before writing into it.
Watch out
the answer is per board, so a field found on one board may be missing on the next.
PLANTA pulse52

List Custom Fields by Type

SearchIn the docs only

Custom fields come back sorted by kind instead of by board. It gives the scenario a short list of the fields of one kind only, rather than every field on the account.

When to use it
an audit of the dropdown fields in use, before cleaning up duplicates with Delete a Custom Field.
Watch out
the field types are not documented, so open the module in Make and read the choices it offers.
PLANTA pulse53

List Group Members

SearchIn the docs only

The people inside one PLANTA pulse group come back. The scenario can then reach a whole team at once, since each member arrives as a bundle it can mention, email or copy.

When to use it
a new board is created for a department and every member of that group should be added to it.
Watch out
chaining it with Add a Board Member costs one operation per person.
PLANTA pulse54

List Groups

SearchIn the docs only

The full set of groups in your PLANTA pulse account comes back in one search. It is a quick way to mirror your team structure into another tool or to spot groups nobody uses anymore.

When to use it
syncing departments from PLANTA pulse into a directory or an HR spreadsheet.
Watch out
List Groups by Project gives a narrower answer when only one project matters.
PLANTA pulse55

List Groups by Project

SearchIn the docs only

Here the group search stays inside one project. The scenario learns which teams are involved in that project and nothing more, which keeps notifications targeted.

When to use it
a milestone is reached and only the groups working on that project should hear about it.
Watch out
this is a different thing from board groups; for those, use List Board Groups by Project.
PLANTA pulse56

List Lists by Board

SearchIn the docs only

The columns of a board, in other words its lists, come back. The scenario then knows where each stage lives and can send a card to the right one by its identifier rather than by a typed name.

When to use it
just before Move a Card, when the destination depends on a status coming from another app.
Watch out
renaming a list in PLANTA pulse can break filters that compare list names.
PLANTA pulse57

List Projects

SearchIn the docs only

The projects in your account come back. This is often the first search in a reporting scenario, because the boards, groups and cards all hang off a project.

When to use it
building a portfolio overview in a spreadsheet, one row per project.
Watch out
each project found runs the rest of the scenario once, so add a filter early if you only care about active work.
PLANTA pulse58

List Swimlanes by Board

SearchIn the docs only

The horizontal lanes of a board come back. Swimlanes often split work by team or client, so reading them lets the scenario sort cards along that second axis too.

When to use it
a new request must land in the lane of the client who sent it.
Watch out
a board may have no swimlanes at all; the search then comes back empty and the next module does not run.
PLANTA pulse59

List Webhook Configs

SearchIn the docs only

You see the webhook configurations already registered in PLANTA pulse. A webhook is an address the app calls when something happens; this list tells you which ones exist.

When to use it
checking for leftovers before Create a Webhook Config, so the same event is not sent twice.
Watch out
removing an entry with Delete a Webhook Config can stop another integration that still relies on it.
PLANTA pulse60

List Workloads by Board

SearchIn the docs only

The workload entries recorded on a board come back. It gives the scenario raw material for a capacity view: who carries what on that board, as bundles you can total or chart elsewhere.

When to use it
feeding a resource planning sheet that a delivery lead checks before accepting new work.
Watch out
totals are only as good as the data on the board; empty entries still count as bundles.
PLANTA pulse61

Make an API Call

ActionIn the docs only

You can call any endpoint of the PLANTA pulse API from a scenario, with the connection you already set up. It covers what the 76 ready-made modules do not.

When to use it
a request the listed modules cannot express, once you have found the endpoint in the PLANTA pulse API documentation.
Watch out
you write the request yourself, so test with Run once and read the response before relying on it.
PLANTA pulse62

Move a Card

ActionIn the docs only

A card moves to another place on the board, so its position follows what really happened elsewhere. No one has to drag it by hand after a deal is signed or a ticket is closed.

When to use it
a payment is confirmed in your billing tool and the matching delivery card should jump to the next stage.
Watch out
get the target from List Lists by Board first rather than typing it.
PLANTA pulse63

Remove a Card Label

ActionIn the docs only

A label comes off a card once it no longer applies. Labels stay honest this way, and filters built on them keep showing the right cards.

When to use it
a blocker is cleared in another system and the blocked tag on the card should disappear.
Watch out
this touches one card only; the label itself stays on the board, unlike Delete a Board Label, which removes it for everyone.
PLANTA pulse64

Remove a Card Member

ActionIn the docs only

A person is taken off a card. Their personal list of cards shrinks to what they really own, and the card stops notifying someone who has moved on.

When to use it
a contractor leaves a project and their cards are handed to someone else.
Watch out
the person remains a board member; to take them off the board, reach for Delete a Board Member instead.
PLANTA pulse65

Remove a User from the System

ActionIn the docs only

A person leaves PLANTA pulse entirely, as part of an offboarding flow started from your HR or identity tool. It closes access where it matters, without anyone opening the admin menu.

When to use it
an employee's departure is recorded in the HR system.
Watch out
Make lists this next to Delete a User without saying how the two differ; check with PLANTA pulse before automating it, since removal is hard to undo.
PLANTA pulse66

Update Custom Fields On Card

ActionIn the docs only

The custom fields of a card get filled in, so data born in another tool shows up where the team works. Budget, client reference or priority no longer need to be copied by hand.

When to use it
a quote is accepted in your CRM and the amount belongs on the delivery card.
Watch out
for dropdown fields, read the valid options with List Custom Field Listbox Items first.
PLANTA pulse67

Update a Board

ActionIn the docs only

An existing board gets updated from a scenario. Board details then stay in step with the project they belong to, without anyone remembering to edit them.

When to use it
a project is renamed in your CRM and its board should carry the new name.
Watch out
the module needs the board to exist; find it first with List Boards by Project or Get a Board.
PLANTA pulse68

Update a Board Member

ActionIn the docs only

The membership of someone already on a board changes, instead of removing and re-adding them. The person keeps their cards and history on that board while their membership changes.

When to use it
a team member takes over coordination of a board after a reorganization.
Watch out
the module names do not say what can be changed; open the module in Make and read the settings it offers.
PLANTA pulse69

Update a Card

ActionIn the docs only

An existing card picks up fresh information coming from elsewhere. The card stays the single place to look, even when the source of truth is a ticketing or sales tool.

When to use it
a customer changes the deadline in a support ticket and the delivery card should reflect it.
Watch out
to change its position rather than its content, use Move a Card.
PLANTA pulse70

Update a Checklist

ActionIn the docs only

A checklist already attached to a card gets updated. That helps when the steps of a job change after it started and the card should show the current version, not the original one.

When to use it
a compliance step is added to a process and existing onboarding cards must follow.
Watch out
spot the right checklist with List Card Checklists first; a card can carry several.
PLANTA pulse71

Update a List

ActionIn the docs only

A list on a board changes without rebuilding the board. The workflow columns stay aligned with how the team actually works, across boards that follow the same process.

When to use it
a stage is renamed in your process documentation and every board should show the new wording.
Watch out
other scenarios that filter on the old list name will stop matching.
PLANTA pulse72

Update a Project

ActionIn the docs only

The details of a PLANTA pulse project change from a scenario. The project record stays in line with the contract or the opportunity it was created for, with no double entry.

When to use it
an opportunity is renamed or its scope changes in your CRM.
Watch out
pick the project with List Projects or Get a Project first so the change hits the right one.
PLANTA pulse73

Update a Swimlane

ActionIn the docs only

An existing swimlane on a board gets reworked. When lanes stand for clients or teams, this keeps their labels right as accounts and teams evolve.

When to use it
a client changes its company name and the lane that holds its work should follow.
Watch out
read the lanes with List Swimlanes by Board before editing, so the scenario never edits a lane chosen at random.
PLANTA pulse74

Update a User

ActionIn the docs only

A PLANTA pulse user profile stays in step with your HR or identity system. Name or role changes then reach the tool without a ticket to an admin.

When to use it
someone changes department and their profile should reflect it the same day the HR record does.
Watch out
the profile fields are not documented; check in the module which ones Make exposes.
PLANTA pulse75

Update a Workload

ActionIn the docs only

A workload entry already on a board gets corrected, so capacity figures reflect the latest estimate rather than the first guess.

When to use it
an estimate is revised in a planning sheet and the board should carry the new figure before the next staffing decision.
Watch out
find the entry with List Workloads by Board first; to add a new one, Create a Workload is the right module.
Need help

Need help automating PLANTA pulse with Make?

A person reads every message.

FAQ

PLANTA pulse and Make: common questions

01Is the PLANTA pulse Make integration free?
Yes, on the Make side. PLANTA pulse is a standard app, so it works from the Free plan onward. That plan allows 2 active scenarios, 15 minutes at least 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 1 minute intervals and unlimited active scenarios. Your PLANTA pulse subscription is a separate matter: check the PLANTA pulse pricing page for it.
02What do you need to connect PLANTA pulse to Make?
An active PLANTA pulse account and a bearer token. You create the token in PLANTA pulse under Administration, then Users: add a user of type API User, click Create Token, then Create, and copy the key shown. In Make, add a PLANTA pulse module, click Create a connection, name it if you want and paste the token. The same connection then serves every PLANTA pulse module in your scenarios, so you only do this once.
03Does the PLANTA pulse trigger in Make work in real time?
No. Watch All Activities is a scheduled trigger: Make checks PLANTA pulse on the scenario's schedule, which is every 15 minutes by default. On the Free plan the shortest interval is 15 minutes; paid plans go down to 1 minute. Activity therefore reaches your scenario at the next check. The app has no instant trigger in Make, the kind an app calls through a webhook as soon as something happens.
04What if a PLANTA pulse module you need is missing in Make?
Use Make an API Call. With it, the scenario can call any endpoint of the PLANTA pulse API through the same connection, which covers what the 76 listed modules leave out. Keep in mind that the Make documentation page for this app says it was generated with AI from the vendor documentation and may contain mistakes, so confirm important details with PLANTA pulse before you rely on them, and test each call with Run once.
05Should you use Make or n8n with PLANTA pulse?
It depends on the tool your team already runs. On Make, PLANTA pulse brings 76 modules, including 1 scheduled trigger, 53 actions and 22 searches, plus Make an API Call for the rest, and it is available from the Free plan. The same app often has an n8n node too, so check whether n8n lists one for PLANTA pulse and compare the modules you actually need on each side before picking.
Same platform

Other docs you might need on this stack.

Browse all integrations