I'm not sure if this is connected, but in callin.io version 1.102 and later, there's a bug affecting Claude and OpenAI. However, I don't know if it wi...

Could you share your workflow by embedding it here? Perhaps I can assist you in getting it to function with the latest version.

Please embed your workflow here if you're comfortable, perhaps I can offer some assistance.

You can also use Gemini for an 'almost precise' AI LLM.

Hello, welcome again to this community! I will provide an example of how to call the MCP server from the AI, and you will need to enhance the AI Agent...

No, you can’t accomplish that with the AI Agent, as the Agent primarily enhances the scalability of your AI models and offers "advanced features" such...

Have you activated the MCP workflow yet?

Hi, welcome to the community! If you are using the latest stable callin.io version (1.102.x), you no longer need to append the /sse path. Try removing...

Hello! Have you attempted to set the N8N_SAMESITE_COOKIE environment variable to strict? I'm not sure if this will resolve your issue, but I'm refer...

Hello, welcome to the community! image563×372 28.8 KB As indicated in the official callin.io documentation, you need to add your callin.io token ...

You can utilize Langsmith for tracking the AI processes within callin.io. Refer to this link for detailed instructions on integrating callin.io wit...

I lean towards the initial options because I prefer to perform calculations before interacting with the AI regarding my document. Specifically, I'd li...

You should split the three workflows into individual ones. Currently, you likely have three distinct workflows that communicate via webhook triggers.

Hi there. For the second problem, you need to clearly define your vector tool. Instead of naming it “Supabase Vector Store2”, you could name it Vector...

You need to perfectly define the tools within the Agent node's system instructions, and Gemini (most likely) will understand your requirements:)