LogoLogo
  • Introduction to the Ebbot Platform
  • Ebbot Platform
  • Bot basics
    • Scenarios
    • Entities
    • Triggers
    • Training center
  • Scenarios
    • Cards and syntax
      • File Input
      • Text card
      • Input
      • Buttons
      • Image
      • File
      • Carousel
      • Location
      • List
      • Contact Agent
      • Rating request
      • Custom component
      • CoBrowsing
    • Transition
    • Card properties
  • AI Insights
    • Setup and Configuration
    • Using the Insights Dashboard
  • EbbotGPT
    • Knowledge
      • Data source transformer
      • Source types
        • File
        • Website scrape
        • Docx file
        • TOPdesk API
        • Sitevision API
        • SharePoint API
          • Create app with Sites.FullControl.All permission in Azure
          • Ebbot SharePoint Postman Guide
        • Confluence API
    • Configurations
    • Persona
    • GPT Evaluation
    • Embedder models
    • EGPT models
  • Custom vocabulary
  • Tutorials
    • Create your first scenario
      • Select a trigger
      • Add bot responses
  • Data Object
  • Release notes
  • For developers
    • Ebbot SDK
    • Safe Exchange API / Vault
    • Subdomain manager
  • EbbotGPT API
  • Chatbot & Live chat
    • Install chat widget
    • Chats API
    • Chat widget API
    • Datasource API
    • Sales tracking for live chat
    • Webhook
      • Incoming webhooks
      • Outgoing webhooks
    • SMS API
      • Authentication
      • Send SMS
      • Errors
      • Encoding
    • Python components
    • Intent detection (NLP)
  • Product guides
    • Product data feeds
    • Install guide
    • Product guide events
      • Product guide user events
      • Received events
      • Send events
    • API & webhooks
    • GA4 integration
    • Klaviyo integration
  • Messenger marketing
    • Install popup
    • API & webhooks
  • For chat agents
    • Ebbot Chat
      • Settings modal
      • Queue
      • Topbar Stats
      • Menu
        • Power-Ups!
        • Quick Replies
  • INTEGRATIONS
    • Ebbot Live Chat in Zendesk
      • Setup guide
    • Active Directory - SAML
    • Configure SAML in Azure
Powered by GitBook
On this page
  • Graphical view
  • Code editor
  • Python component

Was this helpful?

  1. Scenarios
  2. Cards and syntax

Custom component

You can pass data from your scenario to a custom component where you can process it and then return it to the scenario. Or if you like trigger another scenario or state.

Custom components are useful when you want to call an external API or create a ticket or pass data to your own systems.

Graphical view

Select the custom component card in the card selector and select the custom component that you have created. You need to create the component before calling it. When using the graphical mode, you will not be able to pass data to the component.

Code editor

Create a new state and give your component a name. In the example below we named the component test_component You can pass as many variables as you like to the component.

[
    {
        "name": "state_1",
        "component": "test_component",
        "properties": {
            "key": "value1",
            "key2": "value2"
        }
    }
]

Each variable will be accessible through the data object sent to the custom component. In this scenario we will end up with the following two variables:

data['properties']['key'] ## value1
data['properties']['key2'] ## value2

Python component

The platform supports version 3.4 or later.

PreviousRating requestNextCoBrowsing

Last updated 1 year ago

Was this helpful?

You can easily create custom python components. For details on how to create python components .

click here