Time-based automations

This is a type of automation that runs periodically based on elapsed time (cron). It uses 3 key elements for configuration.

1. Event (trigger)

Defines the time since an action:
  • Days since creation (form or task)
  • Days since last edit (form or task)
  • Days since available (tasks only)

2. Object with status filters

Select the form or task to automate and define the statuses in which it should apply.

3. Associated attribute

The object must include an attribute representing the defined time (for example: Timer X days). This is the label that associates that object type with scheduled automations.
Once these three elements are configured, you can create automations according to the available options for each object type.
Note: Need a different combination? Write to us at  implementacion@sytex.io 


Automation examples

For tasks

  • Event: X days since available
  • Statuses: Open, In Progress, or On Hold
  • Required attribute: Timer X days (TA available)
An example:
A task can be automatically completed 30 days after creation.
For this to work, the task must be based on a template that contains the associated attribute.

For forms

  • Event: X days since last edit
  • Statuses: Open, In Progress, or In Review
  • Required attribute: Timer X days (FO last edit)
An example:
A form can be cancelled 21 days after creation.
For this to work, the form template must have a pre-configured associated attribute.


Wait for completion

Simply wait for the configured time to elapse and the process will run.