fix(cli): register webhooks when activating workflow via REST API

[DmitryVDV]

Summary

When activating a workflow via REST API (POST /rest/workflows/{id}/activate), webhooks are not being registered because shouldAddWebhooks() in ActiveWorkflowManager only returns true for init and leadershipChange activation modes, not for activate.

Fix

Added activate to the list of activation modes that trigger webhook registration in shouldAddWebhooks() method.

Before:

if (['init', 'leadershipChange'].includes(activationMode)) return true;

After:

if (['init', 'leadershipChange', 'activate'].includes(activationMode)) return true;

Testing

Tested manually on a development build:

1. Created a workflow with a webhook node
2. Activated it via REST API: POST /rest/workflows/{id}/activate
3. Verified the webhook responds with 200 OK and "Workflow was started"

Related Issue

Fixes #21614

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

DmitryVDV seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[cubic-dev-ai]

No issues found across 1 file

[n8n-assistant]

Hey @DmitryVDV,

Thank you for your contribution. We appreciate the time and effort you’ve taken to submit this pull request.

Before we can proceed, please ensure the following:
• Tests are included for any new functionality, logic changes or bug fixes.
• The PR aligns with our contribution guidelines.

Regarding new nodes:
We no longer accept new nodes directly into the core codebase. Instead, we encourage contributors to follow our Community Node Submission Guide to publish nodes independently.

If your node integrates with an AI service that you own or represent, please email [email protected] and we will be happy to discuss the best approach.

About review timelines:
This PR has been added to our internal tracker as "GHC-5790". While we plan to review it, we are currently unable to provide an exact timeframe. Our goal is to begin reviews within a month, but this may change depending on team priorities. We will reach out when the review begins.

Thank you again for contributing to n8n.