Merged
Size
XS
Change Breakdown
Bug Fix95%
Maintenance5%
#27968fix(core): Set trigger start node for executions without input data

Test button now works for webhook-only AI triggers

Webhook-only triggers like Chat Trigger in Instance AI can now be tested directly — previously, clicking "Test" silently did nothing instead of running the trigger or returning a meaningful error.

When setting up workflows with the Instance AI assistant, clicking "Test" on webhook-only triggers like Chat Trigger did nothing. The system found the trigger node but never told the execution engine where to start, resulting in a silent "No node to start the workflow from could be found" failure.

The execution adapter has been updated to explicitly tell the engine which node to start from when no input data is present. Now when users click "Test" on Chat Trigger or similar webhook-only triggers, the trigger executes and returns either success or a meaningful error — the behavior users expected all along.

This fix lives in the CLI's Instance AI adapter service, which handles workflow setup interactions.

View Original GitHub Description

Summary

  • Fixes the "Test" button in Instance AI workflow setup doing nothing for webhook-only triggers like Chat Trigger
  • The execution adapter found the trigger node but never told the execution engine to start from it when inputData was absent, causing "No node to start the workflow from could be found"
  • Sets triggerToStartFrom so the manual execution service uses the correct start node

Related

https://www.notion.so/n8n/Test-step-is-not-doing-anything-3365b6e0c94f80aaa298efbba2d45dc6

Test plan

  • Open Instance AI, build a workflow with a Chat Trigger
  • In the setup step, click "Test" on the Chat Trigger card
  • Verify the trigger test executes (success or meaningful error) instead of silently failing
  • Verify workflows with other trigger types (Webhook, Schedule, Form) still work correctly
© 2026 · via Gitpulse