Form trigger URL construction fixed in AI agent
The AI agent no longer mangles form trigger URLs. A clearer system prompt now distinguishes between Webhook, Form, and Chat trigger URL patterns so users get working links to their workflows.
The AI agent was generating incorrect URLs when users built workflows with form triggers. It was likely applying the /chat suffix that belongs only to Chat Triggers, leaving users with broken links to their forms.
The system prompt has been rewritten to explicitly separate the three trigger types. Webhook Trigger and Form Trigger now share a clear pattern (base URL plus path), while Chat Trigger gets its own distinct /chat suffix. The new prompt also explicitly warns against guessing webhook IDs and instructs the agent to read the workflow to find the correct value.
Users building form-triggered workflows should now receive accurate, working URLs immediately after workflow creation.
View Original GitHub Description
Summary
The agent was struggling to construct correct links for form triggeres. I adjusted the system prompt to hopefully make it easier for the agent to come up with the correct URL.
Related Linear tickets, Github issues, and Community forum posts
<!-- Include links to **Linear ticket** or Github issue or Community forum post. Important in order to close *automatically* and provide context to reviewers. https://linear.app/n8n/issue/ --> <!-- Use "closes #<issue-number>", "fixes #<issue-number>", or "resolves #<issue-number>" to automatically close issues when the PR is merged. -->Review / Merge checklist
- I have seen this code, I have run this code, and I take responsibility for this code.
- PR title and summary are descriptive. (conventions) <!-- **Remember, the title automatically goes into the changelog. Use `(no-changelog)` otherwise.** -->
- Docs updated or follow-up ticket created.
- Tests included. <!-- A bug is not considered fixed, unless a test is added to prevent it from happening again. A feature is not complete without tests. -->
- PR Labeled with
Backport to Beta,Backport to Stable, orBackport to v1(if the PR is an urgent fix that needs to be backported)