Skip to main content
Actions in Forest let operators trigger custom business logic on one or more records, sending emails, updating statuses, charging payments, generating reports, and more. This page explains how to find and execute actions as an operator.

​
Types of actions

TypeDescription
Single recordTriggered from a specific record’s detail view or row menu
BulkTriggered on multiple selected records at once
GlobalTriggered from the collection level, without selecting a record

​
Triggering a single record action

  1. Open a record by clicking on a row in the table view.
  2. In the detail view, look for the Actions button (top-right area).
  3. Click the action you want to execute.
  4. If the action has a form, fill in the required fields and click Submit.
Trigger actions directly from the row using the context menu (three-dot icon) without opening the detail view.

​
Triggering bulk actions

  1. Select multiple records using the checkboxes in the table view.
  2. The Actions toolbar appears at the top of the table.
  3. Click the action you want to run on the selected records.
  4. Fill in the form (if required) and confirm.
Bulk actions apply to all selected records. Some actions may have a maximum number of records they can process at once.

​
Triggering global actions

Global actions are not tied to any specific record. They appear in the Actions menu at the top of the collection view, regardless of whether records are selected. Use global actions for operations like generating a report, triggering a sync, or exporting data.

​
Action forms

Many actions open a form before execution. The form lets you provide additional input required by the action, for example, a reason for rejection, an amount to refund, or a target email address.
  • Required fields are marked and must be filled before the form can be submitted.
  • Dynamic fields may appear or change based on values you enter in other fields.
  • Dropdowns and pickers are common field types for structured input.

​
Actions requiring approval

Some actions are configured to require approval from another team member before they execute. When you trigger such an action:
  1. A request is submitted to the Approval Workflow.
  2. The action is not executed immediately, it waits for approval.
  3. You can track the status in the Approval Workflows tab.
Approval workflows are configured by admins in Project Settings → Roles. See Approval Workflows.

​
Actions requiring confirmation

Some actions display a confirmation dialog before executing, to prevent accidental triggers. Read the confirmation message carefully before proceeding.

​
Permissions

Which actions you can see and execute depends on your role permissions, configured by your admin. If an action is not visible, you may not have permission to access it.