September 2026 release notes: MCP-triggered Workflows and deterministic Decisions

Two updates to Workflows this month. One of them makes the Forest MCP Server even more helpful.

Trigger Forest Workflows from any MCP client

Your LLM client (Claude, Dust, or any MCP-compatible client) can now trigger Forest Workflows via the Forest MCP Server. Combined with reading records and running actions, that covers the three main operations against Forest: read, act, trigger.

Setup takes one config in your Forest back-end. See the MCP Server docs.

Forest Workflows: trigger a Workflow from your MCP client

Decisions get an "Automatic (Deterministic)" execution mode

While we shipped Workflows with AI at every step, many of you mentioned you'd rather keep things deterministic for certain use cases. So we're bringing more deterministic options to Workflows.

• Get Data and Update Data steps received deterministic options in August.

• New: Decision steps are getting an "Automatic (Deterministic)" execution mode. It uses upstream Get Data steps to evaluate conditions and ensure the workflow goes down the correct path, with no runtime interpretation.

• Manual, AI-assisted, and Full AI execution modes remain available for Decisions that need runtime interpretation.

Question or suggestion? These inform the roadmap, so get in touch.

Forest is the back-office platform for fintechs. Ops teams and the AI agents that assist them work on the same governed data (accounts, transactions, customers), through the same audited surface. Learn more →