Getting Session ID in Webhooks

I'm not quite sure I follow your problem. Could you please provide more details?

However, since you're setting the session ID at the start, wouldn't it be possible to utilize that?

Hi,

Thanks for the prompt response. Attached is a Voiceflow implementation where five GET API calls are made to the callin.io webhook. The user interacts with a chatbot to ask a series of questions (5). For each of these calls, a new sessionID is unfortunately generated. Instead, I was hoping for all of them to share the same session_ID. Please let me know if you have any further questions.

I understand. The session_id can be any identifier.

You can set it to be:

• A username
• A phone number
• A UUID

Essentially, whatever suits your needs.

Therefore, within Voiceflow, you'll need to transmit a session_id along with the message.

Utilize this session_id within your buffer memory, which is associated with the AI Agent.

Hi,

Thanks for the response. I did implement the solution by sending sessionid with the message. However, I believe the sessionid should be unique with every chat. In my case, I keep having the same session_id even after logging out and then logging in again.

Please provide guidance on this.

Oh, I understand now. I initially thought you intended to maintain the same session ID.

If Voiceflow does not modify the session_id, here are two potential approaches:

1. Implement logic in Voiceflow to generate the UUID there and transmit it to callin.io

This method would give Voiceflow control over the UUID. You would generate and refresh the UUID within Voiceflow.

2. Generate the UUID in callin.io and store it in a database

You can utilize the Crypto node to generate a random UUID.

However, you would need to store this in a database for repeated use.

My suggestion is to associate an expiration date with the UUID in the database. Consequently, if the UUID has expired for a specific username/phone number, you would generate a new one using the Crypto node.

Does this approach seem logical?

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