Resources · Make integration

Persat Make integrationAutomate Persat with Make.

Can Make keep your Persat clients, work orders and deliveries in sync with the rest of your tools? Yes. The Persat Make integration offers 40 modules: 3 triggers, 32 actions and 5 searches. This guide links your account and walks you through a first working scenario.

Try the Persat integration on MakeSee the 40 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Persat Make integration let you automate?

The Persat Make integration links your Persat account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a small brick that watches, reads or changes data. With it, client records, work orders, deliveries, digital forms and MasterDB elements move between Persat and your other apps without copy and paste.

Client onboarding that starts field work. Watch New Client Events notices a fresh client, and Create a Work Order and Assign opens the first job for a technician. Nobody has to remember to schedule the visit by hand.

Delivery updates your customers can follow. Create a Delivery registers the drop-off, then Get Delivery Track Link returns a link you can send by email or text from another app in the same scenario.

Reference data kept in one place. When a product list or price table lives in a spreadsheet, Create a MasterDB Element and Update a MasterDB Element copy each change into Persat, while List MasterDB Elements checks what is already there.

Know the limits before you build. The 3 triggers only follow client events (new, updated, deleted); nothing watches work orders or deliveries directly, so those flows start from another app or on a schedule. Each run counts operations, which the Make pricing guide explains. Make an API Call covers the rest of the Persat API with the same connection. The same app often has an n8n node too, and the n8n vs Make comparison lays out how the two tools differ. If you would rather learn the editor step by step, the Make training starts from zero.

Connect

How do you connect your Persat account to Make?

  1. 01

    Copy an API key from Persat

    In Persat, click the user icon at the top right, open Integrations and Partners, then Integra con nuestra API in the left sidebar. Go to Api keys, click Crear mi primer Api Key and copy the key shown on screen.

  2. 02

    Add a Persat module in Make

    Open your scenario in Make, add any Persat module and click Create a connection. A connection is your Persat account linked to Make once and reused by every Persat module afterward. The Connection name field is optional.

  3. 03

    Paste the key and save

    Paste the API key you copied into the credentials field, or follow the on-screen instructions, then save. Make can now read and write in your Persat account, and every other Persat module in the scenario picks the same connection from a list.

First scenario

Build your first scenario with Persat

GoalWhen a new client appears in Persat, Make creates a work order for that client and assigns it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + in the middle of the editor to place your first module.

  2. 02

    Pick the trigger

    Search for Persat, choose Watch New Client Events and select the connection you built earlier. This module starts the scenario each time Make finds a client that was just added.

  3. 03

    Add the work order

    Click the + on the right of the trigger and add Create a Work Order and Assign. Map the client data coming from the trigger into its fields so the order points to the right client.

  4. 04

    Test with Run once

    Add a test client in Persat, then click Run once. Each module shows the bundles it received, a bundle being one item passed along, here one client. Check that the work order looks right in Persat.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, and you can change that under Scheduling. Then switch the scenario on so it keeps running without you.

Triggers

What starts a Persat scenario?

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

Persat1Watch Deleted Client Events

Watch Deleted Client Events

triggerIn the docs only

This trigger tells your other tools that a client was removed from Persat, so a CRM, a billing sheet or a mailing list stops treating that customer as active. Each deleted client arrives as one bundle.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, which is why the module carries a clock badge rather than a lightning one.
When to use it
your sales pipeline or invoicing tool still lists the client and should flag or archive the record once Persat drops it.
Watch out
every module that handles a bundle spends an operation, the unit Make counts on your plan, so a cleanup of many clients can consume more than you expect.
Persat2Watch New Client Events

Watch New Client Events

triggerIn the docs only

Your scenario starts whenever a fresh client shows up in Persat, handing the new record to the modules that follow. It is the natural starting point for onboarding: welcome message, first job, CRM entry.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a client added a moment ago appears at the next check, not the same second.
When to use it
clients get created directly in Persat by your office team and the rest of the company needs to hear about them.
Watch out
if your scenario also creates clients with Create a Client, those clients will most likely come back through this trigger, so keep the two flows in separate scenarios.
Persat3Watch Updated Client Events

Watch Updated Client Events

triggerIn the docs only

Changes to an existing Persat client, a new phone number or a moved address, flow out to your other apps through this trigger, so the same person does not carry two versions across your tools.

How it fires
scheduled. Make checks the app on the scenario's schedule and passes along the clients that changed since then.
When to use it
Persat is where your dispatchers correct client details and your CRM or accounting tool should mirror those corrections.
Watch out
a scenario that writes back into Persat with Update a Client will most likely raise a new update event itself; route the change in one direction only to avoid an endless back and forth.
Modules

