When a reply isn’t enough, move the work forward.

A refund to approve, access to authorise, a case involving several departments. Map the process and track tasks, ownership and progress directly in Uppo.

  • Core nodes included in every plan
  • Advanced nodes with the Enterprise plan
  • Every step stays linked to the ticket that started it
When a reply isn’t enough, move the work forward.

Examples

The processes support handles every day

A refund to approve, access to authorize, a case involving several departments: each follows a traceable process.

Workflow builder

The building blocks of your process

Combine tasks, decisions, waits and connections to business systems. Before publication, Flow validates the structure and flags issues to address.

Essential workflow components are included on every plan. Advanced nodes are available with Enterprise.

Approvals

Clear approvals with rules that fit your process

Choose who decides, whether one response is enough or several approvals are required, and what happens after a rejection.

One person is enough

The task goes to every recipient and the first answer closes the step. The other tasks are cancelled.

Everyone must approve

The step closes once every recipient has answered. Use it where approval is collective.

In order

The task reaches one person at a time, in the order you listed the recipients. The next one gets it after the previous answer.

A due date on the step

Each task has a due date. Once it passes, the task stays marked as overdue in its owner’s task list.

Delegation

If the person expected to respond has an active delegation, the task reaches the delegate without redrawing the Flow.

Everyone's own task list

Each person has a list of steps waiting for them, with the related case and due date.

Configuration, availability and frequently asked questions
More about this feature

A refund to approve, access to authorise, a case involving several departments. Map the process and track tasks, ownership and progress directly in Uppo.

  • Start a workflow from a ticket
  • Manage tasks, ownership and approvals in one workflow
  • Every step stays linked to the original ticket
The processes support handles every day

Refund approval

What starts it
A customer asks for a refund and the agent starts the procedure from the ticket.
The path
  1. The agent records the amount and reason in a form linked to the ticket.
  2. Flow checks the amount and selects the approval path.
  3. The manager makes a decision. For higher amounts, Finance reviews it next.
  4. Flow updates the ticket with the outcome: approved or declined.

Complaint with escalation

What starts it
An automation recognises a complaint and starts the Flow without waiting for someone to open the queue.
The path
Action that assigns the right team → two-day wait → condition on the ticket status → if it is still open, manager approval to decide the escalation → outcome.

Access request

What starts it
A request comes in for authorisation to a tool or a dataset.
The path
Form with the tool requested and the reason → approval by the data owner → action that notifies whoever configures the access → outcome «granted» or «denied», with a note on the ticket.

Procedure across teams

What starts it
A case that needs both the technical and the administrative side, without one waiting on the other.
The path
Branch → the technical team's form on one side, finance approval on the other → join once both have arrived → closing action → outcome.
All nodes and data transformation
Start
Where the procedure begins. One per Flow.
Form
Collect the information you need using dedicated fields or an existing ticket form.
Approval
Request a decision from the right people and define how the process continues after approval or rejection.
Condition
Picks the route based on ticket data and on the values collected in earlier steps.
Action
Carries out an operation with no human input: assigns, updates, notifies, calls a webhook.
Wait
Pauses the path for a duration or until a date, then resumes on its own.
Branch
Start parallel tasks when several teams can work at the same time.
Join
Bring parallel paths together before continuing with the next tasks.
Create linked ticket
Opens a ticket for another team while retaining the link to the case and the original request.
Wait for ticket
Pauses the path until a linked ticket reaches the status or conditions you defined.
HTTP request
Calls an external system with dynamic headers and data, then handles success and error on separate paths.
Data transform
Prepares and converts collected values so later steps can use them in the right format.
Outcome
Closes the procedure with a stated result, and can update the linked ticket.
The three settings of an approval
What happens on a refusal
A refusal closes the step immediately, even in «everyone must approve» mode. From there it is your call: the procedure ends with an outcome, goes back to the start, returns to the previous step, or jumps to a node you name.
Due dates
As with forms, an approval can carry a due date. Once it passes the step shows as overdue; the decision still belongs to a person.
No recipient available
If the node cannot produce a single recipient, the case stops and the manager is notified, instead of moving on as if the step had been done.

