Estimated reading time: 3 minutes

Save yourself hours of work by automatically routing tasks to your team members based on predefined rules.

You can rest easy knowing it’s effortless to define assignees to cards as soon as they are created.

Step 1

To begin, access the pipe where you want to create the automation and click on the Automations button, located in the pipe’s header. You can also

access Pipefy's automations in Settings, in the upper right corner of the screen.

👉 Remember: you have to be an admin user to set up this feature.

Then, click on Create new automation.

Step 2

Choose an event that triggers an action in this automation.

  • As an example, the event is When a card enters a phase.

After choosing the event, select the pipe and phase for this automation to run in.

While setting up an event, it's possible to add conditions and get more specific about this automation.

To add conditions, click Add condition, select the field and the scenario.

  • For example, imagine this automation criteria is a card's urgency, represented by a label. The automation condition will look like this:

Step 3

After choosing an event and its conditions, define an action.

  • Select Update a field's value.

  • Then, on Select field, choose the assignee field for this action.

  • Click Add assignee, then update it with one or more pipe members to execute cards in this specific phase.

Remember: Your card should contain an assignee field if you want to automatically assign pipe members.

In this example, the automation works like this:

  • Event: When a card enters the Approval phase of the Expense Reimbursement pipe

  • Condition: and, when its label is High priority

  • Action: the member assigned to execute this phase's cards is Steve Jobs.

Create automation according to your rules and ease manual work by assigning team members automatically!

🔔 Attention: Pipefy counts automations jobs whenever needs to check the conditions to trigger it or not the automation according to the scenario. The verification step is considered an automation job and therefore counted as such. For example, if you set up a rule where an automation moves a card to a specific phase, and if the card doesn't move because of conditions, then automation does not occur, but action to check it happened.

Learn how to make the most out of our platform with Pipefy University's free courses.

Join Pipefy's Community to ask questions, share ideas, give feedback about our product, and engage with other members.

Related articles:

Did this answer your question?