⏩ Content Summary:

Every time an event happens in your process, it will trigger an automation action.

Example: every time a card enters a phase → send an email template to an assignee (automation action).

You can trigger the following automations:

As you create an email template, you can automatically send it from a card whenever a field is updated, if it's moved to another phase, or when an alert is triggered (among other options).

Automating email templates helps you streamline your communication with stakeholders or team members. All without the need to handle many email inboxes or to write the same thing multiple times.

👉 Example: Every time a ticket is solved in a Customer Support helpdesk, an email confirming the resolution is submitted to the customer who requested support.

Automatically move a card to a phase depending on previous events.

This automation is great for eliminating manual work, such as checking if the fields in the card are updated before moving it to another phase. And it streamlines the information flow, such as approvals, screenings, etc.

👉 Example: in a Sales CRM process, if a lead is marked as qualified, it will move from phase Prospect to Discovery.

Update fields on cards or database records automatically with the exact information you want. For example, whenever a card is moved to phase X, update the assignee field of the same phase with a specific team member.

Another possibility is to update a database record according to the actions that happen on the card or in the phase. For example, if a lead becomes a customer in a Sales Funnel process, the information in the database is automatically updated.

🔎 Learn how to set automations to update cards and records.

Such automations are valuable for processes with well-defined business rules, such as approval flows, that require constant updates.

👉 Example: in a Customer Onboarding process, every time a customer (card) is ready for implementation (phase), update the field assignee with Nex Nix.

This automation works similarly. In this case, there must be an active connection between the cards and databases.

This way, it's possible to create a card connected to another card in different pipes. Or between a pipe and a connected database.

👉 Example: in a Purchase Process, every time a purchase order is paid (moved to the Paid phase), create a record in the Expenses database.

Match the fields from a pipe to fields from another pipe (or from a database record) and update them simultaneously.

This way, whenever a field is updated in a card, another card or record will be created with the same intakes.

It's especially useful for teams updating the same information across multiple processes. It cuts out the manual work and avoids duplicated data.

👉 Example: use fields from a Recruitment Process to create employee records and automatically update information in both.

A parent card contains other cards connected to it (called the child cards). In this automation, every time a child card moves to a phase (either in the same pipe or another pipe), the parent card also moves.

It's great for teams that work with the same information across different processes.

👉 Example: cards in Purchase Process and Expense Reimbursement pipes are connected. They share the same information: product's cost and payment information.

A parent card in the Expense pipe represents an expense, and it shares the same information with a card in the Purchase pipe.

Every time a card with the purchase order is paid (moved to phase Done), it becomes an expense ready for approval (the parent card is moved to the Approval phase).

Easily integrate Pipefy with other tools without exiting the platform.

🔎 Learn how to make an HTTP request through Pipefy

With an HTTP request, you just need to select the trigger and then select the HTTP request to start communicating with another system.

👉 Example: Every time the Finance team needs to approve a request, send a message through Slack. Or when a new collaborator finishes onboarding in the HR process, give them access to different software.

➡️ Request access to HTTP feature

Evenly or randomly distribute the demands from your process to your team members. For example, always that a card is created, assign the card to a different person from your team, following a rotating sequence (also known as Round Robin distribution). You can choose among all pipe members which ones will participate in the rotation and the distribution strategy.

It is especially useful for pipes with a high volume of cards, with 2 or more people working on those cards, assuring the best efficiency possible for your process.

👉Example: on an IT tickets pipe, always that a new ticket gets on the Backlog phase, distribute them evenly among the IT analysts available by filling in the Responsible for this ticket field.

You can use formula automations to make calculations in a simple and objective way in your processes.

➡️ Request access to formula feature

You can apply the following functions:

🔎 Get to know all numeric features in Pipefy

👉 Example: In a Purchasing Process, subtract the value negotiated from the total foreseen spent and update the Discouts field automatically.

Create advanced SLA rules to gain more visibility into your team's efficiency and greater reliability on operation data.

With this automation, you can:

You can apply this rule every time a card is created, for example. This way, the resolution time for requests will only consider working days and hours, excluding holidays, and adjusting to each time zone.

👉 Example: In a procurement process, where many people and teams with different working hours and locations may be involved, apply SLA rules so that everyone has visibility of deadlines realistically and adapted to each individual's reality.

🔎 Learn more about advanced SLA rules

Related Content: