Actions
Define the operations your team performs every day as actions on the customer record. Permissions, approvals, and audit are part of the action, not bolted on after.

Every action runs on the record, under the permissions of the actor (human or agent), and writes back to the source.
Record-level actions
Actions live on the customer, transaction, or case record. The action knows the context it runs on.
Permissions at the action level
Who can trigger the action, on which records, under what conditions. Configurable per role.
Approvals when required
Add an approval step before an action executes. Two-person, manager, or workflow-driven.
External system calls
Actions can call your PSP for a refund, your messaging provider for a notification, your detection engine to update a case. The call is logged.
Custom logic in code
Beyond configuration, actions can include custom code in the Forest SDK. Validation, side effects, and complex logic run inside the Forest Agent.
Audit on every execution
Each action records who ran it, on which record, with which data, and what the result was. Audit is structural.


Built for governed ops
Permissions per action
Each action carries its own permission scope. Your team and your AI agents only trigger what their role allows.
Approvals built in
Sensitive actions can require manager sign-off, two-person review, or workflow-driven approval before they run.
Audit-ready by default
Every action records who ran it, on which record, with which data, and what the result was. Compliance is structural, not bolted on.
Vendor agnostic
Frequently asked questions
You still have question ?
Book a conversation with a forest expert
What is an Action in Forest?
An Action is an operational step defined on a record type (customer, transaction, case). It runs under the permissions of the user or agent triggering it, and writes its effect back through the connected system.
Can actions trigger external systems?
Yes. Actions can call your PSP, KYC provider, messaging tool, or any external API. The call and response are logged with the action.
How do approvals work on actions?
Approvals can be required per action, per role, or per record condition. The approval step is part of the action's definition.
Can agents trigger actions?
Yes, within their configured permissions. An agent triggers an action the same way a human does, under its own scoped role, with the same audit trail.
Can we extend actions with custom code?
Yes. The Forest SDK supports custom action handlers in code, running inside the Forest Agent. Validation, side effects, and complex logic can be written in your language of choice.

