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
    • 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

Was this helpful?

  1. Scenarios

Card properties

The following properties is possible to add on each card regardless of the type

Ask again

The ask_again property is only valid for input cards and lets you define if you would like to always ask for the inputted value every time the scenario is triggered or if you like to have it stored in memory. As default Ebbot will never ask for a variable that it already has.

[
	{
		"name": "state_1613396374509",
		"component": "ebbot_input_string",
		"properties": {
			"text": "Tell me your name please",
			"output": "name",
			"ask_again": true
		}
	}
]

Database

The database object is used to add data to the database.

"database":{ 
    "first_name": "Emmett",
    "last_name": "Brown"
}

You can define whatever property you like and it's then reachable through either {{ property }} or data['db']['property']

Reaction

With the reaction property you can assign a card as a reaction to an output. A card that has a reaction will only be played the first time the variable is set. This is useful if you would like to add a thank you response when collecting values for instance.

Here is an example of a reaction that says "Thank you" once the user has entered their name. The second time the scenario is triggered none of the cards will be played.

[
	{
		"name": "state_1613396374509",
		"component": "ebbot_input_string",
		"properties": {
			"text": "Tell me your name please",
			"output": "name",
			"ask_again": false,
			"validation": {}
		}
	},
	{
		"name": "state_1613396382298",
		"component": "ebbot_text",
		"reaction": "name",
		"properties": {
			"text": "Thank you"
		}
	}
]

Stop

By using the stop property you can discard all the remaining cards in a scenario. By default this property is set to false.

[
	{
		"name": "state_1613396374509",
		"component": "ebbot_text",
		"properties": {
			"text": "Hello there 😊",
		},
		"stop": true
	}
]

Next

By using the next property you can link to another scenario at a given state. It is useful if you would like to trigger another scenario without using buttons. You can make a trigger to a scenario or to a given state in that scenario.

[
	{
		"name": "state_1613396374509",
		"component": "ebbot_text",
		"properties": {
			"text": "Hello there 😊",
		},
		"next": {
		"scenario": "scenario_name_or_id",
		"state": "state_id" ## OPTIONAL
	}
]

PreviousTransitionNextAI Insights

Last updated 4 years ago

Was this helpful?