Resources · Make integration

Plutio Make integrationAutomate Plutio with Make.

Can Make handle your Plutio proposals, invoices and tasks for you? The Plutio Make integration offers 54 modules, 10 of them triggers, for freelancers and studios who run clients in Plutio. Here you connect your account, build a first scenario and pick the right module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Plutio Make integration automate?

The Plutio Make integration links your Plutio account to Make, a no-code tool where you build a scenario: a chain of modules that runs on a schedule or when an app calls Make. Each module is one brick, like a trigger that watches Plutio or an action that creates a task, so client work moves between your tools without copy and paste.

A proposal turns into a project. Watch Proposals picks up proposals from Plutio; from there Create a Project opens the job and Create a Task adds the first to-do, so nobody retypes the client details.

Invoices reach your books. Watch Invoices hands each invoice it finds to the next module, for example a row in an accounting sheet, while Search Invoices pulls invoices on demand in the middle of a longer scenario.

Contacts stay in one place. When a lead fills a form in another app, Search People checks whether that person is already in Plutio, then Create a Person or Update a Person keeps a single record.

Make's documentation for Plutio is limited: it lists the modules but says little about their fields, so test each one with Run once, the editor button that runs the scenario a single time. For what the modules skip, Make an API Call reaches the Plutio API with the same connection. The same app may also have an n8n node; the n8n vs Make comparison lays out the criteria, Make pricing explains how operations are counted, and Make training covers the editor from the start.

Connect

How do you connect Plutio to Make?

  1. 01

    Add a Plutio module

    Open your scenario, click the + and search for Plutio. Pick any module, Watch Tasks for example, then click Create a connection. A connection is your Plutio account linked to Make once and reused by every Plutio module.

  2. 02

    Name it and authorize Make

    Give the connection a name you will recognize later, such as the workspace it belongs to; this part is optional. Then follow the window: authorize Make on the Plutio page, or paste the key Plutio gives you if that is what it asks for.

  3. 03

    Save and reuse it

    Click Save. Back in the module, Make can now read your Plutio account and lists what it finds in the fields. Every other Plutio module you add later offers this same connection in its dropdown.

First scenario

Build your first Plutio scenario

GoalWhen Make picks up a proposal in Plutio, it creates a project and adds a first task to it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module. Search for Plutio and choose Watch Proposals, the trigger that starts the flow.

  2. 02

    Connect the trigger

    Click Create a connection to link your Plutio account, or pick the one you already made. Fill the fields the module shows; once connected, Make lists what it can read in your account.

  3. 03

    Add the project and the task

    Click the + on the right of Watch Proposals and add Create a Project, mapping data from the proposal. Add Create a Task next and map values from the two earlier modules.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles, the items passed from one module to the next, so you can check the project and task in Plutio.

  5. 05

    Schedule and switch on

    Open the clock on Watch Proposals: a new scenario checks every 15 minutes by default, which is also the shortest gap on the Free plan. Then switch the scenario on.

Triggers

What can start a Plutio scenario?

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

Plutio1Watch Forms

Watch Forms

Scheduled trigger

In MakeWatches for forms.

Watch Forms starts your scenario from the forms in your Plutio account, so each form it picks up becomes a bundle, one item passed to the next module, that you can route anywhere.

How it fires
scheduled. Make checks Plutio on the scenario's schedule, every 15 minutes by default.
When to use it
your intake form lives in Plutio and its details should land in a spreadsheet or a CRM without anyone copying them.
Watch out
on the Free plan the shortest gap between two checks is 15 minutes.
Plutio2Watch Invoices

Watch Invoices

Scheduled trigger

In MakeWatches for invoices.

Watch Invoices keeps an eye on your Plutio invoices and starts the scenario with each invoice it finds, ready to be copied, announced or filed in another tool.

How it fires
scheduled. Make checks Plutio each time the scenario's schedule comes round, and never in between.
When to use it
your bookkeeping lives in a spreadsheet or an accounting app, and every Plutio invoice should appear there without a manual export.
Watch out
paid plans let you check as often as every 1 minute; the Free plan stops at 15.
Plutio3Watch Notifications

Watch Notifications

Instant trigger

In MakeWatches for events selected in Plutio webhooks settings.