What can Make do in Persat?

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

Persat2

Cancel a Work Order

ActionIn the docs only

Calling off a Persat job from another tool keeps a technician from driving to a visit the client no longer wants.

When to use it
a cancellation reaches you through a web form, a CRM stage or a support ticket, and Persat should reflect it without anyone logging in.
Watch out
test with Run once on a dummy order first; a cancel sent to the wrong job disrupts real work in the field.
Persat3

Create a Client

ActionIn the docs only

A new Persat client record appears from data captured elsewhere, which spares your office from retyping names and addresses.

When to use it
a signed quote, a website form or a won deal in your CRM should become a Persat client straight away.
Watch out
when the same customer might already exist, search with List Clients first so the scenario does not create a second record for one person.
Persat4

Create a Client Object Element

ActionIn the docs only

Adds an element to one of the client objects set up in your Persat account, so extra information about a client lands in Persat instead of staying in a side file.

When to use it
details your team tracks per client, gathered in a form or a spreadsheet, need to show up inside Persat.
Watch out
the client and the object must exist before this module runs; place it after Create a Client or Get a Client.
Persat5

Create a Delivery

ActionIn the docs only

Registers a new delivery in Persat from an order placed in another system, so the drop-off enters your field planning with no manual entry.

When to use it
an online store, an ERP or an order spreadsheet receives a sale that someone on your team has to bring to the customer.
Watch out
pair it with Get Delivery Track Link if the customer expects a tracking link; this module alone does not send anything to them.
Persat6

Create a Digital Form

ActionIn the docs only

Creates a digital form in Persat from data held in another app, which puts the paperwork where technicians already work.

When to use it
an inspection checklist or intake questionnaire starts life in another tool and should be available in Persat for the next visit.
Watch out
build it once with Run once and check the result in Persat before letting the scenario create forms on its own.
Persat7

Create a MasterDB Element

ActionIn the docs only

With this module, a new entry lands in the MasterDB of your Persat account, the shared reference data your team picks from, without anyone typing it twice.

When to use it
a product, a site or a reference code gets added to a spreadsheet or an ERP and Persat should know about it too.
Watch out
run List MasterDB Elements first when the entry may already exist, or you will end up with duplicates.
Persat8

Create a Pending Work Order

ActionIn the docs only

Opens a work order in Persat and leaves it pending, so a dispatcher can review it and choose who goes before anything is assigned.

When to use it
requests come from customers or a support desk and need a human check before they reach a technician.
Watch out
if the job should go straight to someone, Create a Work Order and Assign is the better fit; a pending order waits until a person acts.
Persat9

Create a Work Order and Assign

ActionIn the docs only

Creates the work order and hands it to a technician in one step, so the job is on someone's list the moment the request arrives.

When to use it
the rule for who takes the job is clear, for example one technician per area, and no dispatcher needs to review it.
Watch out
map the assignee carefully during your Run once test; if the mapping is wrong, every single job ends up with the same person.
Persat10

Delete a Client

ActionIn the docs only

Removes a client from Persat when that customer leaves your books in another system, which keeps the Persat list free of dead records.

When to use it
an account gets closed in your CRM or billing tool and the field team should no longer see it.
Watch out
a deletion cannot be undone from Make; start the scenario on a clear event and test on a dummy client first.
Persat11

Delete a Client Object Element

ActionIn the docs only

Clears one element from a client object in Persat, handy when a piece of information about a client stops being true.

When to use it
an item tied to a client is retired or removed in your source tool and Persat should drop it as well.
Watch out
the module works on a single element, so look it up first with List Client Object Elements or Get a Client Object Element; a deletion is final.
Persat12

Delete a MasterDB Element

ActionIn the docs only

Takes an entry out of your Persat MasterDB, so technicians stop picking a product or reference that no longer exists.

When to use it
a line gets discontinued in your catalog or ERP and the reference data in Persat should follow.
Watch out
there is no undo from Make; if you only want to hide an entry, Update a MasterDB Element may be the safer choice.
Persat13

Get Gps Tracking Data

ActionIn the docs only

Pulls the GPS tracking data Persat holds, so positions recorded in the field can feed a report, a map or a spreadsheet.

When to use it
a manager wants the route history in a tool other than Persat, or proof of travel needs to be stored with an invoice.
Watch out
tracking data can return many points; each module that processes them afterward spends operations, so keep the flow short.
Persat14

