What is automation?

Automation helps you automatically trigger an action when a specific event happens. 

Automated actions work according to an 'event > action' logic: when a pre-determined event X happens, a pre-determined action Y will occur automatically. 

What is an event?

An event is something that happens on Pipefy to trigger the automation action. Example: Every time a card is done on your Sales Pipeline. 

In this case, the event is “when a card is moved" to phase done.

What is an action?

The action is what happens after the automation is triggered.
Example: Every time a card is done on your Sales Pipeline, a new card is created in the accounts receivable pipe. 

In this case, the action is “create a new card”.

What events are available?

  • When a card is created: Triggers the automation when a new card is created in a specific pipe;
  • When a card is moved: Triggers the automation when a card is moved to a specific phase of a specific pipe;
  • When a field is updated: Triggers the automation when a field is filled or the value in it is modified;
  • When all connected cards are moved to a phase: Triggers the automation when all connected cards are moved to a specific phase (this event demands that you create a connection between pipes before setting it up);
  • Recurring activity*: Triggers the automation every hour, every day, every week or every month (at defined times/days);
  • When an alert is triggered: Triggers the automation whenever a card becomes late, expired or overdue in a specific pipe;
  • When an email is received: Triggers the automation once a card receives an email;

*. When setting up a recurring activity, the time you choose is UTC, which means that if you want cards to be created everyday 7AM your time, you need to check your time zone and add/subtract the difference from UTC.

What actions are available? 

  • Create a new card in a pipe: A new card will be created in a specific pipe with the information you set up corresponding the fields;
  • Create a new connected card: A new connected card will be created in a specific pipe with the information you set up corresponding the fields (this action demands that you create a connection between pipes before setting it up);
  • Move the parent card: The parent card will be automatically moved to a specific phase (this action demands that you create a connection between pipes before setting it up);
  • Update a field's value: The value in a specific field will be automatically filled/updated (this action only allows users to update fields that belong to the same pipe as the event);
  • Move card: A card will be moved to a specific phase in the same pipe where the action happened.

Related articles

Advanced uses of automations

Did this answer your question?