>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3538732. --> Reported by: [d34dman](https://www.drupal.org/user/751698) >>> <p>FlowDrop aims to provide a visual, agentic workflow execution engine capable of orchestrating complex tasks, including AI-driven decision-making and multi-step automations. Before committing to a fully custom execution model, we need to evaluate whether existing Drupal core or contrib workflow systems can serve as a foundation or partially integrate into FlowDrop.</p> <h3>Scope of Research:</h3> <ul> <li><strong>Drupal Core Workflow / Workbench</strong>: <ul> <li>Entity-based state management</li> <li>Transition handling and limitations for dynamic or AI-driven flows</li> </ul> </li> <li><strong>ECA (Event-Condition-Action) module</strong>: <ul> <li>Node-based event and condition orchestration</li> <li>Suitability for high-volume, asynchronous processing and complex branching</li> </ul> </li> <li><strong>Core Actions and Events</strong>: <ul> <li>Trigger-based execution model</li> <li>Extensibility for AI-driven or agentic processes</li> </ul> </li> <li>Investigate any other contrib solutions relevant to workflow orchestration</li> </ul> <h3>Goals:</h3> <ul> <li>Identify gaps in current contrib solutions for supporting FlowDrop&rsquo;s complex workflow needs (dynamic branching, agentic reasoning, async execution, external API orchestration).</li> <li>Determine if we should extend an existing model (ECA or Core Workflow) or implement a custom Node Runtime as designed in FlowDrop.</li> <li>Produce a recommendation document that guides architectural decisions for the FlowDrop execution engine.</li> </ul> <h3>Deliverables:</h3> <ul> <li>Comparative matrix highlighting features, limitations, and performance considerations of each evaluated model</li> <li>Recommendation on integration, extension, or custom build approach</li> </ul>