Get Last Tracking Point

ActionIn the docs only

Returns only the latest position Persat recorded, which answers the simple question of where someone is right now without the full trail.

When to use it
a customer asks when the technician will arrive, and your support tool needs the most recent location to reply.
Watch out
for a whole route, reach for Get Gps Tracking Data instead; this module gives a single point.
Persat15

Get Visits to Clients

ActionIn the docs only

Brings back the visits made to clients as Persat recorded them, a quick way to build proof of service or a visit report outside Persat.

When to use it
account managers want visit history in the CRM, or finance needs it to back an invoice.
Watch out
the result can hold several visits; test with Run once and read the bundles before sending them anywhere.
Persat17

Get a Client

ActionIn the docs only

Reads one Persat client in full, so the next modules can use the name, address and other details stored there.

When to use it
a trigger or another app hands you only a client reference, and the email or invoice you are building needs the complete record.
Watch out
it reads a single client; to browse or search, List Clients is the module to use.
Persat18

Get a Client Custom Field Value

ActionIn the docs only

Fetches the value of one custom field on a Persat client, the kind of detail your company added on top of the standard record.

When to use it
a decision in the scenario depends on that value, such as a contract level or a preferred time slot your team stores in a custom field.
Watch out
it returns one field; if you need the whole client, Get a Client is simpler.
Persat19

Get a Client Object Element

ActionIn the docs only

Retrieves a single element from a client object, so details kept inside Persat can travel to a document, a message or another tool.

When to use it
you already know which element you need and want its data for the next step of the scenario.
Watch out
without the element reference, start with List Client Object Elements to find it.
Persat20

Get a Device

ActionIn the docs only

Looks up one device registered in Persat and returns its details, useful when a later step has to know which device sent data.

When to use it
tracking data or a visit comes with a device reference and your report should show more than that reference.
Watch out
to see every device on the account, List Devices returns them all as separate bundles.
Persat21

Get a Digital Form

ActionIn the docs only

Opens one digital form from Persat and passes its content along, so answers collected on site can reach a report, a file or your CRM.

When to use it
a completed inspection or checklist should be archived or shared outside Persat.
Watch out
the module needs to know which form to read, so an earlier step must supply that reference.
Persat22

Get a MasterDB Element

ActionIn the docs only

Reads one entry of your Persat MasterDB, bringing its data into the scenario for a quote, an order or a check.

When to use it
an order mentions a product or site code and you need the full reference data behind it.
Watch out
when you do not know the exact entry, List MasterDB Elements lets you look through the database first.
Persat23

Get a Work Order

ActionIn the docs only

Fetches the full detail of one Persat work order, so the status, client and assignee can drive the rest of your automation.

When to use it
a support ticket references a job and the agent should see its details without opening Persat.
Watch out
Persat has no work order trigger in Make, so this module usually sits after another app's trigger or a scheduled start.
Persat24

List Client Object Elements

SearchIn the docs only

As a search module, it returns the elements of a client object, zero, one or many, each one as its own bundle.

When to use it
you want to export what Persat holds for a client, or find the element to update or delete next.
Watch out
every returned element runs through the following modules and spends operations; test with Run once to see how many come back.
Persat25

List Clients

SearchIn the docs only

Searches your Persat clients and sends back every match as a separate bundle, which suits exports and duplicate checks.

When to use it
before Create a Client, to see whether the customer already exists, or to copy your client base into a spreadsheet.
Watch out
a search can return nothing; the modules after it then do not run, which is normal and not an error.
Persat26

List Devices

SearchIn the docs only

Gives you the devices registered on your Persat account, one bundle each, for an inventory or a check of what is active.

When to use it
you keep an equipment register elsewhere and want it to match what Persat knows.
Watch out
for the detail of a single device you already identified, Get a Device is lighter.
Persat27

List MasterDB Elements

SearchIn the docs only

Browses your Persat MasterDB and returns its entries as bundles, the starting point for syncing reference data with another tool.

When to use it
before creating an entry, to avoid a duplicate, or to compare the MasterDB with your catalog.
Watch out
a large database means many bundles and many operations downstream; check the count during Run once.
Persat28

List Users

SearchIn the docs only

Returns the users of your Persat account, which helps when a scenario needs to pick a technician or match people across tools.

When to use it
you assign work orders automatically and need the right person's reference, or you audit who has access.
Watch out
each user comes out as one bundle, so later modules run once per person unless you narrow the result.
Persat29

Make an API Call

ActionIn the docs only

When none of the ready modules does what you need, this one calls any endpoint of the Persat API, reusing the connection you already set up.