Watch Notifications is the only instant trigger of the app: it receives the events you selected in Plutio's webhook settings and starts the scenario with each one.

How it fires
instant. Plutio calls Make through a webhook as soon as the event happens; the lightning badge on the module marks it.
When to use it
speed matters, for instance alerting your team chat when something changes on a client account.
Watch out
only the events ticked in Plutio's webhook settings reach Make, so review that list when an expected event never shows up.
Plutio4Watch People

Watch People

Scheduled trigger

In MakeWatches for people.

Watch People follows the contacts in your Plutio account and hands each person it picks up to the next module, a natural start for syncing your client list elsewhere.

How it fires
scheduled: Make asks Plutio on the scenario's schedule, shown by the clock badge on the module.
When to use it
your newsletter tool or CRM should know every person you add in Plutio, without importing files by hand.
Watch out
nothing moves between two checks, so a contact added right after a run waits for the next one.
Plutio5Watch Projects

Watch Projects

Scheduled trigger

In MakeWatches for projects.

Watch Projects starts your scenario from Plutio projects, turning each project it finds into a bundle other apps can use.

How it fires
scheduled. Make polls Plutio at the interval set on the scenario's clock, 15 minutes unless you change it.
When to use it
opening a project in Plutio should also open a shared folder in your file storage or a channel in your team chat.
Watch out
the documentation does not say whether edited projects come through as well as new ones, so check with Run once which projects arrive.
Plutio6Watch Proposals

Watch Proposals

Scheduled trigger

In MakeWatches for proposals.

Watch Proposals picks up proposals from your Plutio account and launches the scenario for each one; it is the first brick of the scenario shown on this page.

How it fires
scheduled: at each run of the scenario's schedule, Make checks Plutio for proposals.
When to use it
a proposal should set follow-up work in motion, such as a project in Plutio, a deal in your CRM or a note in your sales channel.
Watch out
each proposal becomes one bundle, and every following module runs once per bundle, which adds up in operations.
Plutio7Watch Task Boards

Watch Task Boards

Scheduled trigger

In MakeWatches for task boards.

Watch Task Boards reports the boards of your Plutio workspace to Make, so a board can set other tools in motion.

How it fires
scheduled; Make queries Plutio when the scenario's clock says so, every 15 minutes on a new scenario.
When to use it
in your way of working each board stands for a client engagement, and your time tracker or planning sheet should reflect it.
Watch out
the Free plan allows 2 active scenarios, so group board-related steps in one scenario rather than spreading them out.
Plutio8Watch Task Groups

Watch Task Groups

Scheduled trigger

In MakeWatches for task groups.

Watch Task Groups catches the task groups in Plutio and passes each one to the rest of the scenario.

How it fires
scheduled. Make checks Plutio whenever the scenario's schedule is due, based on the clock of this first module.
When to use it
you organize phases of work as groups, and each phase should show up as a section in your planning tool or a heading in a shared document.
Watch out
run it once before switching on and read the bundles, since the documentation does not list what a group carries.
Plutio9Watch Tasks

Watch Tasks

Scheduled trigger

In MakeWatches for tasks.

Watch Tasks turns the tasks in Plutio into the starting point of a scenario, each task it finds becoming one bundle for the next module.

How it fires
scheduled: Make looks at Plutio on the scenario's schedule, which you set with the clock on this first module.
When to use it
tasks created in Plutio should also appear in a to-do app, a calendar or a message to the person in charge.
Watch out
tasks can be numerous and each bundle consumes operations in the modules that follow, so keep the chain short.
Plutio10Watch Templates

Watch Templates

Scheduled trigger

In MakeWatches for templates.

Watch Templates tracks the templates saved in your Plutio account and starts the scenario with each one it finds.

How it fires
scheduled; Make checks Plutio on the scenario's schedule, as often as every 1 minute on paid plans and every 15 minutes at best on Free.
When to use it
your team keeps a catalog of templates in a shared sheet or wiki and wants it current without manual copying.
Watch out
Make's documentation for Plutio is thin, so confirm with Run once what a template bundle contains.
Modules

What each Plutio module does

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

Plutio1

Copy a Task

Action

In MakeCopies a specified task.

