Skip to main content

Dialog webhooks

A dialog webhook is a webhook that runs as part of a workflow. You add a webhook action to a dialog node, point it at a configured webhook, and the AI Agent calls your endpoint when the conversation reaches that node. The endpoint can return new context variables (to carry data forward) or its own responses (to take control of the agent's reply).

Use a dialog webhook to:

  • Validate information collected from the user.
  • Fetch data from another system, like a customer record or inventory status.
  • Trigger an action with side effects, such as sending an OTP or creating a ticket.
note

This page covers how to wire a dialog webhook into a workflow. To configure the webhook itself (URL, verification token, headers), see Webhooks. For the request and response payload schemas, see Build a webhook.

Add a webhook action to a workflow

  1. Open the AI Agent and pick the dialog where you want the webhook to run.

  2. Drag a Webhook action onto the node, in the position where the call should happen.

  3. Configure the action:

    FieldDescription
    WebhookPick the webhook from the list of webhooks configured on the AI Agent. Only webhooks of type dialog appear here.
    FallbackA text response sent to the user if the webhook call fails or times out. Used as a graceful degradation when fail on error is off.
Webhook action inside a dialog node

Once the action runs, any context variables your endpoint returns are immediately available to the rest of the workflow — condition nodes downstream can branch on them, and other actions can interpolate them into their text.

What gets sent and received

When the action fires, Moveo sends the conversation's full context, the user's input, and the recognized intents and entities. Your endpoint replies with any combination of:

  • Context updates — new or changed variables to carry forward in the session.
  • Responses — a list of reply objects (text, media, carousel, webview, etc.) that the agent will deliver to the user instead of generating its own reply.

Full schemas for the request body, the supported response types, and the rules around updating context are in Build a webhook → Type reference.