Workflows allow you to trigger complex series of actions when collection items are Created, Updated or Deleted.
For example, you can send a goodbye email to a client when their account is Deleted.
Or you might want to update the client's owner when the client creates a Ticket
Each workflow starts with a trigger. A trigger has three properties
Useful for identifying your workflow
Which collection does this workflow run on, i.e. Users, Companies, or a custom collection
When this workflow runs, one of;
Created - when a new collection record is created
Updated - when an existing collection record is updated in any way
Deleted - when an existing collection record is deleted
A workflow can have as many actions as necessary. Actions run sequentially, i.e. one-after-another. This means you can use values from previous actions in your following actions.
There are three types of actions at the moment;
Send an email
Send an email to one (or many) email address(es).
An email action has the following fields:
To - The address to send the email to. If you want to send to multiple, separate them by commas
Subject- The email's subject
Message - The email's message. This can be as long as you want.
Call-To-Action Text - When provided, will render as a CTA button text
Call-To-Action URL - When provided, the link of the CTA button
Trigger a webhook (e.g. Zapier or Integromat)
Trigger an outgoing webhook, useful for triggering instant Zaps
For each item in a list...do...
This action on its own doesn't do anything, but it allows you to fetch a list related to the trigger item and loop over it. For example, sending an email to everyone in the company of the person who submits a ticket.
The below example shows off each action, using variables from the trigger and from previous steps