What can an automation do? (Actions)

An action is the actual work the process does: creating a project or task, assigning a user, sending a notification, creating an invoice draft, requesting approval, calling a webhook, or escalating. An automation can hold several actions, one after another or on separate branches.

Drag an Action block onto the canvas, click it, and in the panel on the right choose what it should do in the Action Type field. Each type has its own settings:

• Create project – fill in Project name. You can include data from the event in the name.
• Create project from template – pick the template in Project template.
• Create task – fill in Task name and choose in Project which project it belongs to.
• Assign user – adds the colleague chosen in Assign to to the project, task or opportunity the event is about.
• Send notification – enter the Message and the Recipients. Only users of your company can be notified.
• Create invoice draft – creates an invoice draft for the customer the event is about, which you review and issue later.
• Request approval – starts an approval request for the item the event is about.
• Send webhook – notifies an external system by sending the event's data to the Webhook URL you enter.
• Escalate – raises the pending approval to the next level, and the user chosen in Escalate to gets a notification with the Message text.

Several steps: chain actions with arrows, or put them on separate branches after a Condition. A Delay block adds time between two steps – for example, an escalation 7 days after a notification.

Trying it out: the editor's Test Run button shows on the canvas which steps would run – it does not actually create or send anything. The test runs what is on the canvas, saved or not, so you can check a change to an active automation before it goes live.