Resources · Make integration

Pipefy Make integrationAutomate Pipefy with Make.

Want your Pipefy pipes to react on their own when a card changes? The Pipefy Make integration gives you 23 modules, including 7 instant triggers on cards. This guide connects your account, builds a first scenario and explains when each module earns its place.

Try the Pipefy integration on MakeSee the 23 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Pipefy Make integration automate?

The Pipefy Make integration links your Pipefy account to Make, a no-code tool where you build a scenario: a chain of modules that runs when an app calls Make or on a schedule. Pipefy tells Make when a card is created, moved, finished or late, and Make can then create, update or move cards and table records for you.

Requests that open their own card. A form, a spreadsheet row or an email in another app can start the scenario, and Create a Card drops the request into the right pipe with its fields filled. Nobody retypes anything.

Late work that escalates by itself. Watch Late Cards fires the moment Pipefy flags a card, and Move a Card to Phase pushes it into an escalation phase where a manager spots it. The same idea works with Watch Overdue Cards and Watch Expired Cards.

Reference tables kept in step. Pipefy tables hold suppliers, clients or assets. Create a Table Record and Update a Table Record keep them aligned with the tool where that data really lives, such as the one described in our Airtable Make integration guide.

What the Make side does not cover: the Pipefy documentation gives no numeric limit, and anything outside the listed modules goes through Make an API Call or Execute a GraphQL Query. Pipefy may also be reachable from n8n; our n8n vs Make comparison lays out the criteria, and the Make training covers the editor from scratch.

Connect

How do you connect Pipefy to Make?

  1. 01

    Generate your Pipefy credentials

    Sign in to Pipefy with Super Admin permissions, open your avatar, then Company settings. In Service Accounts, click Generate new token, give it a name, a role and an expiration, then copy the Client ID and Client Secret somewhere safe.

  2. 02

    Open the connection window in Make

    Add any Pipefy module to your scenario and click Create a connection. A connection is your Pipefy account linked to Make once, then reused by every Pipefy module. Naming it in Connection name is optional but helps later.

  3. 03

    Paste the keys and save

    Fill Client ID and Client Secret. Touch Subdomain only if your workspace has a custom domain: for bestsaas.pipefy.com you type just bestsaas. Click Save and confirm access if Pipefy asks.

First scenario

Your first scenario with Pipefy and Make

GoalWhen Pipefy flags a card as late, Make moves it into your escalation phase.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Search for Pipefy and pick Watch Late Cards as your first module.

  2. 02

    Link the trigger to Pipefy

    Click Create a webhook, then Create a connection with the credentials from the previous section. Once connected, fill the trigger's fields: Make lists what it can read in your account, so you pick from a menu instead of typing.

  3. 03

    Add the move

    Click the + to the right of the trigger and add Move a Card to Phase. Map the card coming from the trigger, then choose the phase where late work should land.

  4. 04

    Test with a real late card

    Click Run once, then let a test card go late in Pipefy. Each module shows the bundle it received, meaning the card data passed along, so you can check the right card moved.

  5. 05

    Switch it on

    Turn the scenario on. Because the trigger is instant, Pipefy calls Make as soon as a card turns late, and each module run counts as one operation on your Make plan.

Triggers

Pipefy triggers in Make

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

Pipefy1Watch Card Field Update

Watch Card Field Update

Instant trigger

In Make“Trigger when a card field updated.”

Any time someone edits a field on a card, this trigger hands the change to your scenario, so a new amount, owner or status can ripple into other tools without a copy and paste.

How it fires
instant: Pipefy calls Make through a webhook as soon as the field changes.
When to use it
a finance pipe where an updated budget field should reach your accounting sheet or a Slack channel.
Watch out
every edit sends a bundle, so a busy pipe can use more operations than you expect.
Pipefy2Watch Done Cards

Watch Done Cards

Instant trigger

In Make“Triggers when a card is marked as done.”

Finished work becomes a signal: this trigger starts your scenario when a card is marked as done, which is the natural moment to close the loop with a client, an invoice or a report.

How it fires
instant: Pipefy calls Make through a webhook as soon as the card is completed.
When to use it
an onboarding pipe where a done card should send the welcome email and archive the file elsewhere.
Watch out
use this one for completion, and Watch Moved Cards if your pipe has several final phases you treat differently.
Pipefy3Watch Expired Cards

Watch Expired Cards

Instant trigger

In Make“Triggers when a card expires.”

You get a scenario run the moment Pipefy marks a card as expired, which lets you react to work that ran past its window instead of discovering it during a review.

How it fires
instant: Pipefy calls Make through a webhook as soon as the card expires.
When to use it
quotes or approval requests that lose their value once expired and should be closed or reassigned.
Watch out
expired, late and overdue are three separate Pipefy triggers; pick the one matching the status your pipe actually sets.
Pipefy4Watch Late Cards

Watch Late Cards

Instant trigger

In Make“Triggers when a card gets late.”