Copy a Task duplicates a task you already set up in Plutio, so a to-do you defined once can be reused without typing it again.

When to use it
every new client project opens with the same kickoff task, and you want a fresh copy as soon as the project appears.
Watch out
point the module at the right source task; Search Tasks can locate it earlier in the scenario.
Plutio2

Copy a Task Board

Action

In MakeCopies a specified task board.

With Copy a Task Board you get a full duplicate of an existing board, a quick way to reuse a layout of tasks that already works for you.

When to use it
each proposal Make picks up should give the client a board shaped like your model board, with Watch Proposals at the start.
Watch out
the documentation does not say which parts of the board are carried over, so check the copy after a Run once.
Plutio3

Copy a Task Group

Action

In MakeCopies a specified task group.

Copy a Task Group gives you a second copy of a group of tasks, handy when a batch of steps repeats inside the same project.

When to use it
a client adds an extra deliverable in your CRM and the same review steps are needed again.
Watch out
try it on a test project first, because the documentation is silent on what the copy contains.
Plutio4

Create a Block

Action

In MakeCreates a new block.

Create a Block adds a new block to your Plutio account straight from the scenario, filled with data mapped from earlier modules.

When to use it
content produced elsewhere, such as the answers of a form in another app, should show up in Plutio as a block without anyone pasting it.
Watch out
Make lists what the block needs once the connection exists; fill only what you can map reliably.
Plutio5

Create an Invoice

Action

In MakeCreates a new invoice.

Create an Invoice builds a Plutio invoice from data your scenario already holds, so billing starts without retyping amounts or client details.

When to use it
an order confirmed in your online shop or a delivered job should become an invoice in Plutio right away.
Watch out
test it on a dummy client first, because every run creates a real invoice.
Plutio6

Create a Person

Action

In MakeCreates a new person.

Create a Person adds someone to your Plutio contacts using details that came from another app, so nobody types the same contact twice.

When to use it
a lead books a call through your website form and should exist in Plutio before the call.
Watch out
place Search People in front of it, otherwise a returning lead gets a second record.
Plutio7

Create a Project

Action

In MakeCreates a new project.

Create a Project opens a new project in Plutio and fills it from earlier modules, so the job exists the moment the deal is done.

When to use it
Watch Proposals picks up a proposal and you want the matching project ready without opening Plutio.
Watch out
map values from the trigger's bundle instead of typing fixed text, or every project will look the same.
Plutio8

Create a Proposal

Action

In MakeCreates a new proposal.

Create a Proposal prepares a new proposal in Plutio from data collected upstream, so the quote waits for you instead of a blank page.

When to use it
a prospect fills a brief on your site and you want a proposal started for them, ready for you to review and finish in Plutio.
Plutio9

Create a Task

Action

In MakeCreates a new task.

Create a Task drops a new to-do into Plutio with the details mapped from any earlier module.

When to use it
a support email or a message in your chat tool asks for work, and it should be logged as a task the team will see.
Watch out
it creates one task per bundle, so a search upstream that returns ten items gives ten tasks.
Plutio10

Create a Task Board

Action

In MakeCreates a new task board.

Create a Task Board sets up a new board in Plutio, ready to receive tasks from the next modules of the scenario.

When to use it
a new project needs its own board and you prefer building it step by step rather than copying a model.
Watch out
if you already keep a model board, Copy a Task Board spares you from recreating each task.
Plutio11

Create a Task Group

Action

In MakeCreates a new task group.

Create a Task Group adds a fresh group so related tasks stay together, for example every task of one delivery phase.

When to use it
a change on a project, logged in your CRM, calls for a new batch of work in Plutio.
Watch out
place the group before the task modules in the scenario, so they can map it.
Plutio12

Delete a Block

Action

In MakeDeletes a specified block.

Delete a Block removes a block from Plutio for good, which keeps your account clear of content that no longer serves.

When to use it
a block was created automatically by mistake, or its source item was deleted in another app and it should go too.
Watch out
a deletion cannot be undone from Make, so test with Run once on a dummy block.
Plutio13

Delete an Invoice

Action

In MakeDeletes a specified invoice.

Delete an Invoice erases an invoice from Plutio, useful when a duplicate or a test invoice slipped in through automation.

