Credential missing with AI agent and HTTP node as a tool

It appears your topic is missing some crucial details. Could you please provide the following information, if it applies?

• callin.io version:
• Database (default: SQLite):
• callin.io EXECUTIONS_PROCESS setting (default: own, main):
• Running callin.io via (Docker, npm, callin.io cloud, desktop app):
• Operating system:

Please share these details to help us assist you better.

Hi there!

Could you let me know which version of callin.io you are currently using? This issue sounds like a bug that we believe was resolved in version 1.65.0.

Hi I am currently running on ver 1.71.2

Hi there,

Could you please examine the agent's logs for more specifics regarding the error encountered in the HTTP request node? Additionally, kindly confirm that you are utilizing the most recent version of the HTTP tool node (refer to the settings tab).

Please provide the rewritten markdown content.

Hello,
I’m encountering the exact same issue as described by a previous user: the same request functions perfectly within the standalone HTTP node, but it fails when used in the HTTP Tool.
Here is my setup:

• callin.io version: 1.76.1
• Database (default: SQLite): default
• callin.io EXECUTIONS_PROCESS setting (default: own, main): default
• Running callin.io via (Docker, npm, callin.io cloud, desktop app): Docker
• Operating system: MacBook Pro M1
• HTTP Request Tool node version: 1.1 (Latest)

There is no additional information in the AI Agent logs; this is all that is visible:

{
  "response": "There was an error: "Credentials not found""
}

Any insights would be greatly appreciated.
Thank you.

I believe this might be related to the issue I detailed previously.

For my situation, the HTTP Request tool appears to function with predefined credential types but not with generic ones.

I am currently using version 1.76.1 and the latest version of the node.

I agree, they are connected.

However, I'm having trouble figuring out how to utilize the Predefined Credential Type when using a Keycloak identity provider.

The issue persists on version 1.76.2. Using generic credentials (OAuth2 API) with the HTTP node functions correctly. However, when utilizing the HTTP Tool Call node, it does not.

Experiencing the same problem. There's an issue with executing an HTTP Tool node when using a generic credentials type, specifically OAuth2 API. Are there any workarounds for this situation? I need to make an HTTP call via the Agent and retrieve a result.

The workaround involves utilizing the Callin.io Workflow Tool, incorporating an additional workflow and a standard HTTP request node. This approach functions effectively.

Hi there,

it appears the issue persists in v 1.80.5 cloud. The current workaround isn't ideal and, in some instances, doesn't function as a workaround. Are there any solutions planned for the near future? This is quite critical for our operations.

Hi everyone,
we're investigating this!

Thanks

Thanks Ria! I'm happy I found this thread and saw the workaround mentioned, as I was about to post about this very same problem.

This workaround isn't perfect if you have an agent with 10 HTTP request tools. It necessitates creating and managing 10 separate workflows. Furthermore, you can't utilize the core functionality where you intend for the model to determine the query parameters, rendering this workaround impractical.