Box trigger node pagination and webhook checks fixed
The Box trigger node was using the wrong pagination type and failing to check webhooks correctly. Both issues are now resolved.
Box changed their webhook API, breaking n8n's trigger node in two ways. The pagination logic used an outdated offset-based method when the API now requires marker-based iteration. Worse, the webhook existence check relied on fields—address and triggers—that the API no longer includes in list responses. Users activating Box triggers would find workflows stuck in a failed state with no webhook created.
A new marker-based pagination function handles the API's current requirements. When checking for existing webhooks, the node now fetches full webhook details on demand rather than expecting everything in the list response. Webhook activation should now work reliably.
View Original GitHub Description
Summary
The Box trigger node was using the wrong pagination type, This adds a second pagination type and updates the node to use it along with fetching the details for the webhook if needed due to the "mini webhook" option.
Related Linear tickets, Github issues, and Community forum posts
https://linear.app/n8n/issue/NODE-4656/community-issue-box-trigger-node-logic-is-broken#comment-54ad0262 Closes #25013
Review / Merge checklist
- 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)