Execute the HITL Agent without having to ask the u...
# 👀feature-requests
b
Hi everyone, remember @acceptable-gold-88171 that I mentioned I was trying to execute the HITL agent in my bot without having to ask the user for their name and email since these were received and stored in their respective variables through the Zapier trigger. I tried to implement the bot structure you suggested me in order to deploy the HITL agent with the webhook trigger. Even so, when I check the bot's logs, it still complains that it needs the "user.name" and "user.email"
Bot flow⬇
Bot Log⬇
I've thought of several solutions to execute the HITL Agent without having to ask for their name and email again, as it would be very repetitive for the user and wouldn't help keep them engaged in their conversation with the bot: 1.- Add placeholders in the HITL Agent. 2.- Create a Ticket in Zendesk through its integration in Botpress. 3.- Create a Ticket in Zendesk through Zapier. 4.- Add a code that makes the same input to the bot as if it were taking the user's name and email data through Raw Input
.
.
.
1. Add placeholders in the HITL Agent. I'm not sure if it would be possible for the HITL Agent to have placeholders that can be filled with whatever we want, where we could insert the "user.name" and "user.email." Just like when we deploy the "Create a Ticket" card from Zendesk. Would it be possible for the Botpress team to make this happen?
.
.
.
2. Create a Ticket in Zendesk through its integration in Botpress. As a second option, we could create a ticket directly in Zapier using the “Create a Ticket” card. We can fill in the placeholders with the already registered user variables.
The problem is that when I do this, an error appears—a problem that some members of the Discord community also encounter when trying to execute this "Create a Ticket" card.
.
.
.
3.- Create a Ticket in Zendesk through Zapier. Additionally, I have considered the idea of sending all the data to Zapier, and once Zapier receives the trigger, it creates a Ticket in Zendesk. The thing is that I need to send the “user.name,” “user.email,” and the “conversation.SummaryAgent.transcript” so that the person handling the ticket knows the context of the conversation. Here I have tried sending the data to Zapier in two ways: **A)**Through the "Send to Zapier" card. In this card, I send the information using the JSON format: {{ JSON.stringify({ Name: user.name, Email: user.email, Chat: conversation.SummaryAgent.transcript }) }}
**B)**Through a code card, I send the same information to the Zapier webhook The code card in the flow⬇
The problem is that when the trigger receives the information, whether it's with the code card or the "Send to Zapier" card, it receives two inputs. One registers the name and email variables (request C⬇), and the other registers the chat transcription (request D⬇). If the information is not sent to Zapier in a single input, the data cannot be filled in correctly when creating a ticket in Zendesk.
Is there any way to send, either through code or the "Send to Zapier" card, the conversation.SummaryAgent.transcript as if it were text, like the variables user.name and user.email, so that everything is received in the same input?
.
.
.
4.- Add a code that makes the same input to the bot as if it were taking the user's name and email data through Raw Input Lastly, I was thinking that maybe a code card could be added right before the HITL Agent that replicates the conversation the bot might have with the user. This would try to make the input of this code the same as the input the bot would have if it asked the user for their name and email again.
.
.
.
This is everything I've been able to consider and test while trying to avoid repeatedly asking the user about their name and email. All of these have been my own ideas based on my limited coding knowledge, so I'm not sure how feasible any of these solutions are 😅. How does the Botpress team see this? Do you think any of the issues I'm presenting have a solution that would allow the HITL Agent to be executed without having to ask again? @bumpy-butcher-41910 @some-baker-90541 @flat-plumber-75402
3 Views