Skip to content
AI Agent in callin....
 
Notifications
Clear all

AI Agent in callin.io Not Passing sessionId to Workflow Tool – How to Fix?

4 Posts
4 Users
0 Reactions
4 Views
donpollo
(@donpollo)
Posts: 1
New Member
Topic starter
 

I have an AI agent that forwards a conversation to a “callin.ioworkflowtool”.
This conversation originates from the integrated chat within callin.io, represented by {{ $json.chatInput }}.
I am storing this conversation in a Windows Memory Buffer, which assigns an ID through the variable {{ $json.sessionId }}.
However, when invoking the workflowtool, the AI agent is only transmitting {{ $json.chatInput }}, despite my explicit instruction in the system prompt to send {{ $json.chatInput }} + {{ $json.sessionId }} to the workflowtool.
I have included an image illustrating what the workflowtool receives when a message is sent from the chat. As observed, there is no mention of the memory ID.
This is crucial because, to implement memory within the workflow
tool, I need to supply the sessionId from the parent node.
Any assistance with this matter would be greatly appreciated!

 
Posted : 20/02/2025 10:07 am
n8n
 n8n
(@n8n)
Posts: 97
Trusted Member
 

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

  • 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:
 
Posted : 20/02/2025 10:07 am
jpvanoosten
(@jpvanoosten)
Posts: 4
New Member
 

You can achieve this by utilizing an expression within your Workflow Tool:

This action will transmit the session ID to the workflow you are invoking. Ensure that the workflow is configured to accept it by defining the necessary fields in the Workflow Execution Trigger:

Hopefully, this is helpful!

 
Posted : 21/02/2025 8:30 am
system
(@system)
Posts: 332
Reputable Member
 

This thread was automatically closed 7 days following the last response. New replies are no longer permitted.

 
Posted : 28/02/2025 8:30 am
Share: