Tasks

With these steps an automation creates and updates tasks, so that a colleague picks something up. They are in the Tasks group. For how the outputs work, read Outputs of an action.

How does this fit together?Copy link to this section

A task created by an automation is an ordinary task: you find it on the tasks page, in the views it fits and on the customer or record it is linked to.

More about what colleagues see and do is in Tasks and Tasks with choice buttons.

Create taskCopy link to this section

Creates a task in the task system. The task is created in the name of Workflow.

Keep in mind:

• If you choose nobody under Assign to or Assign to groups and leave Also assign whoever caused the event off, the task has no assignee. Workflow is never assigned itself
• Subtasks get the title you enter, no assignee and no deadline. Empty lines are skipped. You may use variables in the lines
• Link to concerns customers, terrains, invoices, reservations and meters. For an occupancy that ends, the task is therefore linked to the terrain, the customer and the reservation by default. If you remove a record from the list, the task stays away from it. Records that join the flow later are not added automatically by Tillor once you have edited the list yourself. Choose everything again and the step follows all available records once more
• If a task is only on a personal board, only the people involved see it. See Private tasks

For later steps the action provides {createdTask.id} and {createdTask.name}. With those you can, for example, set the status afterwards.

If you do not want a second task when an open task already exists for the same terrain or customer, first add a Find task step and create the task only via Not found. The Holiday caravan check example does that.

If you switch on Only the flow can finish it, the task shows Finished by its automation. Colleagues cannot complete or delete it.

Delete taskCopy link to this section

Deletes a task, for example the task this flow created once it is no longer needed.

A task that is already gone is skipped. The flow then simply continues.

Set task statusCopy link to this section

Changes the status of an existing task, for example to complete it.

{task.id} works when the automation starts on a task event, such as task:created. After a Create task step, use {createdTask.id}. The action provides {updatedTask.id} and {updatedTask.status}.

Find taskCopy link to this section

Looks for an existing task by title. The step has two outputs: Found and Not found. That way you can update a task if it already exists, and otherwise create a new one.

If several tasks match, the step takes the newest. If Linked to the records of the event is on but the event has no customer, terrain, invoice, reservation or meter, the flow goes via Not found.

Via Found, later steps can use {foundTask.id}, {foundTask.name}, {foundTask.priority} and {foundTask.status}.

Set task priorityCopy link to this section

Changes the priority of an existing task.

The order is Low, Medium, High, Urgent. One step lower stops at Low. If nothing changes, the step simply succeeds without changing the task. The action provides {updatedTask.id} and {updatedTask.priority}.

Update taskCopy link to this section

Changes an existing task. Fields you leave empty stay as they are.

Keep in mind:

• If you choose Replace the current ones and specify nobody, the task has no assignee afterwards
• If the task no longer exists, the step fails
• The action provides {updatedTask.id}