When to use it
a Persat feature has no dedicated module in Make and you know which API request covers it.
Watch out
you write the request yourself, so keep the Persat API documentation open and test with Run once before going live.
Persat30

Move Work Order To Pending State

ActionIn the docs only

Sends an existing work order back to pending, so a dispatcher can take another look before the job goes ahead.

When to use it
a customer asks to reschedule, or a missing part holds the job, and the order should leave the technician's list for now.
Watch out
to stop the job for good, Cancel a Work Order is the right module; pending means it can come back.
Persat31

Move a Client Object Element

ActionIn the docs only

Relocates a client object element in Persat, which saves deleting it and creating it again by hand.

When to use it
an item tracked for a client changes place in your records, and Persat should show it in its new spot.
Watch out
run it once on a test element and check the outcome in Persat before automating it.
Persat32

Update Work Order Labels

ActionIn the docs only

Changes the labels on a Persat work order, so your team can sort and spot jobs by the tags that matter to them.

When to use it
an event in another tool, such as a paid invoice or an urgent ticket, should mark the related work order.
Watch out
test how the labels you send combine with those already on the order before running it on live jobs.
Persat33

Update a Client

ActionIn the docs only

Writes changes into an existing Persat client, keeping phone numbers and addresses in step with the system your office trusts most.

When to use it
a customer updates their details in your CRM or portal and technicians need the new information.
Watch out
paired with Watch Updated Client Events in the opposite direction, it can bounce changes back and forth; sync one way only.
Persat34

Update a Client Custom Field Value

ActionIn the docs only

Sets the value of one custom field on a client, a precise edit that leaves the rest of the record untouched.

When to use it
a contract renewal or a new service level in another tool should show up on the Persat client.
Watch out
the module name points to setting a value, so create the custom field in Persat first.
Persat35

Update a Client Object Element

ActionIn the docs only

Edits an element inside a client object, so the information your team relies on in Persat stays current.

When to use it
the source of truth for that item lives in another tool and each change there should reach Persat.
Watch out
if the element may not exist yet, check with Get a Client Object Element first and create it when missing.
Persat36

Update a Digital Form

ActionIn the docs only

Changes a digital form already stored in Persat, so corrections made in another tool land on the same form instead of a new copy.

When to use it
back-office staff complete or correct form data outside Persat after the visit.
Watch out
read the form with Get a Digital Form during your first test to confirm you are editing the right one.
Persat37

Update a MasterDB Element

ActionIn the docs only

Refreshes an entry of your Persat MasterDB from another system, so prices, names or codes match everywhere.

When to use it
your ERP or catalog spreadsheet changes a product and Persat should reflect it without manual edits.
Watch out
when the entry is missing, the scenario needs a path to Create a MasterDB Element instead.
Need help

Need help automating Persat with Make?

A person reads every message.

FAQ

Persat and Make: common questions

01Is the Persat Make integration free?
Yes, on the Make side. Persat 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 per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute and count usage in credits per month. You still need an active Persat account; its subscription is described on the Persat pricing page.
02What do you need to connect Persat to Make?
An active Persat account and an API key. In Persat, click the user icon, go to Integrations and Partners, then Integra con nuestra API and Api keys, and click Crear mi primer Api Key to generate one. In Make, add a Persat module, click Create a connection, paste the key and save. The connection is then reused by every Persat module in your scenarios, so this setup happens once, and you never paste the key again.
03Does the Persat trigger in Make react in real time?
No. The 3 Persat triggers, Watch New Client Events, Watch Updated Client Events and Watch Deleted Client Events, are scheduled: Make checks Persat on the scenario's schedule, every 15 minutes by default, and never faster than 15 minutes on the Free plan. The Make documentation lists these modules without a type, so the scheduled label comes from their names. On a paid plan the interval can go down to 1 minute.
04What if a Persat module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Persat API with the connection you already created, so a feature without a dedicated module is still within reach. You write the request yourself, which means having the Persat API documentation at hand. Note also that the Make documentation for Persat is marked as AI-generated from the vendor's docs, so verify important details with Persat directly before relying on them.
05Make or n8n for Persat?
It depends on what you need. In Make, Persat comes with 40 ready modules, including triggers on client events, work order and delivery actions, and Make an API Call for the rest. The same app often has an n8n node as well, so check on the n8n side which Persat operations it covers before choosing. The right pick is the tool whose modules match your scenario and whose editor your team is comfortable with.
Same platform

Other docs you might need on this stack.

Browse all integrations