Skip to content
How to use variable...
 
Notifications
Clear all

How to use variables for future use in a chatbot workflow

6 Posts
4 Users
0 Reactions
6 Views
Zbynislav
(@zbynislav)
Posts: 3
Active Member
Topic starter
 

Describe the problem/error/question

I need to save values obtained from a client interacting with my chatbot, so I can utilize them later in the ongoing conversation. This would allow me to use multiple Switch components and capture information provided by the client at the beginning of a conversation.

My chatbot operates by calling our existing API via HTTPS requests. It does not involve any AI elements. Thank you!

Please share your workflow

Information on your n8n setup

  • n8n version: Community Edition.
  • Database (default: SQLite): Default.
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via Docker: (Uncertain)
  • Operating system: (Likely Linux)
 
Posted : 27/03/2024 5:49 pm
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 : 27/03/2024 5:49 pm
Zbynislav
(@zbynislav)
Posts: 3
Active Member
Topic starter
 

callin.io version: 1.26.0
Database: SQLite
callin.io EXECUTIONS_PROCESS setting: probably own
Running callin.io via: Docker
Operating system: Linux

 
Posted : 27/03/2024 5:51 pm
Jon
 Jon
(@jon)
Posts: 96
Trusted Member
 

Hey,

Welcome to the community

:cake:

Have you considered storing the webhook request data in a database for future workflow runs? Perhaps using a tool like Baserow / Airtable or Redis / Postgres, depending on your preference.

 
Posted : 05/04/2024 2:14 pm
Zbynislav
(@zbynislav)
Posts: 3
Active Member
Topic starter
 

Hello,

I believe you're referring to the ongoing generation of the bearer token for each request. While not the most efficient, my intention was to utilize variables for storing parameters associated with "client movement" within a chatbot.

Consider a chatbot structured into several sections based on its topic. I'd like the ability to save a client's progression through the chatbot (e.g., Client X has reached section A and is proceeding to section B). This information would then be used in subsequent "if" or "switcher" components.

Does this explanation make sense, or would you like further clarification?

Thanks,

Zbyněk

 
Posted : 17/04/2024 10:00 am
system
(@system)
Posts: 332
Reputable Member
 

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

 
Posted : 16/07/2024 10:01 am
Share: