Install

Works with Drupal: ^11.3

Using Composer to manage Drupal site dependencies

Alternative installation files

Download tar.gz 59.41 KB
MD5: 87ad508a1e21051835149d4a9d0f45c0
SHA-1: cb1d6ed191e1504768fa0caba971d445dbb230b6
SHA-256: 6a464997af2079acf9cb93cb1be65d9f47138d253a93f2278a6f3f7c3122ae4c
Download zip 87.77 KB
MD5: f63452ea579123d10d35b01908da42a0
SHA-1: 1f6c4795305578e821c355a573843682db29bccc
SHA-256: ad8e583297a5bc9115d13855e92ef944a8b9a35f0ce5e3ccf444e79e2749333f

Release notes

Workflow tools now run through FlowDrop's launcher and are recorded as runs. Only a workflow that can answer a tool call in the same request can be called as a tool. Requires Drupal core ^11.3 and FlowDrop 2.7.

Check this before upgrading

These workflows are refused as tools, where alpha3 ran them:

  • Asynchronous workflows, including any workflow that declares no orchestrator (FlowDrop then defaults to the asynchronous one). FlowDrop 2.7 has no form for this setting, so set it in each workflow's config and import it:
    metadata:
      orchestrator_settings:
        type: 'flowdrop_runtime:synchronous_pipeline'
  • Workflows that can pause: a node that asks or waits (confirmation, choice, text or form input, timer, call and wait), a node that needs approval before it runs (a side-effecting node, unless waived), or a Run Workflow node whose sub-workflow is missing, runs asynchronously or can itself pause.
  • Disabled workflows and node types.

The status report (/admin/reports/status) warns about each node type marked "Available as Tool" that cannot be called as a tool, and says why. Check it after updating.

Changed

  • A workflow tool runs through flowdrop_workflow_executor.launcher, on the orchestrator the workflow declares. Each call is stored as a pipeline with one job per node, and records the calling user as its starter (#3631968).
  • Calls that cannot work are refused before anything is launched, so no run is created. Disabled and asynchronous workflows are left out of the tool list. A workflow that can pause is still listed but is refused when called.
  • A run that still pauses (on its execution budget, or at a wired confirmation port) fails the call and is marked cancelled.
  • Failure messages name the run.
  • Storage cost: each call now writes a pipeline and its jobs, and FlowDrop 2.7 never deletes runs. Plan for this on tools that agents call often.
  • core_version_requirement is ^11.3 in both modules, matching composer.

Fixed

  • The tool list refreshes when a node type or workflow is saved or deleted, with no cache rebuild needed.
  • A tool whose node type is gone, disabled, no longer exposed or repointed refuses to run, even from a stale cached definition.
  • The tool no longer uses FlowDrop's @internal pipeline interface or status enum.

Known limits

  • Tool calls run inside the web request, so a long workflow can hit PHP's time limit.
  • Changing the site's default orchestrator is picked up only after a cache rebuild.
  • Letting the tool choose an orchestrator when a workflow declares none: flowdrop#3592516, tracked here in #3631969.

Full details are in CHANGELOG.md.

Created by: d34dman
Created on: 18 Nov 2026 at 03:41 UTC
Last updated: 18 Nov 2026 at 03:43 UTC
Bug fixes
New features

Other releases