Using Content Variables in Automated Workflows

Starting with the November 2024 Edition of Pagico, content variables can be used in workflows to generate more informative content. For more information on Automated Workflows, click here.

You can pass some of the content from the previous object into the action. For example, if a task triggered a workflow that will send out an email, you can include details of the task in the email content using the Content Variable feature (this feature was introduced in the November 2024 Edition of Pagico). 

The syntax to use content variables is: {{FieldName}}.

The supported field names vary based on the type of upstream object, and the field names are case sensitive. This means that {{Title}} would be replaced by the title field of the upstream data object, but {{title}} would not.

Lists

• Title
  This is the title of the list.

Tasks (List Items)

• Title
  This is the title of the task or list item.
• Desc
  This is the description of the task or list item.
• Location
  This is the location of the task or list item.
• StartDate
  This is the timestamp of the start date of the task or list item.
• DueDate
  This is the timestamp of the due date of the task or list item
• CompletionDate
  This is the timestamp of the completion date of the task or list item. Note that this field may only be valid after the task or list item is checked off.

Notes

• Title
  This is the title of the note.
• Body
  This is the content of the note body.
• Timestamp
  This is the timestamp of the note object.

Files

• Title
  This is the file name of the file object.
• Description
  This is the description of the file object.

Projects

• Title
  This is the title of the project.
• Description
  This is the description of the project.
• Tags
  This is the tags of the project.

Contacts

• Name
  This is the full name of the contact
• Tags
  This is the tags field of the contact.

Date Adjustments

Adjusting Timestamps

For timestamp variables, you can perform simple adjustments to create new timestamps using this syntax: {{Keyword +/-Adjustments}}. For example, in a workflow action, if you wish to create a new task that is due 5 days after the upstream task due date, use this in the Due Date field of the New-Task action:

{{DueDate +5 days}}

Here's another example of date adjustment that creates a new timestamp that's 2 weeks after the Completion Date of the upstream task.

Using Timestamp Variables as Text

Alternatively, the timestamp variables can also be used in text fields. For example, you can have an workflow action that writes a new email with a subject line of:

Task Completed: {{Title}}, {{DueDate}}

In this case, the DueDate timestamp will be rendered in text (e.g. Monday, December 2 2024). The timestamp adjustments can also be used in text fields.

Things You Should Know

• Workflows are synced across your devices! So if you created workflows on your primary Mac, then you don't need to do the same thing on your second computer.
• Workflows are triggered locally, right on your computer. This means all the programmed actions will take place as soon as the workflows are triggered. This also means that if Pagico is not running, the workflows are not triggered even if changes are made via your mobile device or via other cloud-based APIs.
• To prevent the runaway situation where workflows are repeatedly triggered by changes made by the same workflow (an infinite loop situation), each data object could only trigger each workflow only once. 
• How did your workflows run? You can check the execution results in the Notification panel, or by going to the Workflow Editor, which shows you 5 recent executions of each workflow and their recent errors (if any).
• The Send Email action is rate limited to 24 per day at the moment. This limit may increase in the near future as the system and service stabilizes.
• At the moment, the Automated Workflow feature is in BETA. If you see strange behaviors or run into issues, please don't hesitate and let us know by sending emails to [e-mail].