Automations

Set up events that create tasks, spend warehouse stock, or reassign an order on their own — no manual work by the team.

Overview

Automations run pre-configured actions in response to an event in the project — no human involved. Open Settings → Automations in the project sidebar. Managing automations requires the Edit project permission.

Every automation has three parts:

• Event — what has to happen for the automation to fire.
• Condition — narrows the event to a specific case (for example, a specific order status). Some events have no condition at all.
• Actions — what to run once the condition is met. There can be several; they run in the order they were added.

The available actions and condition depend on the chosen event — some actions (warehouse ones, for example) only make sense where the event is actually tied to an order.

Creating an automation

Click Add on the automations page.

1. Enter a name — it only exists to tell automations apart in the list and in the order journal.
2. Pick an event.
3. Fill in the condition, if the event has one.
4. Click Add action and configure each action.

The Save button becomes available only once the condition and every required action parameter is filled in — Configo won't let you save an automation that could never fire.

Events

Order status changed

Fires when an order transitions into the status set in the Order status condition. Every action is available — both warehouse and task ones.

Task overdue

Fires once for each task whose due date has passed while its status is still Open — the same process that sends the overdue reminder. There's no condition: the event already points at one specific overdue task. If the task was created from an order or a contact, the automation sees that link and can inherit it (see Create task below).

It won't fire again for the same overdue task — only if the task falls overdue again after its due date gets moved.

On schedule

Fires on a timer rather than something happening in the project. The Frequency condition sets how often:

• Daily — every day.
• Weekly — on Mondays.
• Monthly — on the 1st of the month.

This event carries no order link, so warehouse actions and reassigning an order aren't available under it — only creating a task.

Actions

Spend from warehouse / Receive finished products

Spends the order's materials or finished products from the warehouse (or receives what was produced), computed from the calculator's bill of materials. Parameters:

• Source — materials or products.
• Warehouse — a specific project warehouse, or Default warehouse.

If the warehouse doesn't have enough stock, the action fails — and so does the order's transition into the new status: the order stays in its current status until there's enough stock.

Create task

Creates a task under Tasks. Parameters:

• Task title.
• Assignee — a specific project member, or Order assignee (the assignee becomes whoever is running the deal at the moment the automation fires). The second option isn't available under On schedule — there's no order there to pull it from.
• Due in, days — how many days from the moment of firing to set the task's due date. Can be left empty, in which case the task gets no due date.

If the event is tied to an order or a contact, the created task inherits that link and appears in its journal — the same as if it had been created by hand.

Change assignee

Assigns the order to a new responsible user — a project member chosen in the Member parameter. If that member is already the assignee, the action does nothing.

Run history

Click the clock icon next to an automation to open Run history. Every attempt — successful or not — lands in the list with a status (Success / Failed) and, on failure, the reason. That makes it quick to see why an automation didn't do what you expected — for example, that the chosen member no longer has access to the project.

Enabling and disabling

The toggle in the Active column temporarily disables an automation without deleting its configuration. The trash icon deletes an automation permanently.

Where this shows up elsewhere

• Actions that change the order (spending warehouse stock, reassigning it) leave an entry in its journal — tagged with the automation's name, so it reads apart from a manual edit.
• A task created by an automation is indistinguishable from one created by hand in Tasks, including due-soon and overdue reminders.