Make it work for your team

Every step connected to the customer’s request
Why it matters

Every step connected to the customer’s request

Assign work, collect information and manage approvals while keeping the context intact between departments.

Consistent processes as volume grows

Define the steps and rules once. Your team follows the same process for every request instead of rebuilding it case by case.

Every step has an owner

Assign tasks to people or teams and set deadlines. Ownership and the next action are always visible.

Progress and decisions in view

See progress, open tasks, decisions and history without asking the team for updates.

Tasks and approvals
Collecting data

Collect the information before work moves forward

Assign a form to the right person and let the workflow continue only when the required data is complete.

Fields on the node, or a ticket form

Define the fields on the step itself, or reuse a ticket form you already built and avoid writing the same form in two places.

To a person or a team

The step goes to a specific person or to a team. If you name several recipients, the engine opens a task for each one under the rule you chose.

A due date on the step

Every task carries its due date. Once it passes, the task stays flagged as overdue in the lists of whoever owns it and of the manager.

The data stays with the case

What someone writes in a form becomes a value on the case, readable by the conditions and actions that come after.

Delegation

If the person who should answer has an active delegation, the task reaches the delegate without anyone redrawing the Flow.

Everyone's own task list

Each person has the list of steps waiting on them, with the case they came from and the due date.

Conditions and parallel paths
Routes

Adapt the path to each case and let teams work in parallel

Conditions send each case down the right path. Independent tasks run together and rejoin when they are complete.

Condition

Compares ticket fields and the values collected in earlier steps. Rules combine by requiring all of them or accepting any one, and a branch can be the default for cases that match none.

Parallel branches

A branch node opens two or more routes that run at the same time. This is the case of two teams doing their part without waiting on each other.

Continue once the required branches are done

The path resumes once every branch opened by that split has reached the join, and continues as one until the outcome.

A check before you publish

The validator confirms that every branch returns to its join and that none of them ends on its own: a case never waits for something that will not arrive.

People and automation

People and automations work in the same process

Combine assigned tasks and approvals with automatic ticket updates, notifications, emails and webhooks.

Errors that don't block

This is the default: the error is recorded on the case and the path continues. Right for a notice or a note.

Errors that block

Switch it on for a single node. The case stops and is flagged, instead of assuming an action the following steps depend on, such as a refund.

Waits

A wait node pauses the path for a duration (24 hours, 2 days) or until a specific date. Then the engine resumes on its own.

Case log

Every step opened, every answer, every action and every error goes into an append-only log you can read back to reconstruct how the outcome was reached.

Delays in plain sight

Tasks past their due date stay flagged as overdue, and stalled cases have a view of their own.

Effect on the ticket

On closing, the outcome node can leave a note on the linked ticket or move it to a status you choose.

Starts and versions
Starting a case

Start the workflow at the right moment

An agent can launch it from a ticket, or a rule can start it automatically when the expected conditions are met.

Manual

An agent starts the procedure from a ticket when they recognise the case. It takes the permission to start Flows: seeing them and starting them are two separate rights.

From an automation

A rule starts the Flow when its conditions are true. This is the route for procedures that must always run, without depending on who opens the queue.

Both

The rule covers expected cases; agents can start the procedure manually for other cases.

On the same ticket you decide whether one case at a time is enough or several can coexist. Procedures can also be started from the API.

Draft and publish

Validate every workflow before it goes live

Work in draft, fix configuration errors and publish only when the path is complete and valid.

  1. 01

    Draft

    Design and save as often as you like. The draft runs nothing and touches no case in progress.

  2. 02

    Check

    The validator reviews nodes, connections, branches and settings, and points you to the node behind every error or warning.

  3. 03

    Publish

    The draft becomes the published version. The check runs again on exactly what you are publishing.

Cases already under way stay on their version

Every case freezes the version it started with and follows it to the end. A new version applies to the cases created after it: nobody halfway through a path finds different steps in front of them.

Turning a Flow on and off

A Flow can be deactivated without deleting it: it stops being startable and stays available to reread and switch back on. Cases already open carry on.

