Flowise [BUG] Composio - Auth Status fails to update to Connected

Describe the bug When adding a Tool node to Agentflow 3.0.1 using the Composio tool, authentication succeeds and integration data is retrieved, but the integration status does not update to "Active". As a result, the node fails to execute properly.

To Reproduce Steps to reproduce the behavior:

Go to Agentflow 3.0.1
Add a new Tool node to the flow
Configure the node to use Composio tool
Complete the authentication process
Verify that integration data is successfully retrieved
Observe that the integration status remains inactive instead of updating to "Active"
Attempt to execute the flow
See error - node does not execute due to inactive status

Expected behavior After successful authentication and data retrieval from the Composio integration, the status should automatically update to "Active", allowing the Tool node to execute properly within the flow.

Screenshots If applicable, add screenshots to help explain your problem.

Setup

Docker [email protected]

Additional context

The authentication process completes successfully
Integration data is properly retrieved from Composio
The issue appears to be specifically with the status update mechanism
This prevents the Tool node from functioning despite successful connection
Issue occurs consistently with Composio tool integration in Agentflow 3.0.1

Jun 03 '25 16:06 jtguzman

I have the same issue with NPM [email protected]

Logs:

2025-06-13 18:45:00 [INFO]: ⬆️ POST /api/v1/node-load-method/composio [info]: 06-14 00:45:00.24 - Initializing Composio w API Key: [REDACTED] and baseURL: https://backend.composio.dev/ 🚀 Upgrade available! Your composio-core version (0.4.8) is behind. Latest version: 0.5.39.

Jun 14 '25 00:06 SheshoVega

hi can I work on this issue?

Jul 08 '25 13:07 ydv-ankit

hello, same issue with [email protected], any updates please .?

[info]: 07-21 09:56:02.01 - Initializing Composio w API Key: [REDACTED] and baseURL: https://backend.composio.dev/ 🚀 Upgrade available! Your composio-core version (0.4.7) is behind. Latest version: 0.5.39. 🚀 [Info] Give Feedback / Get Help: https://dub.composio.dev/discord 🐛 [Info] Create a new issue: https://github.com/ComposioHQ/composio/issues ⛔ [Info] If you need to debug this error, set env variable COMPOSIO_LOGGING_LEVEL=debug Error loading apps: ComposioError: 💥 Oops! Internal server error for https://backend.composio.dev//api/v1/apps at CEG.throwAPIError (X:\Windows\Flowise\node_modules.pnpm\[email protected]\node_modules\composio-core\dist\index.js:38917:15) at CEG.handleAllError (X:\Windows\Flowise\node_modules.pnpm\[email protected]\node_modules\composio-core\dist\index.js:38884:35) at Apps.list (X:\Windows\Flowise\node_modules.pnpm\[email protected]\node_modules\composio-core\dist\index.js:39190:23) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Composio_Tools.listApps (X:\Windows\Flowise\packages\components\dist\nodes\tools\Composio\Composio.js:42:34) at async Object.getSingleNodeAsyncOptions (X:\Windows\Flowise\packages\server\dist\services\nodes\index.js:98:36) at async getSingleNodeAsyncOptions (X:\Windows\Flowise\packages\server\dist\controllers\nodes\index.js:67:29) { metadata: { fullUrl: 'https://backend.composio.dev//api/v1/apps', method: 'GET', statusCode: 500, requestId: 'Request ID: 70f065fb-df99-4de3-ab7d-1ce44d1aeb37', metadata: { responseTime: 508, responseSize: 0 } }, errCode: 'BACKEND::SERVER_ERROR', description: 'Your request could not be processed due to an internal server error.', possibleFix: 'Please try again later. If the issue persists, contact support.', timestamp: '2025-07-21T09:56:02.571Z', errorId: '2afe0cc9-d752-4d94-84cc-e42a65c96195' }