Skip to content
Allow AI Agent tool...
 
Notifications
Clear all

Allow AI Agent tool to send multiple "return in webhook" responses

5 Posts
4 Users
0 Reactions
6 Views
davidjm
(@davidjm)
Posts: 2
New Member
Topic starter
 

When an AI Agent utilizes tools such as web search via the HTTP Request node, it can take a considerable amount of time to respond to the user. This delay can sometimes cause users to wonder if the AI is still functioning.

Here's a proposed solution:

  1. The AI Agent calls a tool using HTTP Request, named “WebSearch”.

  2. Create a new workflow named “WebSearch”.

  3. Within the Webhook, select the response option as “Using ‘Respond to Webhook’ Node”.
    image

  4. Therefore, when the user inquires about news, the AI Agent should invoke WebSearch and provide two responses:
    a. "wait a moment, please" from within the WebSearch tool.
    b. The outcome from the AI Agent, utilizing the WebSearch result, such as "the news are ..."

However, when I execute the workflow, I only receive one response: "wait a moment, please".

Are there any workarounds to resolve this issue?

 
Posted : 14/07/2024 3:42 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:

Please share these details to help us understand your issue better.

 
Posted : 14/07/2024 3:42 pm
Jon
 Jon
(@jon)
Posts: 96
Trusted Member
 

Hello,

What you're observing is anticipated behavior. You've configured the webhook trigger to respond with the output from the respond to webhook node, and it's functioning as instructed, but this will only occur after the AI agent node has completed its execution.

To display a waiting message, given your use of the webhook node, you would need to implement a custom loading state on your webpage. This could involve actions such as displaying a spinner, sending the request, and then removing the spinner once the request is finished. This is a common approach for managing such processes.

Feel free to ask if you have any further questions.

 
Posted : 19/07/2024 3:14 pm
davidjm
(@davidjm)
Posts: 2
New Member
Topic starter
 

Hi,

Thanks for the suggestion.

 
Posted : 20/07/2024 3:34 pm
system
(@system)
Posts: 332
Reputable Member
 

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

 
Posted : 27/07/2024 3:35 pm
Share: