Automations

Automations are used to perform common tasks on a regular basis. There are two types of automations: time-based automations and trigger-based automations.

Time Automations

Time automations perform tasks on a pre-determined schedule rather than being triggered by an event.

Fields

• Starting On
  • Date: this is the date the automation will run for the first time.
• And Repeating Every
  • #: the number of the frequency that must elapse before the automation runs again
  • Frequency: the type of frequency that must elapse before the automation runs again
  • For example, entering "3" as the # and selecting "days" as the frequency will cause the automation to run every 3 days
• And Stopping
  • Never: the automation will run without an end date
  • After
    • #: the number of times the automation will run before terminating forever

Actions

Actions are what occur as a result of the automation. Time automations support the following actions:

• Create AR invoice with billable time: outstanding billable time will be added to an AR invoice for each relevant client
• Import Asana time: billable time will be imported from your Asana integration
• Import ClickUp time: billable time will be imported from your ClickUp integration
• Import Monday time: billable time will be imported from your Monday integration

Trigger Automations

Trigger automations perform task after some event occurs inside of your organization.

Triggers

Trigger automations support the following triggers:

• AR invoice is approved: the automation will run when your organization approves an AR invoice
• AR invoice is overdue: the automation will run when the due date for an AR invoice elapses without full client payment
• AR invoice is paid: the automation will run when a client makes a payment against an AR invoice
• Client is created: the automation will run when your organization creates a client
• Client/vendor registers: the automation will run when a client or vendor accepts an invite to your organization's portal
• Expense is approved: the automation will run when your organization approves an expense
• Product reaches reorder threshold: the automation will run when a product's on-hand inventory reaches its reorder threshold
• Quote is approved: the automation will run when a client approves a quote
• User registers: the automation will run when a user accepts an invite into your organization
• Vendor is created: the automation will run when your organization creates a vendor

Conditions

Conditions control if the automation will run when the trigger activates it. For example, you may have an automation fo when an "AR invoice is overdue" but only want the automation to run for specific clients, so you configure this with conditions.

The conditions available differs per trigger.

Actions

Actions are what occur as a result of the automation. The actions available differ per trigger.