This trigger turns a slipping card into an action: as soon as Pipefy considers a card late, your scenario can alert someone or move the card where it will be seen.

How it fires
instant: Pipefy calls Make through a webhook as soon as the card gets late.
When to use it
a support or purchasing pipe where late requests need a manager's eyes before they turn into complaints.
Watch out
if you also move the card, test the flow with Run once on a dummy card before your real pipe depends on it.
Pipefy5Watch Moved Cards

Watch Moved Cards

Instant trigger

In Make“Triggers when a card in a particular pipe is moved.”

Phase changes are where most processes hand work over, and this trigger fires when a card in the pipe you choose moves, so the next team hears about it without checking the board.

How it fires
instant: Pipefy calls Make through a webhook as soon as the card moves.
When to use it
a hiring pipe where moving a candidate to the interview phase should create a calendar event.
Watch out
the trigger watches one pipe; a move made by one of your own scenarios can start it as well, so keep an eye out for loops.
Pipefy6Watch New Cards

Watch New Cards

Instant trigger

In Make“Triggers when a new card is created.”

Every fresh card becomes the start of an automation: the trigger runs your scenario when a card is created, whether a teammate, a Pipefy form or another scenario added it.

How it fires
instant: Pipefy calls Make through a webhook as soon as the card exists.
When to use it
announcing each new request in a team channel, or copying it into a CRM as a lead.
Watch out
if the same scenario also uses Create a Card in that pipe, each new card can start another run, so keep creation and watching in separate flows.
Pipefy7Watch Overdue Cards

Watch Overdue Cards

Instant trigger

In Make“Triggers when a card gets overdue.”

Deadlines stop hiding in the board: this trigger starts your scenario when a card becomes overdue, so you can chase the owner or warn the client before anyone asks.

How it fires
instant: Pipefy calls Make through a webhook as soon as the card goes overdue.
When to use it
contract or compliance pipes where a missed due date needs a written trace and a named person to act.
Watch out
an overdue card may already have fired Watch Late Cards; decide which status drives your alert to avoid two messages for one card.
Modules

What Make can do in Pipefy

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

Pipefy1

Create a Card

Action

In Make“Creates a new card.”

New requests land in Pipefy without anyone typing them: this action opens a card in the pipe you pick and fills it with data from earlier modules.

When to use it
a web form, an email or a spreadsheet row in another app should become a card in your intake pipe.
Watch out
check with Run once that the card lands in the intended pipe with the values you mapped.
Pipefy2

Create a Table

Action

In Make“Creates a new table.”

This one builds structure rather than data: it adds a brand new Pipefy table, useful when each client, project or event deserves its own reference list.

When to use it
a new project card is done and you want a dedicated table ready for its suppliers.
Watch out
run it once per real need; placed in a busy flow, it will pile up tables quickly.
Pipefy3

Create a Table Record

Action

In Make“Creates a new table record.”

Your Pipefy tables fill themselves: the action adds a record, like a supplier, a contact or an asset, using data that arrived earlier in the scenario.

When to use it
a new row in a shared spreadsheet or a new contact in your CRM should also exist in a Pipefy table.
Watch out
it always adds; pair it with List Table Records first if duplicates would hurt.
Pipefy4

Delete a Card

Action

In Make“Deletes a card.”

Cleanup without the clicking: this action removes a card from Pipefy when your scenario decides it no longer belongs there, such as spam or a duplicate request.

When to use it
a request is cancelled in the original tool and the matching card should vanish from the pipe.
Watch out
treat deletion as final and try it on a test card with Run once before switching the scenario on.
Pipefy5

Delete a Table Record

Action

In Make“Deletes a table record.”

A record that is gone at the source disappears from your Pipefy table too, which keeps lookups and connected cards from pointing at stale entries.

When to use it
a supplier is removed from your ERP or a client closes their account and the table must follow.
Watch out
be sure the scenario targets the right record, ideally found by Get a Table Record just before.
Pipefy6

Execute a GraphQL Query

Action

In Make“Performs an arbitrary authorized GraphQL query.”

Pipefy speaks GraphQL, and this module lets you send your own query with the existing connection, reaching data or actions that the ready-made modules do not offer.

When to use it
you need a precise mix of card, phase and field data in one call, and you already know the query you want.
Watch out
it assumes you read the Pipefy API; start with the ready-made modules and come here only when they fall short.
Pipefy7

Get a Card Info

Action

In Make“Gets card details.”

Hand it a card and it returns the full details, so the rest of the scenario works with complete information instead of the thin slice a trigger or another app provided.

When to use it
a card ID arrives from an email or a sheet and you need its fields before sending a summary.
Watch out
it reads one known card; to find cards you do not have yet, use List Cards.
Pipefy8

Get a Table Record

Action

In Make“Gets a table record.”

One table record, fetched in full: the module pulls a record so its values can feed an email, a card update or a document later in the flow.