Track every case without asking for updates
Oversight

Track every case without asking for updates

Monitor tasks, deadlines, decisions and overall status from one view.

My tasks

Each person sees the steps waiting on their answer, with the due date and the case they came from.

Case list

Every case with its status: running, waiting, blocked, completed, cancelled or failed.

Blocked cases

A dedicated view for the cases that are stuck, with the reason for the block.

Case detail

Completed steps and open ones, the values collected, the branches running and the full history.

Cancellation

A case started by mistake can be cancelled, under a permission separate from the one to start it.

Final outcome

On closing, a case carries a stated result — approved, declined, or whatever label makes sense for your procedure.

Automations handle immediate actions. Flow manages processes over time.

Automations handle immediate actions. Flow manages processes over time.

Use them together: a rule recognises the case and starts the workflow; Flow coordinates people, deadlines and approvals through completion.

Automations

Rules that react to an event on a ticket. They check conditions and take one or more actions, straight away. Nobody has to step in: the ticket is updated and the rule is done.

Flow

A procedure that runs over time. It has steps assigned to people, approvals, conditions, waits and a final outcome. It stays open until the path reaches the end, and at any moment you know where it is.

The two work together

An automation starts a Flow when a condition is met, and an action node inside the Flow uses the same catalogue of actions as the rules. They are two ways of triggering the same work.

See how automations work
Uppo Flow

Flow grows with your plan

Build workflows with forms, approvals and linked tickets. With Enterprise, you can also call external APIs and transform data between steps.

Included on all plans

The core nodes, from Starter up

The core canvas nodes are part of Starter, Growth, Scale and Enterprise. The canvas is not reserved for the higher plans.

Guided configuration

From process to canvas

Start from a template or design the process on the canvas. Steps, owners, deadlines and approvals remain editable by your team.

Enterprise

The advanced nodes

HTTP calls to external systems and data transformations are reserved for Enterprise. Linked tickets, waits and human steps remain in the core catalogue.

Compare plans and prices

Frequently asked questions

Setting up, starting and managing procedures.

What is the difference between Flow and automations?

Automations apply actions when an event occurs and the configured conditions are met. Flow manages a procedure over time, with assigned tasks, approvals, waits and an outcome. An automation can start a Flow.

Who can start a Flow?

It depends on how you configure it. A Flow can be startable only by hand, only by an automation, or both ways. Manual start requires a dedicated permission, separate from seeing procedures and from designing them. Procedures can also be started from the API.

Who does a step get assigned to?

To a person or to a team. If you name several recipients, the engine opens a task for each under the rule you chose on the node, and if the person who should answer has an active delegation the task reaches the delegate.

How do approvals and due dates work?

On each approval you choose whether one person is enough, whether everyone must answer, or whether they answer in order. You can set a due date: once it passes the step shows as overdue, and the decision still belongs to a person. On a refusal, you decide whether the procedure ends, goes back to the start, returns to the previous step, or jumps to a specific node.

Can tasks run in parallel?

Yes. You can open parallel work paths and bring them together before continuing. Publication checks verify that the paths reach the intended join point.

What happens if an action fails?

Configure the behaviour on each node. A non-blocking action records the error and lets the path continue; a blocking action stops the case and reports the issue. Choose according to how the action affects later steps.

Do edits affect Flows already running?

Each case retains the published version it started with. New versions apply to cases started after publication.

How do I configure my first Flow?

Start from a template or design the procedure on the canvas, defining steps, owners, deadlines and approvals. Core nodes are included on every plan; advanced nodes remain reserved for Enterprise.

Which plans include it?

Core Flow is included on every plan, from Starter to Enterprise. Advanced HTTP request and data transform nodes are reserved for Enterprise.

Read more

Automations

The rules that react to an event on a ticket, and that can start a Flow when a procedure is needed.

See the automations

All the features

Channels, tickets, SLAs, knowledge base, portals and integrations: the whole product at a glance.

See the features

Plans and prices

What Uppo costs, what each plan includes and how the agents in the plan work.

See the prices

Design your first workflow with your team

Start with an example, adapt it to your service and publish it when it’s ready.