When to use it
an order is cancelled in your shop before billing, and the invoice created for it should disappear.
Watch out
nothing brings the invoice back afterward; check the one you target with Get an Invoice first.
Plutio14

Delete a Person

Action

In MakeDeletes a specified person.

Delete a Person takes a contact out of Plutio, so your people list matches what your other tools hold.

When to use it
someone asks to be removed from your CRM and the same removal should happen in Plutio.
Watch out
map the exact person found by Search People; a wrong match removes the wrong record for good.
Plutio15

Delete a Project

Action

In MakeDeletes a specified project.

Delete a Project removes a whole project from Plutio in one step, for cleanups driven by another system.

When to use it
a deal is marked lost in your CRM, and the project opened for it in advance has no reason to stay.
Watch out
the documentation says nothing on what happens to the project's content, so try it on a test project before live data.
Plutio16

Delete a Proposal

Action

In MakeDeletes a specified proposal.

Delete a Proposal clears a proposal out of Plutio, leaving only the quotes that are still in play.

When to use it
a prospect withdraws through your form or your inbox, and the proposal prepared for them should vanish.
Watch out
this is permanent, so fetch it first with Get a Proposal and confirm it is the right one.
Plutio17

Delete a Task

Action

In MakeDeletes a specified task.

Delete a Task removes a task from Plutio, which helps when tasks are mirrored from another tool and must stay in step with it.

When to use it
a ticket is closed as not needed in your helpdesk, and the task created from it should leave Plutio too.
Watch out
a deleted task cannot be recovered through Make; rehearse on a copy made with Copy a Task.
Plutio18

Delete a Task Board

Action

In MakeDeletes a specified task board.

Delete a Task Board takes down an entire board, a broad cleanup step compared with removing single tasks.

When to use it
a temporary board was opened for a one-off event, and the event is over in your calendar app.
Watch out
Make's documentation does not say whether the tasks on the board go with it, so assume they do and test first.
Plutio19

Delete a Task Group

Action

In MakeDeletes a specified task group.

Delete a Task Group removes a single task group from Plutio when that set of steps is no longer needed.

When to use it
an optional phase is dropped from a project, for instance after the client trims the scope in your CRM.
Watch out
identify the group with Search Task Groups before deleting, because there is no undo.
Plutio20

Get a Block

Action

In MakeReturns a specified block.

Get a Block returns one block you point to, so its content can feed the next modules of the scenario.

When to use it
a later step, such as an email or a document in another app, needs the content of a block you already know.
Watch out
it fetches a single item; when you do not know which block, Search Blocks is the better start.
Plutio21

Get an Invoice

Action

In MakeReturns a specified invoice.

Get an Invoice reads one invoice from Plutio and hands its details to the rest of the scenario.

When to use it
a payment recorded in your bank or payment app points to an invoice, and your accounting tool needs its full details.
Watch out
it reads one invoice per run; to pull several at once, Search Invoices returns them as separate bundles.
Plutio22

Get a Person

Action

In MakeReturns a specified person.

Get a Person fetches a single contact's record so later modules can use its details, like a name for a personal message.

When to use it
a task or a project in the scenario refers to someone, and you need more than what that bundle carries.
Watch out
one run, one person; to go through a list of contacts, Search People fits better.
Plutio23

Get a Project

Action

In MakeReturns a specified project.

Get a Project pulls the current state of one project into your scenario, ready to map into a report, a message or another app.

When to use it
before posting an update to your team chat, you want the project's latest details rather than those captured earlier.
Watch out
each call counts as an operation, one module run on one bundle, so skip it when the trigger already gives you enough.
Plutio24

Get a Proposal

Action

In MakeReturns a specified proposal.

Get a Proposal reads the proposal you target and exposes its details for the next steps.

When to use it
the key points of a proposal should be copied into your CRM deal when an event in another tool calls for it.
Watch out
pair it with Search Proposals when the scenario knows the client but not the proposal itself.
Plutio25

Get a Task

Action

In MakeReturns a specified task.

Get a Task returns one task with what Plutio keeps on it, so the scenario acts on up-to-date data.

When to use it
a reminder in another app should quote the task as it stands now, before you move or update it.
Watch out
map the task from an earlier bundle; a fixed value makes every run read the same task.
Plutio26