When to use it
a card links to a supplier record and you need that supplier's details to prepare an order.
Watch out
it needs the record itself; if you only know a name, search with List Table Records first.
Pipefy9

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

The safety net for everything else: this module calls any endpoint of the Pipefy API with the same connection, so a missing module rarely blocks a project.

When to use it
the action you need exists in the Pipefy API but none of the listed modules performs it.
Watch out
you describe the request yourself, so keep the Pipefy API documentation open while you set it up.
Pipefy10

Move a Card to Phase

Action

In Make“Moves a card to another phase.”

Cards advance without someone dragging them: the action shifts a card into another phase of its pipe, which is how an outside event can push your process forward.

When to use it
a signed contract or a paid invoice elsewhere should move the matching card to the next step.
Watch out
a move can also start Watch Moved Cards, so do not combine both in a flow that could move the card back.
Pipefy11

Update a Card

Action

In Make“Updates a card.”

Change several things about a card in one step, keeping Pipefy in line with what happens in your other tools rather than relying on someone to remember.

When to use it
a client updates their request in another app and the card should reflect the new details.
Watch out
for a single field value, Update a Card Field is the more direct choice.
Pipefy12

Update a Card Field

Action

In Make“Updates a card field.”

Precise edits: this module writes a new value into one field of a card, perfect when an outside event settles a single answer such as an approval or a tracking code.

When to use it
a payment tool confirms a charge and the card's payment field should say so.
Watch out
the edit is itself a field change and can wake Watch Card Field Update, so keep that trigger out of the same scenario.
Pipefy13

Update a Table Record

Action

In Make“Updates a table record.”

Records stay current: the action rewrites the values of an existing table record so the people using Pipefy see the same data as the source system.

When to use it
a client changes their address in your CRM and the Pipefy client table must follow.
Watch out
it edits a record you already located, so place Get a Table Record or List Table Records before it.
Pipefy14

Get a Phase

Search

In Make“Returns phase details.”

This search returns the details of a phase, which helps a scenario understand where things stand in a pipe before it decides what to do next.

When to use it
you want to check a phase before moving a card into it or before building a status report.
Watch out
as a search, it can return zero, one or several bundles, so plan for the empty case.
Pipefy15

List Cards

Search

In Make“Lists cards”

Pull a set of cards out of Pipefy at once, then let the next modules handle them one by one, for a digest, an export or a bulk update.

When to use it
a scheduled scenario compiles open requests into a sheet that the managers review.
Watch out
each card is a separate bundle and every later module spends one operation per bundle.
Pipefy16

List Table Records

Search

In Make“Lists table records.”

Retrieve the records of a Pipefy table in one go, handy for checking whether an entry exists before creating it or for syncing a table to another tool.

When to use it
before Create a Table Record, to skip suppliers or clients that are already listed.
Watch out
it can return nothing at all; plan what the scenario should do when no bundle comes back.
Need help

Need help automating Pipefy with Make?

A person reads every message.

FAQ

Pipefy and Make: frequent questions

01Is the Pipefy Make integration free?
Yes, on the Make side. Pipefy is a standard app, so it works from the Free plan, which allows 2 active scenarios, a minimum 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, drop the interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one per module run on one bundle. Your Pipefy subscription is a separate matter handled on the Pipefy side.
02What do you need to connect Pipefy to Make?
An active Pipefy account and a user with Super Admin permissions to create the credentials. In Company settings, under Service Accounts, that person generates a token with a name, a role and an expiration, then copies the Client ID and Client Secret. In Make, you paste both into the connection window and fill the Subdomain field only when your workspace runs on a custom domain. For the instant triggers, click Create a webhook first, then Create a connection.
03Do Pipefy triggers in Make fire instantly?
Yes. All 7 Pipefy triggers are instant: Pipefy calls Make through a webhook as soon as a card is created, moved, updated, completed, late, overdue or expired. Nothing waits for the default 15 minute schedule that polling triggers use. Your scenario still has to be switched on, and on the Free plan it counts as one of your 2 active scenarios. Test it with Run once and a real change in Pipefy before relying on it.
04What if a Pipefy module is missing in Make?
Use one of the two open modules. Make an API Call reaches any endpoint of the Pipefy API with the same connection, and Execute a GraphQL Query sends a query of your own, since Pipefy exposes GraphQL. Between them they cover most gaps left by the 23 listed modules. The Pipefy documentation on Make lists no numeric limit, so the practical constraints come from your Make plan: execution time, file size and operations.
05Should you use Make or n8n for Pipefy?
It depends on the modules you need. On Make, Pipefy comes with 23 modules: 7 instant triggers on cards, 13 actions and 3 searches, plus API and GraphQL modules for the rest. The same app may also have an n8n node, so compare the lists side by side for the actions your process relies on, such as moving cards or editing table records. Pick the tool where those actions exist ready-made, and where your team already builds its automations.
Same platform

Other docs you might need on this stack.

Browse all integrations