Workflows & automation

Automate the busywork. Keep the judgment calls for your team.

A visual automation engine with 30+ modules, a persisted runtime that survives restarts, and deep integration with every part of Sysflows: tickets, cases, forms, lists, approvals, and your external tools.

Start free See pricing

Visual workflow designer

Draw the logic, not the code.

The workflow designer is a node canvas: drag modules from a palette, connect them, and configure each one with a property panel. Every field and event token is listed and auto-resolved, so you don't need to remember field IDs. A run viewer shows every execution in real time: each step's inputs, outputs, and any errors.

  • Node canvas with a searchable module palette
  • Property panels with auto-resolved field tokens
  • Run viewer with per-step inputs and outputs
  • Trigger catalog scoped to ticket type, channel, or case event
  • Manually runnable from any ticket for testing and one-offs
See the full feature set →

Workflow designer

  • Ticket created Type: Billing Trigger
  • Priority = Urgent branch If
  • Request approval Manager Approval
  • Send confirmation Customer Reply

Persisted runtime

Automations that wait as long as they need to.

Most workflow engines run and forget. Sysflows workflows are persisted to the database and can pause mid-run, waiting for a timer to fire, an external event to arrive, or an approval to come back. Restart the server and the run picks up exactly where it left off.

  • Pause and resume across server restarts
  • Wait-for-event module holds a run until a specific ticket event fires
  • Timers: delay for N minutes, hours, or days, or until a calendar date
  • Approval steps gate the next action until a decision is made
  • Run-ceiling loop protection to prevent runaway automations

Run viewer, paused

Trigger matched ON
HTTP lookup · 200 OK ON
Wait-for-event · ticket.replied OFF
Send Slack · #billing-alerts OFF

30+ modules. One engine.

Mix and match modules to build any automation, from a simple auto-reply to a multi-step approval chain that calls an external API and writes back to a data table.

Flow control

Branch with If and Switch on any field or expression. Loop over a list with For-each. Pause a run with Wait-for-event until a specific ticket or case event fires.

Data modules

Make outbound HTTP calls to any REST API. Query an internal SQL view. Lookup records from a List or contact. Set variable to carry values across steps.

Ticket actions

Create, update, comment, or reply on tickets. Link related tickets. Split one ticket into two. Merge duplicates. Request an approval as a workflow step.

Cases, forms & lists

Create or update a case. Submit or read a form. Read or write a row in a list table. All three share the same field-token system, so values flow between modules without mapping code.

Approvals as workflow steps

Drop an Approval module anywhere in the flow to pause until a person, team, or role responds. Set any-one, unanimous, or quorum policies. The run gates on the result: approved continues, rejected branches.

AI action module

Call the AI mid-workflow: classify content, summarise a thread, draft a reply, or extract structured data from free text. The result becomes a variable you can branch on or write back to a field.

External connectors

Send messages to Slack, Microsoft Teams, and Discord, and read or write files in OneDrive and SharePoint, from any workflow step. Connect once in Settings; pick the connector per workflow node. OAuth, API-key, and webhook-URL auth all supported.

DocuSign e-signature

Send a document for signature straight from a workflow step, then wait: a DocuSign completion trigger resumes the run the moment it's signed, so the next action (update the case, notify the team, file the signed copy) happens automatically. No manual chasing, no polling.

Timers & scheduled runs

Delay a run for a fixed period or until a calculated future date. Use timers for follow-up reminders, SLA-approach nudges, or any time-sensitive step that should happen later rather than immediately.

Trigger on any event, including channel intake.

Workflows start from a scoped trigger: a ticket event, a form submission, a case update, or an API call.

Ticket events

Created, updated, replied, status-changed, assigned, approved, breached: trigger a workflow the moment any ticket event fires. Scope to a specific type so only the relevant tickets run it.

Form submissions

Every form submission can trigger a workflow immediately. Route the submission, create linked records, notify a team, or kick off a multi-step onboarding process, all without code.

Case events

Trigger on case-created, stage-changed, or a party update. Use case-event workflows to automate the steps that happen every time a matter reaches a new stage in your pipeline.

Manual & API-triggered

Run a workflow by hand from any ticket, useful for one-off actions or testing. Or trigger via the API to drive automations from your own systems and scheduled jobs.

Automate the repeatable. Focus on the work that matters.

Start free See pricing

No credit card. 14-day full trial.