← All products
Synapsi / Product / Custom builds

Fit the operationyou already run.

Start from a template or map your own process: what triggers it, which systems it touches, and where a person must decide. Custom work is scoped with you around your systems and approval boundaries.

See it work Open workspace
Workflow canvas · draftnot published
Using a template creates a draft. Publishing is a separate step.
How it works
01

40+ templates to start from

Welcome sequences, payment reminders, complaint clocks, switch-out retention. Using one creates a draft; publishing is a separate, deliberate step.

02

Eight building blocks

Start, condition, parallel, action, join, for-each, delay and end. Triggers are a webhook from your system, a schedule, or an event in a connected app.

03

Watch every run

A live canvas shows each step green, red or grey with the reason for any failure. Failed steps retry with a growing wait before they are set aside.

Template families

Built around the clocks energy supply runs on.

Several templates carry a regulatory deadline inside them, so the timing is part of the workflow instead of somebody's calendar.

Conversations and inbox
wf-020-whatsapp-inboundwf-029-email-inboundwf-023-capture-and-answerwf-030-triage-inboundwf-037-inbound-email-draft-for-reviewwf-039-email-answered-by-agent
Billing and payments
wf-022-payment-reminderswf-032-failed-payment-follow-upwf-047-returned-receipt-recoverywf-048-regularisation-explainedwf-056-first-real-bill-periodswf-035-tariff-change-notice
Switching and contracts
wf-051-distance-contract-confirmationwf-042-contract-signed-messageswf-043-switch-completed-messageswf-044-switch-failed-messagewf-046-switch-out-retentionwf-049-atr-rejection-recoverywf-055-winback-after-switch-out
Service, field and care
wf-033-engineer-visit-bookingwf-024-appointment-reminderwf-054-gas-inspection-duewf-027-outage-broadcastwf-053-complaint-answer-clockwf-050-bono-social-expiry-noticewf-052-change-of-holder-missing-data
From process to production · against the clock

A supplier needs a bespoke exception workflow.

First

Map

Name the trigger, the data each step needs, and the points where a person must decide.

recorded
Then

Build the draft

Start from the closest template, add a condition and a delay, and name the capabilities each step needs.

recorded
Before go-live

Validate

Run it as a draft and watch the canvas: green where it worked, red with the reason where it did not.

denied
Go-live

Publish

Publishing is its own decision. From then on every run is recorded, and every definition is versioned.

approved

Custom integrations and deployment scope are agreed individually; no unsupported connector is implied.

Where it sits

Each layer adds to the one beneath.

Layer 05 of 06

Workflows adds when it all runs.

A trigger from your system, a schedule or an app event starts the work, step by step, with every run recorded.

It stands on the 4 layers beneath it.

Built to be trusted

Safe by default, provable afterwards.

Refused unless you allow it

Every action an agent can take needs a setting from you. With no setting, the answer is no.

A person approves what matters

Anything you mark as sensitive stops and waits. One press approves it, and the record shows who pressed.

A log nobody can edit

Each action is written to an append-only audit log in the same step as the action itself, refusals included.

Triggers are signed

Requests from your systems are signed and verified before a workflow starts, and bursts beyond the ceiling are held.

Roles for your team

Viewer, operator and owner. People sign in with the Google or Microsoft account they already have.

Your figures stay your figures

No model rewrites a price or an invoice amount. Numbers are sent exactly as your system produced them.

Clear boundaries

What it does, and what it will not.

It does
  • Starts from a template or a blank canvas
  • Calls your own system with a generic HTTP step where no connector exists
  • Keeps a version of every published workflow definition
It does not
  • Publish a draft by itself
  • Start unlimited runs from one trigger: bursts past the ceiling are held
  • Promise a connector that has not been built and tested with you

Bring the process. We will fit the platform to it.

Tell us what you run today and where the approvals sit.

Open workspaceTalk to the team