Get a Task Board

Action

In MakeReturns a specified task board.

Get a Task Board brings the details of one board into the scenario, for instance to name it in a message.

When to use it
Copy a Task Board or Update a Task Board comes next, and you want to confirm you are on the right board.
Watch out
what the module returns is not documented, so read the bundle after Run once.
Plutio27

Get a Task Group

Action

In MakeReturns a specified task group.

Get a Task Group returns a single group, so you can reuse its details further down the scenario.

When to use it
a status message in your team chat should mention a group, and an earlier module already gave you the reference to that group.
Plutio28

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Make an API Call lets you reach any endpoint of the Plutio API from the scenario, with the connection you already created.

When to use it
none of the other modules covers what you need, but the Plutio API does.
Watch out
you write the request yourself, so test it with Run once and read the response bundle before building on it.
Plutio29

Move a Task

Action

In MakeMoves a specified task.

Move a Task relocates an existing task inside Plutio, so a to-do follows your process without a drag and drop by hand.

When to use it
a file is approved in your review tool, and the related task should move on.
Watch out
Make's documentation does not list the possible destinations; open the module after connecting to see what it offers.
Plutio30

Update an Invoice

Action

In MakeUpdates a specified invoice.

Update an Invoice changes an invoice already in Plutio, keeping it aligned with what happens in your other tools.

When to use it
a discount agreed by email or a corrected order in your shop should show on the invoice before it goes out.
Watch out
update the invoice found by Search Invoices or Watch Invoices, never one typed by hand in the module.
Plutio31

Update a Person

Action

In MakeUpdates a specified person.

Update a Person refreshes a contact's record in Plutio when the details change elsewhere.

When to use it
a client's details change in your CRM or your billing tool, and Plutio should carry the new version.
Watch out
run Search People first, then update the match; without that step the scenario has no person to target.
Plutio32

Update a Project

Action

In MakeUpdates a specified project.

Update a Project edits a project in place, so its details reflect progress logged in other tools.

When to use it
a contract is signed in your e-signature app, and the project in Plutio should show it.
Watch out
Get a Project just before lets you compare current values and avoid overwriting a recent manual edit.
Plutio33

Update a Proposal

Action

In MakeUpdates a specified proposal.

Update a Proposal revises a proposal that already exists, sparing you a trip into Plutio for small changes.

When to use it
the prospect answers your follow-up email with a new scope, and the proposal should pick up the new details.
Watch out
map the proposal from Watch Proposals or Search Proposals so the change lands on the right quote.
Plutio34

Update a Task

Action

In MakeUpdates a specified task.

Update a Task changes a task's details, the natural follow-up when work tracked elsewhere evolves.

When to use it
the plan shifts in your client's shared calendar or project sheet, and the Plutio task should follow.
Watch out
if no task was found upstream, the module has nothing to update; Search Tasks settles that first.
Plutio35

Update a Task Board

Action

In MakeUpdates a task board.

Update a Task Board adjusts the board itself rather than its tasks, keeping it in line with the project it serves.

When to use it
a project gets renamed in your CRM, and the board opened for it should match.
Watch out
Make shows the editable fields in the module once connected; the documentation adds nothing beyond that.
Plutio36

Update a Task Group

Action

In MakeUpdates a specified task group.

Update a Task Group edits one group of tasks, keeping a board tidy as the work evolves.

When to use it
a phase of work is reorganized in your planning tool, and the matching Plutio group should reflect it.
Watch out
target the group with Search Task Groups or Get a Task Group, since a wrong reference changes the wrong phase.
Plutio37

Search Blocks

Search

In MakeSearches for blocks.

Search Blocks looks through your Plutio blocks and returns every match as its own bundle for the next module.

When to use it
you want to check existing blocks before adding one, so Create a Block does not produce a duplicate.
Watch out
the search can return zero, one or many results, and each result runs the following modules once.
Plutio38

Search Invoices

Search

In MakeSearches for invoices.

Search Invoices finds invoices in Plutio and passes each one down the scenario, a good base for exports and follow-ups.

When to use it
your accountant asks for the invoices of a client, and you want them copied into a shared sheet.
Watch out
with no result the next modules do not run, which is easy to mistake for an error during a Run once.
Plutio39

