Estimated reading time: 5 minutes

If you use Pipefy for periodic activities such as:

  • Paying suppliers always on the 5th business day of the month

  • Billing customers 7 days after the invoice due date

  • Sending follow-up emails 3 days after a potential client's first contact

  • Any other process with actions based on a period of time from a specific date

You can set automations to ensure deadlines are met and update due dates (or any other important date) automatically.

  • Select an event to trigger your automation

  • As an action, choose the option to update a field

  • Select the field with the date

  • Click the plus sign button

  • In event attributes, set event date and time

  • Click on the calendar button and enter the relative date

📌 For this type of automation, the Pipefy robot counts calendar days, not just business days. This means that if you set the relative date to 7 days after the event, the action will take place in 7 calendar days.

Need more details? Check out the use cases below.

Automations to update payment due dates

Let's assume that in an accounts payable process every time an invoice is received payment should be made 7 days later.

In order not to miss this deadline, we created the following automation:

On your pipe's automations page, select the event when a card is created.

Now select the action update a field's value, and choose the due date of the bill.

Click on the plus sign button and in card attributes, select created at.

Then, click on the calendar icon to define your relative date. In this case, the payment deadline could be 7 days after the card's creation (payment request) in the pipe.

Now, every time you receive a payment request, the payment due date will be automatically updated 7 days after receiving the request.

Automations to collect feedback

In this other use case, let's assume that your HR team collects feedback from all new employees whenever they complete their first 90 days at the company.

Through automation, a due date field will be updated to ensure before the 90 passes you will schedule a meeting with the new employee. For this, you need to inform, in the start form, the date on which the 90 days will be completed.

On the automations page, select the event when a card is created. The action will update a field's value. In this session, select the field that records the date of admission.

The next step is to add the date relative to the event: click on the plus sign button and, in card attributes, select finished at.

Then, choose the relative date by clicking the calendar button. In this case, we use a customized date: 5 days before, so you will have the time to schedule the interview with the employee.

Automation to follow up with potential clients

Now, let's assume that your sales team must contact new customers 3 days after the first contact and this must happen in the follow-up stage.

On the automations page, select the option when a card enters a phase as an event. Select the phase that will trigger the action. In that case, follow up.

As an action, choose to update a field's value, and select the field with the first contact date.

Click on the plus sign button, and in card attributes, select created at.

Then, enter the relative date by clicking on the calendar button. In this example, we use a custom date: 3 days after.

From now on, every time a customer enters the follow-up phase, the date to complete this task will be automatically updated to 3 days after the first contact, which is the card creation date.

Automation for recurring activities

For tasks that always happen on the same date, that is, on the same hour every day, or on the same day of the month (always on the 1st day, for example), you won't set relative date automation, but recurrent activity automation.

📌 In this case, check out this tutorial about how to set automation to recurring activities.

Join Pipefy's Community to share ideas and give feedback about our product.

Learn how to make the most of our platform with Pipefy Academy’s free courses.

Related articles:

Did this answer your question?