Overview
Everything an automation can do, with all fields per action
Last updated on
Actions are the steps that really do something. You find them in the step list in the groups Tasks, Documents, Guests and messages, Invoices and payments, Access and devices and Integrations. The steps in the Logic group steer the flow itself. Those are described under Conditions, switches and delays. All actions are executed by your organisation's Workflow user.
| Group | Action | What it does |
|---|---|---|
| Tasks | Create task | Creates a task, optionally with subtasks, on a board and linked to a customer, terrain or invoice |
| Tasks | Set task status | Changes the status of an existing task |
| Tasks | Find task | Finds a task by title and continues via Found or Not found |
| Tasks | Set task priority | Raises, lowers or chooses the priority of an existing task |
| Tasks | Update task | Renames a task, adds people or labels or moves the deadline |
| Tasks | Delete task | Deletes a task, for example the task this flow created |
| Documents | Find document | Finds a customer's newest document and continues via Found or Not found |
| Documents | Update document | Changes the type of a document, or archives or restores it |
| Guests and messages | Message a guest | Sends your own text to a customer by email, text message or WhatsApp |
| Guests and messages | Notify colleagues | Sends colleagues a push notification or email |
| Guests and messages | Add a comment | Places a comment on the event's records or on a task |
| Guests and messages | Reply in the inbox | Sends a reply in an inbox conversation |
| Guests and messages | Tag or archive conversation | Adds tags to an inbox conversation or archives it |
| Guests and messages | Update customer | Changes the status of a customer or adds a note |
| Guests and messages | Check in, check out or cancel | Puts a reservation into its next status |
| Invoices and payments | Send payment reminder | Sends the payment reminder of an invoice to the customer |
| Invoices and payments | Sync bank transactions | Fetches new bank transactions before the flow continues |
| Invoices and payments | Disable automated reminders for customer | Skips all of a customer's invoices in automated reminders |
| Invoices and payments | Disable automated reminders for invoice | Takes one invoice out of automated reminder flows |
| Invoices and payments | Send invoice | Sends an invoice to the customer |
| Invoices and payments | Book invoice | Books a draft invoice |
| Invoices and payments | Print invoice | Prints an invoice or shows it on a tablet |
| Invoices and payments | Create payment link | Creates an online payment link for what is still outstanding |
| Invoices and payments | Request SEPA mandate | Asks a customer to sign a mandate, or sends a reminder |
| Invoices and payments | Collect by direct debit | Collects what is outstanding with the customer's active mandate |
| Invoices and payments | Invoice consumption | Invoices a customer's outstanding meter consumption |
| Invoices and payments | Draft extension invoice | Creates a draft invoice that extends an occupation |
| Access and devices | Create access method | Gives a customer access via QR code, licence plate, PIN code or NFC |
| Access and devices | Update access | Blocks, unblocks or extends access methods |
| Access and devices | Send or print QR code | Sends a QR access code to the customer or prints it |
| Access and devices | Open or close barrier | Opens or closes a barrier or gate |
| Access and devices | Switch power | Turns the power of a smart meter on or off |
| Access and devices | Update NFC tags | Blocks, unblocks or tops up a customer's NFC tags |
| Access and devices | Control tablet or kiosk | Wakes a tablet or kiosk, puts it to sleep or reloads it |
| Access and devices | Set slideshow | Puts photos on tablets and kiosks, from a list or an earlier request |
| Integrations | Send webhook | Delivers a message of your own to one of your webhook endpoints |
| Integrations | API request | Calls the Tillor API or another website |
In all text fields you can use variables, such as {invoice.displayId}. At the top right of each field is a Variable button to insert one. Fields that ask for a customer, invoice or other record expect the internal id of that record, such as {invoice.id}. An invoice number or name therefore does not work.
Exits of an action
Under a step there are one or more exits. You connect each exit to a next step. If you leave an exit unconnected, the run ends there.
| Exit | On which actions | When |
|---|---|---|
| Next | Most actions | The step succeeded |
| Done and Skipped | Actions that sometimes have nothing to do | Done if the step did its work. Skipped if there was nothing to do, for example because the invoice was already booked. That is not an error |
| Found and Not found | Find task | Whether the task exists |
| Found and Not found | Find document | Whether the customer has such a document |
| Succeeded and Failed | Send webhook and API request | Whether the other side accepted the message |
Done and Skipped are on Message a guest, Check in, check out or cancel, Book invoice, Create payment link, Request SEPA mandate, Collect by direct debit and Invoice consumption. For each of them, it says under the action when a step is skipped.
Continue when this step fails
If an action goes wrong, the run normally stops with the status Failed. If you want to decide yourself what happens then, turn on Continue when this step fails at the bottom of the step's settings. That is possible for every action except Send webhook and API request, which already have an exit of their own, Failed.
The step then gets an extra exit Error. If the action fails, the flow continues via Error instead of stopping. Later steps can use these variables:
| Variable | Content |
|---|---|
{error.message} | The error message. It may be in English |
{error.step} | The name of the step that failed, as you filled it in under Step name |
A few things to know:
- If the action succeeded or was skipped, nothing changes and Error is not used
- If you leave Error unconnected, the run ends there without further steps. The run then gets the status Completed, but the step itself shows its error message on the Runs tab
- A second failed step in the same flow replaces
{error.message}and{error.step}of the first
An example: let Message a guest continue if it fails and create a task via Error with {error.message} in the description. That way a colleague picks up the conversation with the guest themselves.
When a step fails
There are three ways a failure can go.
- A Failed exit. This happens with Send webhook and API request if the other side returns an error. The flow continues via the Failed exit. Connect it to a follow-up, such as a task for a colleague. If you leave the exit unconnected, the run simply ends there
- An Error exit. If you turn on Continue when this step fails on another action, the step gets an Error exit and you can use the reason with
{error.message}. See Continue when this step fails - The step stops the run. If a value is missing after the variables have been filled in, an invoice cannot be sent, an endpoint no longer exists or the JSON is invalid, the run gets the status Failed. The steps after it are not executed and Tillor does not retry the step. This only happens if you have not turned on Continue when this step fails
The error message is on the step on the Runs tab. Those messages may be in English.
Do not miss failures
Want to make sure a failure never goes unnoticed? Connect the Failed exit of an API request or Send webhook, or the Error exit of another action, to a Create task step. That way a colleague can pick it up.