Configuration and integrations for Process Automation

Every automation is configured to measure, but some decisions come up in almost every project. Knowing them helps you ask for changes clearly after handover.

Common integrations

Rules and exceptions

An automation is only reliable if it knows what to do when something is out of the ordinary. During configuration we define, for example:

• What happens if a required field is missing, such as the customer's tax number on an invoice.
• Whether certain situations should pause the automation and ask for human approval, such as amounts above a limit.
• Sending hours, so customers don't get messages in the middle of the night.
• How to avoid duplicates, for example never issuing two invoices for the same payment.

Monitoring and error alerts

Every automation we maintain is monitored. When a run fails, we get an alert and, if the error affects your operations, we let you know too. You can also choose to receive alerts directly, by email or WhatsApp.

A typical alert names the affected automation, the step that failed, the record involved (for example, the order number) and the error message from the tool. For critical processes such as invoicing, we can also set up a daily summary of successful runs, so you know the automation ran even when there are no errors.

Requesting changes

Small tweaks (an email wording, a recipient, a schedule) are usually covered by maintenance. Bigger changes, such as new integrations or extra steps, are quoted separately, always at a fixed price. See how to keep track day to day on the usage page.