Building a workflow

A workflow is built on a canvas. You drag steps onto it and join them with lines, and the lines are the workflow: each one says "when this step finishes this way, do that next".

Every workflow starts with one trigger and runs from there.

Joining steps together

Most steps have a single outgoing connection. Some have several, one per outcome, and which one is used depends on what the step decided — a branch offers True and False, an approval offers Approved, Rejected and Timed Out, an API call offers Success and Error.

Leaving an outcome unconnected is allowed and means the workflow simply stops if it ends up there. That is worth checking before you publish: an unconnected Rejected outcome is a rejection nobody hears about.

Triggers

A trigger decides when a workflow starts. Each workflow has exactly one.

Event starts the workflow when something happens in WiseParts — a record reaching a status, a message arriving, and so on. This is the usual choice.

Schedule starts it on a timetable rather than in response to anything.

Manual starts it only when somebody runs it themselves, which is useful while you are still testing.

Webhook starts it when an outside system calls WiseParts.

Logic

Branch sends the run one way or the other depending on a condition you set.

Filter lets the run continue only if its condition holds, and stops it otherwise.

Merge brings separate paths back together so the steps after it are written once rather than repeated on each branch.

Waiting

These are the steps that make a workflow something an automation cannot be: it can stop, wait, and carry on later.

Delay waits for a set time before continuing.

Human approval puts the run in front of a person and waits for their decision, then continues down Approved, Rejected, or Timed Out if nobody answers in time.

Wait for event holds the run until something specific happens, then continues.

A waiting workflow is not a stuck one. It can sit for days and resume exactly where it left off.

Actions

Update field and Change status write to the record the workflow is running on.

Create task raises a task for someone to pick up.

Send notification tells someone that something happened.

Set variable stores a value for later steps to use.

Call API sends a request to a system outside WiseParts, and offers Success and Error so you can handle a failure rather than have the run stop.

AI steps

These use Henry AI, so they need Henry AI enabled and credits available.

Classify sorts what the workflow is handling into one of the categories you name, and gives each category its own outgoing connection, plus a Fallback for anything it cannot place.

Validate checks the content is complete and sound, and offers Valid and Failed.

Assess risk rates the situation Low, Medium or High, each with its own connection.

Enrich adds detail the record was missing.

Building one by describing it

Select Ask Henry in the builder and describe what you want in plain language — "notify the account manager when a return is rejected", or "add a human approval step before any status change".

Henry drafts it onto your canvas as a proposal. Review each one before keeping it: you can revert any change Henry makes, and nothing is published until you publish it.

You can also ask Henry what an existing workflow does, which is the quickest way back into something built months ago.

This needs Henry AI enabled for your account, with credits remaining.