I would first identify the n8n credential being used by each Box node, rather than trying to infer it from the login screen. the node uses OAuth2 credentials, and on Enterprise/Cloud the practical way to audit this is through the workflows/projects and credentials access you have as an owner/admin. Check each workflow using Box or Box Trigger, note the credential selected on those nodes, then migrate those workflows to the new central Box credential in batches. Keep the old Box app enabled until execution history confirms no workflows are still using the old credential.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Use n8n behind the scenes | 16 | 4450 | February 2, 2021 | |
| Deactivating old n8n and moving workflows to new instance | 9 | 1641 | December 13, 2023 | |
| Can n8n be used to authenticate with multiple different users? | 15 | 5129 | January 9, 2023 | |
| Update n8n CLI workflows command (import/export) to support folders | 0 | 225 | April 29, 2025 | |
| Rest and api | 28 | 3009 | November 8, 2022 |