github-starred/n8n
2
0
Fork 0
mirror of https://github.com/n8n-io/n8n.git synced 2025-12-05 19:27:26 -06:00
Code Issues 1.3k Packages Projects Releases 100 Wiki Activity

The workflow, including the webhook trigger, should always been in an execution state unless it has been deactivated. #4602

New Issue
Closed
opened 2025-11-19 19:42:23 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-19 19:42:23 -06:00
Owner
Copy Link

Originally created by @xiongzhp on GitHub (Jul 23, 2025).

Bug Description

I hope to automatically generate and execute a workflow based on the description. Currently, there is a problem: the webhook trigger can only receive POST requests when the workflow is in an executing state, and there is no available API interface to automatically execute the newly created workflow. In contrast, the timed trigger method seems less flexible and intelligent.

To Reproduce

The workflow, including the webhook trigger, should always been in an execution state unless it has been deactivated. Because there is no available API interface to automatically execute the newly created workflow.

Expected behavior

The workflow, including the webhook trigger, should always been in an execution state unless it has been deactivated. Because there is no available API interface to automatically execute the newly created workflow.

Debug Info

The workflow, including the webhook trigger, should always been in an execution state unless it has been deactivated. Because there is no available API interface to automatically execute the newly created workflow.

Operating System

Ubuntu

n8n Version

any

Node.js Version

any

Database

SQLite (default)

Execution mode

main (default)

Hosting

self hosted

Originally created by @xiongzhp on GitHub (Jul 23, 2025). ### Bug Description I hope to automatically generate and execute a workflow based on the description. Currently, there is a problem: the webhook trigger can only receive POST requests when the workflow is in an executing state, and there is no available API interface to automatically execute the newly created workflow. In contrast, the timed trigger method seems less flexible and intelligent. ### To Reproduce The workflow, including the webhook trigger, should always been in an execution state unless it has been deactivated. Because there is no available API interface to automatically execute the newly created workflow. ### Expected behavior The workflow, including the webhook trigger, should always been in an execution state unless it has been deactivated. Because there is no available API interface to automatically execute the newly created workflow. ### Debug Info The workflow, including the webhook trigger, should always been in an execution state unless it has been deactivated. Because there is no available API interface to automatically execute the newly created workflow. ### Operating System Ubuntu ### n8n Version any ### Node.js Version any ### Database SQLite (default) ### Execution mode main (default) ### Hosting self hosted
GiteaMirror added the
closed:enhancement/feature
in linear
 labels 2025-11-19 19:42:23 -06:00
GiteaMirror commented 2025-11-19 19:42:24 -06:00
Author
Owner
Copy Link

@Joffcom commented on GitHub (Jul 23, 2025):

Hey @xiongzhp,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-3275".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

@Joffcom commented on GitHub (Jul 23, 2025): Hey @xiongzhp, Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-3275". We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful! Thanks for your patience and for bringing this to our attention.
GiteaMirror commented 2025-11-19 19:42:25 -06:00
Author
Owner
Copy Link

@Joffcom commented on GitHub (Jul 23, 2025):

Thank you for taking the time to share your suggestion! We’ve reviewed the details, and it seems this is more of a feature or enhancement request rather than a bug report.

As a heads-up, we use GitHub issues exclusively for tracking bugs. For feature requests or support questions, we recommend sharing them on our forum, where the community and our team actively discuss and prioritize new ideas.

We’re closing this issue for now to keep our tracker focused, but we’d love to hear more about your idea on the forum! Your feedback helps us improve, and we truly appreciate it.

Thanks again for contributing, and we hope to see you on the forum!

@Joffcom commented on GitHub (Jul 23, 2025): Thank you for taking the time to share your suggestion! We’ve reviewed the details, and it seems this is more of a feature or enhancement request rather than a bug report. As a heads-up, we use GitHub issues exclusively for tracking bugs. For feature requests or support questions, we recommend sharing them on [our forum](https://community.n8n.io), where the community and our team actively discuss and prioritize new ideas. We’re closing this issue for now to keep our tracker focused, but we’d love to hear more about your idea on the forum! Your feedback helps us improve, and we truly appreciate it. Thanks again for contributing, and we hope to see you on the forum!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Backlog
bug-report
Bump
Bumped
closed:duplicate
closed:enhancement/feature
closed:incomplete-template
closed:info
closed:non-english
closed:support-issue
closed:working-as-expected
Duplicate
in linear
In Review
n8n team
Needs Feedback
Needs Feedback:Unable to reproduce
node/improvement
node/issue
node/new
pull-request
Mirrored from GitHub Pull Request
Released
Stale
status:complete
status:in-linear
status:pending-assignment
status:team-assigned
team:adore
team:ai
team:cats
team:nodes
team:payday
triage:complete
triage:in-progress
triage:needs-info
triage:needs-reproduction
triage:pending
triage:stalled
ui
Upcoming Release
No Label
closed:enhancement/feature
in linear
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/n8n#4602
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?