"Function calling" is a broader concept across the entire AI landscape. Within callin.io, we leverage this principle internally with a more advanced i...

Hi everyone, We're currently streamlining the usage of our AI Agent. If you're using a recent version of callin.io, you'll notice there's now only o...

Hi everyone, we're investigating this! Thanks

You can leverage the AI Agent to format the desired output, and then utilize the standard HTTP request node subsequent to the agent within your workfl...

Hi Could you share a minimal workflow so we can reproduce this?

Hi, You’ll be better off using the Tool Agent for this. We’ll probably deprecate the other Agents at some point.

Apologies for the delayed response. We are investigating this matter, as it might indicate a bug.

Hello everyone, we've just released the fix in version 1.75.1. If anyone could update and test again to see if the issue is resolved, we would greatl...

Hi everyone, good news! We have a fix ready for this, which we hope to release this week. github.com/n8n-io/n8n refactor(Postgres Node): ...

Hi there! Apologies for the late reply – I encountered a bug myself and was unwell for a few days. Haha, anyway, it appears the API indeed retu...

Hi everyone, Ahh, got ya! So I think what’s happening is that you have your HTTP tool configured to expect a JSON response, but the API is not ...

Hi there, Could you please examine the agent's logs for more specifics regarding the error encountered in the HTTP request node? Additionally, kindl...

Hi there! Based on the screenshot you've provided, it appears you're encountering a different error now, and you're utilizing the HTTP request tool ...

Hi there! The code node might return the object correctly, but since it's passed to the AI agent, the agent will default to returning everything as ...

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 ver...