Workflows

Automate your processes with deterministic rules, AI steps and human in the loop

Automate your processes with deterministic rules, AI steps and human in the loop

Automate your processes with deterministic rules, AI steps and human in the loop

Workflows start on a record change, a webhook or an AI agent. Rules settle defined cases, AI handles complex ones, and your team has the final say.

TL;DR

Forest Workflows are multi-step operational processes built directly on top of your live data, started by a record change, a webhook, an AI agent or an operator.

Rules run the defined steps, AI takes on complex tasks, and your team keeps the final say, with approvals and routing built in.

Every step runs under the permissions you define, and lands in your audit trail.

Define the right workflows. Run them on live data. Audit every step.

Define the right workflows. Run them on live data. Audit every step.

From onboarding to refund approvals, Workflows guide operators through each step, with the right data and the right actions in place.

Step-by-step guidance

Each workflow defines the steps and the order. Operators see exactly what to do next.

Starts on its own

A workflow can start when a record changes, when another system calls its webhook, when an AI agent asks through the MCP server, or when an operator starts it.

Deterministic and AI steps

Rules run the defined steps with the same result every time. An AI agent can take a step (draft, summarize, classify, decide on routine cases) inside the same workflow as a human.

Approvals built in

Add an approval step anywhere in the flow. Two-person, manager sign-off, or role-based, configurable per step.

Escalations to the right team

Routing rules send the case to a different inbox, a different team, or a manager when the situation requires it. Automated runs that need a person land in a fallback inbox.

Audit on every step

Every transition, action, decision, and approval is recorded at the record level. The workflow history is part of the case.

Built for cross-team ops

Workflows your team and your AI agents can run together

Workflows your team and your AI agents can run together

Cross-team handoffs

Workflows move cases between ops, compliance, support, and engineering with the context carried through.

Onboarding new operators

Workflow steps double as a checklist. New team members see exactly what to do, in the order it needs to happen.

Your use cases, already mapped

See how teams run KYC, KYB and customer onboarding as workflows on Forest.

Forest Workflows give us a checklist of the procedure for onboarding cases, directly in our production tool. It's increasing our compliance rate.

Martin Bouvier

Head of Customer Onboarding

Forest Workflows give us a checklist of the procedure for onboarding cases, directly in our production tool. It's increasing our compliance rate.

Martin Bouvier

Head of Customer Onboarding

Forest Workflows give us a checklist of the procedure for onboarding cases, directly in our production tool. It's increasing our compliance rate.

Martin Bouvier

Head of Customer Onboarding

Vendor agnostic

Works with the providers you already use

Works with the providers you already use

Frequently asked questions

You still have question ?
Book a conversation with a forest expert

What is a workflow in Forest?

A workflow is a multi-step process defined in the backoffice. It runs on live data, can include AI agent steps and approvals, and is fully audited.

How does a workflow start?

Four ways, each turned on per workflow: when a record changes, when another system calls the workflow's webhook, when an AI agent starts it through the MCP server, or when an operator starts it from Forest. Only one run of a workflow is active on a record at a time.

Can we mix human and AI agent steps?

Yes. A workflow can include any sequence of AI agent and human steps. The same case moves between them, with full audit on every transition.

Which steps are deterministic, and which use AI?

Get Data, Update Data, decisions in automatic mode and sub-workflows give the same result for the same input, with no model call. AI-assisted decisions, drafted guidance and suggested values use a model. If a policy check can be written as a condition, make it deterministic.

Can workflows call external systems?

Yes. Steps can call any external API: PSPs, KYC providers, detection engines, messaging tools. The call is logged with the case.

Can workflows route across teams?

Yes. A workflow can move a case from one team's inbox to another, with the context carried through. Routing rules are configurable per step.

What happens when nobody is there to take a step?

An automated run that reaches a step needing a person, or that fails, goes to the workflow's fallback inbox, flagged as escalated. An operator resumes it from where it stopped.

How do approvals work?

Approval steps are configured per workflow. Two-person review, manager sign-off, and role-based approvals are supported. Approvals are part of the case record.

What does a workflow look like in practice?

Take a KYB review: a record update starts it, rules handle the standard checks, AI assesses whether the activity fits the declared sector, and unclear cases go to your compliance team's inbox. See KYB and KYC for more.

How do you ensure customer data never leaves our environment?

The Forest back-end runs inside your infrastructure, alongside your databases. Customer data travels to a provider only at the point where its service is called, and the response is logged back to the case. Data stays in your systems of record.

{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"What is a workflow in Forest?","acceptedAnswer":{"@type":"Answer","text":"A workflow is a multi-step process defined in the backoffice. It runs on live data, can include AI agent steps and approvals, and is fully audited."}},{"@type":"Question","name":"How does a workflow start?","acceptedAnswer":{"@type":"Answer","text":"Four ways, each turned on per workflow: when a record changes, when another system calls the workflow's webhook, when an AI agent starts it through the MCP server, or when an operator starts it from Forest. Only one run of a workflow is active on a record at a time."}},{"@type":"Question","name":"Can we mix human and AI agent steps?","acceptedAnswer":{"@type":"Answer","text":"Yes. A workflow can include any sequence of AI agent and human steps. The same case moves between them, with full audit on every transition."}},{"@type":"Question","name":"Which steps are deterministic, and which use AI?","acceptedAnswer":{"@type":"Answer","text":"Get Data, Update Data, decisions in automatic mode and sub-workflows give the same result for the same input, with no model call. AI-assisted decisions, drafted guidance and suggested values use a model. If a policy check can be written as a condition, make it deterministic."}},{"@type":"Question","name":"Can workflows call external systems?","acceptedAnswer":{"@type":"Answer","text":"Yes. Steps can call any external API: PSPs, KYC providers, detection engines, messaging tools. The call is logged with the case."}},{"@type":"Question","name":"Can workflows route across teams?","acceptedAnswer":{"@type":"Answer","text":"Yes. A workflow can move a case from one team's inbox to another, with the context carried through. Routing rules are configurable per step."}},{"@type":"Question","name":"What happens when nobody is there to take a step?","acceptedAnswer":{"@type":"Answer","text":"An automated run that reaches a step needing a person, or that fails, goes to the workflow's fallback inbox, flagged as escalated. An operator resumes it from where it stopped."}},{"@type":"Question","name":"How do approvals work?","acceptedAnswer":{"@type":"Answer","text":"Approval steps are configured per workflow. Two-person review, manager sign-off, and role-based approvals are supported. Approvals are part of the case record."}},{"@type":"Question","name":"What does a workflow look like in practice?","acceptedAnswer":{"@type":"Answer","text":"Take a KYB review: a record update starts it, rules handle the standard checks, AI assesses whether the activity fits the declared sector, and unclear cases go to your compliance team's inbox. See KYB and KYC for more."}},{"@type":"Question","name":"How do you ensure customer data never leaves our environment?","acceptedAnswer":{"@type":"Answer","text":"The Forest back-end runs inside your infrastructure, alongside your databases. Customer data travels to a provider only at the point where its service is called, and the response is logged back to the case. Data stays in your systems of record."}}]}

Workflows

LEVEL UP YOUR OPS GAME

One control plane. Every action traced for human, agent, BPO, LLM, workflow.

Workflows

LEVEL UP YOUR OPS GAME

One control plane. Every action traced for human, agent, BPO, LLM, workflow.

Workflows

LEVEL UP YOUR OPS GAME

One control plane. Every action traced for human, agent, BPO, LLM, workflow.

The operational infrastructure regulated companies grow on

Copyright ยฉ 2026 Forest

Design by Alasta & Built by Reiya Studio