LogicDialog
About UsLogicDialogChat PluginSDK
  • What is Logicdialog?
  • Creating your bot
    • Building a conversation flow
    • Finding and editing blocks
    • Selecting the block type
    • Reusing blocks
    • How to change a block type
    • Organising blocks by topic
    • Removing content
    • Buttons
    • Forms
    • Previewing your bot
    • How to write your content
  • Training
    • NLP
    • Creating Intents
    • Creating Entities
    • Using Intents
    • Review questions
    • Testing Intents
  • Look and Feel
    • Standard text
    • Bot Icon
    • Opening Hours
  • Live Agents
    • Agents & Departments
    • Department Routing
    • Live conversations
    • Notifications
  • Integrations
    • Webhooks
    • Zapier
    • WhatsApp
    • Google Business Messaging
    • MS Teams
    • Facebook
    • Analytics APIs
    • Importing knowledge
      • Importing Word Documents
  • Fundamentals
    • Blocks
    • Analytics
    • Utterances
    • Intents
    • Entities
    • Events
    • Forms
    • Webhooks
    • Chat Plugin
  • Support
    • Getting support
    • Raising Tickets
    • Changes to Authentication Provider
    • Enabling Browser Notifications
    • End of support for chat plugin installer
    • Important update: Action required for live agents
Powered by GitBook
On this page
Export as PDF
  1. Fundamentals

Webhooks

PreviousFormsNextChat Plugin

Last updated 3 years ago

There are times when you want the content of a bot to be dynamic. This might be either to fetch some information, or even to save the result of the Forms that the user has completed. In order to "call out" or integrate with other platforms and systems, we have Webhooks.

A Webhook is an API that you can send data to, and in this case it is something that is accessible via a HTTP POST request. As a result, to use a webhook you will need a URL that will receive the information. You can specify this under the Webhook part of the Settings page.

Think of the Webhook Endpoint as an address where you'd like to post a letter to. Inside the letter is the contents of the form that the user has completed.

Once you've setup the webhook, any Function blocks you have in your content will call out to this URL and pass the relevant data with it. As there is one webhook URL per bot, you may need a way to distinguish between one event and the other. We do this by specifying a handler name in the settings of a block.

You can specify any handler name you like, however you then use this name to differentiate between events. By doing so you can have one webhook that supports handling the events from two different blocks.

For more information about building a API that can handle these webhook events, please read our WBB SDK documentation which provides examples and more details.

Quick StartSDK
Logo