Operations

Automations that move the job on without you

Every module has a trigger: a record is created, or its status changes.

01

Chasing that depends on someone remembering

Before

Quotes go quiet, invoices go overdue and suppliers sit on purchase orders.

With Zigaflow

Automated messages live on the pre-build for each module: set the trigger status, the days to wait, the time of day and whether it recurs, and Zigaflow sends the branded email or SMS from your address.

02

Handoffs that are retyped

Before

The quote is accepted, so someone creates the job. The job reaches Ready for Production, so someone creates the works order.

With Zigaflow

An automation on the quotation module creates the job, in the status and pre-build you choose, when the quote moves to Accepted.

03

Systems that do not talk to each other

Before

Your production board, courier system or customer portal needs to know when a Zigaflow order changes, and today that means someone copying it across.

With Zigaflow

Add a webhook action to a quotation or job automation and Zigaflow posts to the target URL on the trigger, with a free-text type you can use to route the call on the other side.

What you get

  • Triggers on status change or on creation, with an optional delay and Allow Repeat
  • Conditions on tags, customer, order value, sibling PO status and more, combined with And and Or
  • Actions: create a job, works order or ticket, move a related record, add or remove a tag, change the assigned user
  • Export invoices to Xero or QuickBooks automatically when they reach a status
  • Webhook action from quotations and jobs to call another system
  • Automated emails and SMS on a schedule: follow up a quote, chase a payment, chase a supplier, escalate a non-response
  • Messages stop by themselves when the record moves to another status
  • One automation log across every module, filterable by module and record

How it works

  1. Pick the module and triggerCog, Automations, then the module.
  2. Set the conditionsEdit the default condition to the status that should fire the automation.
  3. Choose the actionsSelect an action: Create Job with a status and pre-build, Create Works Order for tagged items, Export to Xero or QuickBooks, Change Related Job's Status, add a tag, call a webhook.
  4. Add automated messages on the pre-buildOn the module's pre-build, open Automated Messages and create one: trigger status or date, days to wait, time to send, recurrence, and recipients using variables such as {ClientContactEmail}.
  5. Watch the logOpen the Automation Log to see every run across modules.
What are Zigaflow automations?

An automation is a rule attached to a module: when a quotation, job, purchase order, invoice or other record is created or changes status, and the conditions you set are met, Zigaflow performs one or more actions. Conditions can test the new status, tags on the record or its customer, the record's value or the status of related records such as every purchase order raised from a job. Actions vary by module and include creating a job from an accepted quote, creating a works order for tagged line items, creating a ticket, moving a related job when all its POs are received, adding or removing a tag, changing the assigned user, changing a customer's status, updating the tax codes on a quote, exporting an invoice to Xero or QuickBooks, splitting an order into fulfilled and backordered parts, de-allocating stock, and calling a webhook. Each automation can be delayed, allowed to repeat, and saved inactive while you build it. Every run is recorded in the automation log.

Automated messages are the second half. They live on a module's pre-build and send an email or SMS when a record reaches a status, or a set number of days after it, at a chosen time, optionally recurring until the status changes. Variables such as {ClientContactEmail}, {SupplierContactEmail} and {ReviewLink} address and personalize them, and they can be filtered by tag or business type so different customers receive different chasers.

The workflow library describes end-to-end scenarios built from these pieces, from quote to invoice. This page describes the mechanism. Both start from the same idea: the status a record is in should be enough to make the next thing happen.

Frequently asked

Ready to get started? Try it free.

14-day free trial on all plans. No credit card required.

Start free trialBook a demo