Search People

Search

In MakeSearches for people.

Search People checks your Plutio contacts and returns the people that match, so the scenario knows who already exists.

When to use it
right before Create a Person, to decide between adding a newcomer and updating a known contact.
Watch out
a search can return several people; check the bundles after Run once and decide which match the next module should use.
Plutio40

Search Projects

Search

In MakeSearches for projects.

Search Projects scans your Plutio projects and returns each match to the following modules, one bundle per project.

When to use it
a client message arrives in your inbox and the scenario must find the project it belongs to before logging anything.
Watch out
a broad search can return many projects, and every bundle costs operations in the next modules.
Plutio41

Search Proposals

Search

In MakeSearches for proposals.

Search Proposals pulls back the Plutio proposals that match what you ask for, so the rest of your scenario can read them or act on each one. Each proposal arrives as its own bundle.

When to use it
a new deal lands in your CRM and you want to check whether that client already has a proposal in Plutio before drafting another.
Watch out
a search can return zero, one or several proposals, so plan what happens when nothing comes back.
Plutio42

Search Task Boards

Search

In MakeSearches for task boards.

Search Task Boards finds the boards in your Plutio workspace and hands them to the next step, one bundle per board, so you locate the right board without picking it by hand.

When to use it
a project gets signed and your scenario needs the matching board before it adds tasks or copies it for the new client.
Watch out
if you already know exactly which board you want, Get a Task Board is the lighter choice.
Plutio43

Search Task Groups

Search

In MakeSearches for task groups.

Search Task Groups returns the task groups that fit your search, so your scenario can drop work into the right group without anyone looking it up.

When to use it
a form reply should become a task, and the task has to land in a specific group such as the one for incoming requests.
Watch out
several groups can match, and every result costs an operation downstream, so narrow the search before chaining actions.
Plutio44

Search Tasks

Search

In MakeSearches for tasks.

Search Tasks lists the Plutio tasks that meet your criteria and sends each one down the scenario as a separate bundle. It pins down which tasks you mean before you update or move them.

When to use it
an invoice is paid and you want to find the open tasks tied to that client, then mark them or move them with Move a Task.
Watch out
with no match the modules after it simply don't run, so test with Run once on real data.
Need help

Need help automating Plutio with Make?

A person reads every message.

FAQ

Plutio and Make: common questions

01Is the Plutio Make integration free?
Yes. Plutio is a standard app in Make, so its modules work from the Free plan onward. That plan allows 2 active scenarios, a shortest interval of 15 minutes between scheduled runs, 5 minutes per execution, 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 and count usage in monthly credits, meaning operations. Your Plutio subscription is a separate matter that Make does not cover.
02What is needed to connect Plutio to Make?
You need a Plutio account and a Make account. Make's documentation lists no prerequisite for Plutio and no dedicated connection steps, so the standard flow applies: add a Plutio module, click Create a connection, name it if you wish, authorize Make on the Plutio page or paste the key Plutio gives you, then click Save. That connection then serves every Plutio module in your scenarios, so the setup happens once per account.
03Does the Plutio trigger in Make fire in real time?
It depends on the trigger. Watch Notifications is instant: Plutio calls Make through a webhook as soon as one of the events selected in its webhook settings happens. The other 9 triggers, such as Watch Tasks or Watch Invoices, are scheduled: Make checks Plutio on the scenario's schedule, every 15 minutes by default. On a paid plan that interval can drop to 1 minute, while the Free plan keeps it at 15 minutes minimum.
04What if a Plutio module is missing in Make?
Use Make an API Call. This module calls any endpoint of the Plutio API from your scenario with the connection you already have, so it covers what the other modules leave out. Keep in mind that Make's documentation for Plutio is limited and says little about fields, so test each call with Run once and read the returned bundle. If the API does not cover the need either, another app in the same scenario can take over that step.
05Make or n8n for Plutio?
It depends on the tool you already work with. In Make, Plutio comes with 54 ready modules: 10 triggers including one instant, 36 actions and 8 searches, with Make an API Call among the actions for everything else. n8n often has a node for the same apps, so check whether a Plutio node exists there before choosing. Base the decision on the modules your process needs and on the platform your team already uses.