| Data type | Description |
|---|---|
| Text | Stores any text input. |
| Number | Stores only numeric digits from 0 to 9. |
| Boolean | Stores only 0, 1, true, false. |
| Date | Stores date formats as DD/MM/YYYY and MM/DD/YYYY |
| Stores email addresses. | |
| Phone | Stores phone numbers. |
| Regex | Stores input based on your validation rule. |
| Variable | Description |
|---|---|
| name | Name of the visitor |
| Email of the visitor | |
| phone | Phone number of the visitor |
| ip_address | IP address of the visitor |
| city | City detected through the IP address of the visitor |
| state | State detected through the IP address of the visitor |
| zipcode | Zipcode detected through the IP address of the visitor |
| country | Country detected through the IP address of the visitor |
| timezone | Browser timezone of the visitor |
| os | System OS of the visitor |
| referrer_url | Referrer domain to the visitor. |
| unsubscribed_phone_numbers | Whether the phone number is unsubscribed from outbound messaging. |
| utm_source | Utm source |
| utm_medium | Utm medium |
| utm_campaign | Utm campaign |
| utm_content | Utm content |
| utm_term | Utm term |
| browser | Browser used during the chat |
| contact_id | |
| bot | Name of the bot the visitor interacted with. |
| browser_language | Language set in the browser. |
| browser | Name of the browser. |
| channel | Name of the channel where the chat took place. |
| contact_created_by | Who created the contact. |
| conversation_url | Link to the conversation. |
| country_code | ISO country code of the country where the chat originated from. |
| created_at | Date when the chat was created. |
| gcal_selected_slot_day | Selected day when booking the meeting on Google Calendar. |
| gcal_selected_slot_time | Selected time when booking the meeting on Google Calendar. |
| timezone | Timezone of the device. |
| url | URL of the webpage where the user is interacting with the bot. |
| chat_history | Includes the transcript of the conversation so far. |
| URL | Triggers the chatbot based on the webpage the user is on. E.g., “URL contains pricing” or “URL equals https://wotnot.io” |
| Browser language | Uses the user’s browser language to trigger a chatbot. E.g., “Language is French” |
| Date range | Activates the chatbot only within a specific date range. Useful for seasonal campaigns or special announcements. |
| Keyword | (WhatsApp & SMS only) Triggers when a user sends a specific keyword. E.g., “Book appointment” |
| Button payload | (WhatsApp & SMS only) Triggers when a user clicks a button on a template message sent by the business. |
# Buttons Buttons offers a rich UX for users by showing them a list of predefined options to choose from. This makes the chat more conversational.
## Some more button settings ### Search Enabling it shows a searchbox on top of the list of buttons, so that users can easily find the option they are looking for. This is really helpful when you have a huge list of buttons.
Preview of reply button on WhatsApp
### Header: Header is usually the standout portion of the message. Usually, it consists of the heading text or a cover image. Type of headers that you can configure;
| Text | Add a static text displayed in ‘Bold’ Example: “Welcome to WotNot” |
| Media (Static) | Add a static text displayed in ‘Bold’ Example: “Welcome to WotNot” |
| Media (Dynamic) | Send a dynamic image, video or file by using a variable. The variable needs to contain a publicly hosted file URL. Example: Invoices or personalised images with name. |
| Image | A cover image for each card. |
| Card title | Title of the card. |
| Card description | Brief description of the card. |
| Buttons | Call to action buttons for each card. You can add a max of 2 buttons. Button types: Branch: On click, moves the chat to the next step in the flow. URL: Opens a URL on the browser; flow ends at that point. |
Prompt section when creating a Agent
Function section when creating a Agent
Path section when creating a Agent
Book Demo Path * Path Name: Schedule Product Demo * Description: Trigger this path when the user expresses interest in booking a product demo or meeting. Look for phrases such as “I want to book a demo,” “Can I schedule a meeting to see the product?” or “How can I try the product?” * Required Variables: * Name * Email * Variable Descriptions: * Name: Collect the user’s full name so the meeting can be scheduled properly. * Email: Capture the user’s email to send demo details and confirmation. Ensure the email is in a valid format (e.g., contains @ symbol and proper domain). This path ensures that when a user wants to book a demo, all necessary details like their name and email are captured before proceeding with the demo scheduling. ### LLM settings The LLM Settings section allows you to customize how the language model behaves: * **LLM Model** — Choose which language model (e.g., GPT-3, GPT-4) you want to use for generating responses. Models offered: * OpenAI * Anthropic * Google Gemini * Custom Models *(Available on Enterprise plan)* * **Max Tokens** — This setting controls the maximum length of the response. A higher token limit allows the model to generate longer responses, while a lower limit results in shorter replies. * **Temperature** — This adjusts the randomness of the model’s responses. * Lower = safer, more predictable answers * Higher = more creative, varied answers These settings help fine-tune how the AI interacts with users based on your desired response style and length. {% hint style="info" %} You can view all the AI models supported [here](/build/ai-credits) {% endhint %}
LLM settings when creating an agent
> > Determine, whether a clarifying question is required. > > Instructions: > > 1\. Analyse the 'chunks' and the 'user's question' to identify the specificity of the query and the scope of the information in 'chunks'. > > 2\. If the query is broad and the 'chunks' have multiple categories or types, output '#' and guide the chatbot to ask for clarification. > > 3\. If the query aligns well with a specific part of the 'chunks' that provides a comprehensive answer, output '\~'. > > Output format: \[Decision: '\~' or '#', (if '#') then clarification is required. If '#' also, 'specify the type of information or category that would help better address their question. This should be based on 'chunks'. > > Important: if the user's question is likely to have a device specific answer, then you should ask for more information. > > If the user has given a device, then we don't need to clarify. ## Step 2: Store the response in a variable The AI would process the instruction/prompt and generate a response. To get an ideal response, make sure you include in the instructions what kind of response you want to receive. Choose the variable you want to store the response in. [Learn more](/build/interface/variables) For example, if you want to check if the user has asked for a follow up question, you can write the instruction like: > Examine the user's last utterance: > > "\[LAST INPUT]"
> > Determine if the user has asked a follow-up question by looking for: > > \- Interrogative words (who, what, where, when, why, how, etc.) > > \- Phrases that indicate a desire for additional information (e.g., "I would like to know", "Can you tell me about", "I'm interested in", "Could you explain") > > \- Continuation phrases or conjunctions that introduce new topics or questions (e.g., "but", "however", "also", "in addition")
> > \- Output '1' if any of these indicators suggest a follow-up question is present. > > \- Output '0' if no follow-up question is detected.
> > \[Note: Only output '1' or '0' based on this analysis.] # Send an email Sends an email notification to notify about an event occurring in the chat flow. Send an Email action block is used for sending real time email notification to internal stakeholders about the conversation that happened between the chatbot and the visitor. {% embed url="
> > Here are the details: > > Name: { name} > > Email: {email} > > Phone: {phone} > > Description: {info} > > Location: {city}, {country} > > Webpage: {url} {% hint style="info" %} **Note**: You can use variables in the email. {% endhint %} #### Include chat transcript By enabling this, we will include the entire conversation history between the user and the bot till this point. It will allow your team to look at the chat exactly as it occurred. After enabling this, you can still add the body for more context. This will be added at the bottom of the email.
# List Renders a list of items grouped by categories on a drawer. {% hint style="info" %} Available on WhatsApp for the WA API providers: 360Dialog, Meta, and GupShup. {% endhint %} This action block is used for a rich approach of allowing users to choose from a list of options. Most commonly, it is used as an alternative to the [Option](/build/action-blocks/options) action block, as it it not user-friendly and prone to users from the users.
Preview of list on WhatsApp
| Operator | Description | Example |
|---|---|---|
| Equals to | Commonly used when you want to match the value of the variable with the defined value | "City" 'Equals To' "New York" |
| Not equals to | Commonly used when you don't want the value of the variable to be matched with the defined value | "City" 'Not Equals To' "New York" |
| Contains | Commonly used when you want the variable to contain the defined value | "URL" 'Contains' "Web" |
| Does not contain | Commonly used when you do not want the variable to contain the defined value | "URL" 'Does Not Contain' "Web" |
| Is empty | You can use this operator to identify whether the variable is empty or not | "Phone" is 'Empty' |
| Is not empty | You can use this operator to ensure that variable is not empty | "Name" is 'Not Empty' |
Mapping of response into a variable
| Parameter | Snippet | Description |
|---|---|---|
| Summation (Addition) | const additionResult = num1 + num2; |
|
| Subtraction (Minus) | const additionResult = num1 - num2; |
|
| Division (Divide) | const additionResult = num1 / num2; |
|
| Multiplication (Multiple) | const additionResult = num1 * num2; |
|
| Parameter | Snippet | Example |
|---|---|---|
| Set Variable (Conversation) | wn.setConversationVariable(“variable_name”,”variable_value”); Or WotNot.setConversationVariables({“variable_name”:”variable_value”}) | wn.setConversationVariable(“name_wn”,”ABC”); Or WotNot.setConversationVariables({“t1”:”123”}) |
| Set Variable (Contact) | wn.setContactVariable(“variable_name”,”variable_value”); Or WotNot.setContactVariables({“variable_name”:”variable_value”}) | wn.setContactVariable(“name_wn”,”ABC”); Or WotNot.setContactVariables({“t1”:”123”}) |
| Parameter | Snippet | Example |
|---|---|---|
| Length of String | const lengthOfString = “variable_name”.length(); | const lengthOfString = “some_string_content”.length(); //Output: 19 Calculates the number of characters passed/present in the value |
| Get part of a string | const partOfString = “variable_name”.slice(); | const partOfString = “some_string_content”.slice(5);
|
| Tool | Snippet | Example |
|---|---|---|
| Google Analytics 4 | window.dataLayer = window.dataLayer || []; function gtag() { window.dataLayer.push(arguments); } gtag("js", new Date()); gtag("config", "YOUR-MEASUREMENT-ID"); gtag("event", "YOUR-EVENT-NAME", { "send_to": "YOUR-MEASUREMENT-ID" // Additional parameters that you may want to pass }); | window.dataLayer = window.dataLayer || []; function gtag() { window.dataLayer.push(arguments); } gtag("js", new Date()); gtag("config", "123"); gtag("event", "WotNot_Test", { "send_to": "123", "name": "Test", "phone": "123456789", }); |
isFromDateBeforeToDate(fromDate, toDate) {
const fromDateObj = new Date(fromDate);
const toDateObj = new Date(toDate);
return fromDateObj < toDateObj;
}
| Helps to trigger the flow the day specific flow | # Set variable The Set Variable action block lets you assign a specific value to a variable during a conversation flow. As the name suggests, you can define or update a variable with a new value at any point in the chat.# Delay Adds a specified wait time to the flow. Using the delay action block, the chatbot will intensionally show a typing indicator for the specified duration before proceeding to the next step in the chatbot flow. You can add delays from **1s, 2s, 5s, and 10s**. {% embed url="
Advanced crawling criterias
| Provider | Model | Credits per 1K tokens |
|---|---|---|
| OpenAI | GPT 4.1 | 1 |
| OpenAI | GPT 4.1 Mini | 0.25 |
| OpenAI | GPT 4.1 Nano | 0.05 |
| OpenAI | GPT 4o | 0.8 |
| OpenAI | GPT 4o Mini | 0.05 |
| OpenAI | GPT o4 Mini | 1.3 |
| OpenAI | GPT o3 Mini | 0.35 |
| OpenAI | GPT 5.4 | 0.95 |
| OpenAI | GPT 5.4 Mini | 0.3 |
| OpenAI | GPT 5.4 Nano | 0.1 |
| OpenAI | GPT 5.4 Pro | 11.25 |
| Anthropic | Claude Sonnet 4.5 | 1.05 |
| Anthropic | Claude Haiku 4.5 | 0.35 |
| Anthropic | Claude Opus 4.5 | 1.75 |
| Gemini 2.5 Flash | 0.15 | |
| Gemini 2.5 Pro | 0.55 | |
| Gemini 3 Pro | 0.55 | |
| Gemini 3 Flash | 0.2 | |
| Gemini 2.5 Flash Lite | 0.05 |
{% hint style="info" %} Ensure to grant all the necessary permissions on the account permission screen. {% endhint %} ## Creating records To create a record on Google Sheets, here are the steps to be followed: ### Step 1: Choose your Google Sheet After choosing your Google account, and action as “Create records”, you need to choose your desired “Sheet” from the dropdown. {% hint style="info" %} You will only see the sheets that you have edit access to. And when choosing a sheet, WotNot automatically creates a new worksheet under which the data will be pushed. {% endhint %} ### Step 2: Choose the variables you want to send Now choose the variables that you want to push to the selected Google Sheet. Each selected variable will be added as a column on the sheet. For example, if you want to push lead information you would select the following variables: * Name * Email * Phone * City * Country * Created at ## Fetching records You can fetch data from a Google Sheet based on criteria using this action. ### Step 1: Choose the sheet to search Choose the Google sheet and the worksheet that you want to search data from. Enable the checkbox ‘First row contains..’ if the column heading is present. ### Step 2: Add your search criteria Define the search criteria based on which values will be fetched from the Google Sheet. You can choose to add multiple conditions using the “ANY/ALL” operators. For example, you want to fetch the leads whose city is New York and country is United States. * Condition 1: Column=city, Operator=equals to, Value=New York * Condition 2: Column=country, Operator=equals to, Value=United States * Choose the ALL operator, as you need both conditions to hold true. ### Step 3: Saving responses Choose the values from the columns you want to save into variables. Map them out, and the values fetched will be stored inside. {% hint style="info" %} If more than one row gets qualified in the search criteria, the data will be stored in a JSON format in the variable. You can then use the dynamic data action block to parse the data. {% endhint %} For example, if we choose the above condition of city=New York and country=United States, we will receive multiple records as a response. Taking the example of the name field, it would be stored as: ``` [{“name”: “Hardik Makadia”, “name”: “John Doe”}] ``` ## Updating records You can update records on a Google Sheet based on your criteria. ### Step 1: Choose the sheet to search Choose the Google sheet and the worksheet that you want to search data from. Enable the checkbox ‘First row contains..’ if the column heading is present. ### Step 2: Add your search criteria Define the search criteria based on which values will be fetched from the Google Sheet. You can choose to add multiple conditions using the “ANY/ALL” operators. For example, you want to fetch the leads whose city is New York and country is United States. * Condition 1: Column=city, Operator=equals to, Value=New York * Condition 2: Column=country, Operator=equals to, Value=United States * Choose the ALL operator, as you need both conditions to hold true. ### Step 3: Update the data Map the columns you want to update with a value or variable. The column name from the first row of your sheet will be displayed in the column dropdown. # Google Calendar Collaborate with your visitors and make it easy for them to view and book appointments. {% hint style="info" %} Available on the **STARTER** plan and above. {% endhint %} The Google Calendar action block allows visitors to book appointments with you based on availability. To use the Google Calendar, you will go across the following steps: 1. Connect your Google account 2. Create an event 3. Configure the event settings 4. Setup your meeting invite 5. Collect contact details to book ## Step 1: Connect your Google Calendar account 1. Goto Settings > User > Calendar 2. Click "connect your Google account" 3. Choose the calendar in which events will be booked. 4. Choose the timezone of your availability. 5. Set your availability (Timeslots from this will be displayed to visitors) {% hint style="info" %} Make sure you grant all the permissions as requested when connecting your account. {% endhint %} {% embed url="
| Configurations | Description |
|---|---|
| Slot duration | Length of the event. From 5 mins to 120 mins |
| Buffer time | A gap between two events booked from the chatbot, ranging from 5 minutes to 120 minutes. |
| Notice time | Meetings will only be booked X minutes in advance. |
| Limit future bookings | Total days whose slots are visible. |
Measurement ID of a GA4 property
Calendar account configuration page
| Configurations | Description |
|---|---|
| Slot duration | Length of the event. From 5 mins to 120 mins |
| Buffer time | A gap between two events booked from the chatbot, ranging from 5 minutes to 120 minutes. |
| Notice time | Meetings will only be booked X minutes in advance. |
| Limit future bookings | Total days whose slots are visible. |
| Action | Description |
|---|---|
| Create lead | Create a new lead in Salesforce. |
| Create contact | Create a new contact in Salesforce. |
| Create case | Create a new case in Salesforce. |
| Update lead | Updates an existing lead in Salesforce. |
| Update contact | Updates an existing contact in Salesforce. |
| Update case | Updates an existing case in Salesforce. |
| Fetch lead | Fetches details of an existing lead. |
| Fetch contact | Fetches details of an existing contact. |
| Fetch case | Fetches details of an existing case. |
For example, notifying your team about: * New chat from target country * Existing lead speaking with bot * User submitting qualified answers You can even integrate your IP enrichment tools with WotNot, to fetch the potential company details of the visitor speaking with the bot, to send better and personalized integrations. ### Step 1: Connect your Slack workspace Connect your Slack workspace by clicking on “+ Add account”, and choose it from the dropdown. Next, choose the channel that you want to send the notification to.
To format your message, refer to [Slack’s markdown guidelines](https://api.slack.com/reference/surfaces/formatting). \ **Enable ‘Join conversation’**\ Enabling this option, adds a “Join conversation” button at the bottom of your message. Clicking on it, allows the user to jump into the conversation and take over from the bot, to perform a live chat right from the Slack thread created.
**Post on Slack threads**\ If you do not want a new message post always, you can enable this option and enter the thread in which you want the bot to always post Slack notifications. *** ## Live chat for Slack Using this action block, your users can take up live chat with visitors right from their Slack channels itself.
This is particularly useful for sales teams, as they can instantly jump in and take up chats of qualified visitors on their website. Enabling them to be productive and prompt. ### Step 1: Connect your Slack workspace Connect your Slack workspace by clicking on “+ Add account”, and choose it from the dropdown. Next, choose the channel that you want to send the notification to.
Now, whenever this action block is executed you will see a notification on your slack channel with a thread to continue the conversation.
**Chat history**\ On the slack thread, the first thing you see is the historical context of the chat till the point the human handover took place. Messages are tagged as ‘Bot’ and ‘Visitor’ along with the timestamp. **Actions**\ You can perform the following actions: * Reassign chats – Shows a list of users you can reassign the chat too * Send saved reply – Choose and send the saved reply * Create saved reply – Create a new saved reply * Delete saved reply – Delete a saved reply * Notes – Add a note message to the chat thread * Google calendar – Send a calendar event to book a meeting **Close**\ Once you have completed chatting with the visitor, you can hit “Close” on the slack post to close the chat. If not closed, WotNot will automatically close the chat after the session times out.
# Airtable Fetch records from your Airtable. {% hint style="info" %} Available on the **STARTER** plan and above. Available on the **WEB** channel only. {% endhint %} Airtable is a cloud-based database like Google Sheets to store data. This integration allows you to fetch records from your database and dynamically render them as buttons, image carousels, or carousels.
## Step 2: Filter the records you want to fetch Now that your account is connected choose the **base** and **table** from which the records are to be fetched. {% hint style="info" %} You will only see those bases for which you have granted permission during the authentication process. If you do not see your base, reconnect your account by visiting App Market > Airtable. {% endhint %} Next, define the filter crtieria that you want to apply while fetching the records from the selected base and table. The syntax to write the formula is same as what you would use in Airtable. [Learn more about Airtable formulas](https://support.airtable.com/docs/formula-field-reference). ## Step 3: Choose how to render the data Based on your applied filter, the records will be fetched from Airtable. Here you choose how do you want to render the data -- i.e. as buttons, carousel, or image carousel. {% hint style="info" %} Number of records fetched is determined on the formula you define. {% endhint %} ### Show Buttons: You can choose to render the data as a branch/URL button. * **Branch button** - when clicked moves forward in the chat flow. * **URL button** - when clicked opens a URL. 1. Define the question that will be asked when buttons are shown 2. Choose the Airtable column whose data is to be shown as the button text 3. If URL button is chosen, choose an additional field which contains the URL
### Show Carousel: Here we render the details in a carousel format with a set of cards. * Map 'Cover Image' with Airtable field that contains images * Map 'Title' with Airtable field that contains description. This will be the title of the card * Map 'Description' with Airtable field that contains description. This will provide the brief summary about the card. It is best to limit the text here to 2-3 lines * Define action for the buttons. Maximum upto 3 buttons can be added. * Define variable in which the visitor selection will be stored
### Show Image Carousels: Here we display a set of pictures in a carousel format. \ \ You can follow the following steps to configure it: * Select 'Show data' as 'Carousel' * Map 'Image' field with Airtable field that contains images ## Step 4: Store the selected value in a variable Once the button/carousel is displayed, you can choose a variable in which the data will be stored. * If button is chosen, the button text will be stored in the variable. * If carousel is chosen, the carousel title will be stored in the variable. * If image carousel is chosen, no variable support is provided. ### Limitations: The API has a rate limit of 5 request per second per base. If you exceed this rate, your bot will show an error and the visitors will need to wait for 30 seconds before subsequent requests will succeed. # Zendesk Create tickets, fetch ticket status and perform live chat from Zendesk. {% hint style="info" %} Available on the **STARTER** plan and above. {% endhint %} Zendesk is a popular ticketing system used by many organizations. With WotNot's Zendesk integration, you will be able to perform the following actions: 1. Create tickets 2. Get ticket status 3. Live chat on Zendesk ## Create tickets Using this action block, after collecting information from users, your chatbot can create a ticket on Zendesk and acknowledge the user with the created ticket number. For example, you are creating an IT support chatbot that: * Collects user's email address * Category of the problem (Hardware, Software, Networking, Something else...) * Sub-category of the problem (PC not starting, PC stuck ...) * Description of the problem * Files/images to be attached and creates a ticket on Zendesk after collecting these details. ### Step 1: Connect your Zendesk account Connect your Zendesk account by clicking on “+ Add account”, and choose it from the dropdown. * **Account name** - General name for this account. * **Helpdesk URL** - Domain on your Zendesk account i.e.
* Double click on 'DialogFlow' to configure it on the right panel
1. Map the Variable: \ \ Select the variables in which the visitor's inputs are stored. Just like to answer a question, you need a question; similarly, to parse inout to DialogFlow, we send a sentence to them & DialogFlow in return reads the question & sends the matching answer to WotNot
2. Upload JSON file: \ \ Upload the JSON key that you have downloaded in the earlier steps. If you haven't download it yet, refer to this [video tutorial](https://www.loom.com/share/d1d5b0f1849a4afca5aa8ef8775cc796)
* Define actions:\ \ Define the actions to be performed for the Success & Failure scenarios. You will see two ports '+' for Success condition and '+' for Failure condition. \ \ On Success, meaning when an intent is matched on DialogFlow and a success response is received, we have the option to self loop the block or move on to the next step in the flow
On Failure, you can define what should be the next step in the conversation flow, by adding an action block. Obviously, DialogFlow will not always give you expected response & so whenever it fails, you may try to request the input again and loop it back to the flow {% hint style="info" %} We at WotNot recommend you to have the 'Collect Input' action block placed ahead of the 'DialogFlow' action block & store the response from the visitor in the variable. {% endhint %} # Zoho CRM Create a contact record on your Zoho CRM. {% hint style="info" %} Available on the STARTER plan and above. {% endhint %} Zoho CRM integration allows you to create a new contact record in your Zoho CRM account by mapping the information collected by the chatbot with the contact fields in your CRM. ## Connect your account Connect your Zoho CRM account by authorizing the access and choosing the account from the list.\ \ Zoho's authorization will open in a new window. Please make sure that you have not blocked the pop-up window from opening.
## **Map the fields:** You can map the Zoho CRM fields with the variables defined in the bot builder. This way, whatever values stored in WotNot's variables will be mapped against the Zoho fields that you choose here. {% hint style="info" %} The maximum number of fields you can map is capped at 50 {% endhint %} ## Define next steps Every Zoho CRM action block will have two outcomes - Success or Failure. You can define the success and failure actions as per your need. # Zapier Connect your zap with WotNot. {% hint style="info" %} Available on the **STARTER** plan and above {% endhint %} Zapier integration lets you send data to a zap, which initiates its workflow. You can follow the below steps in sequence to successfully integrate with Zapier: ## Step 1: Add the ‘Zapier’ action block in the flow by clicking on ‘+’ Add the Zapier action block on the chatbot flow. {% hint style="info" %} Keep in mind the Zapier integration will be triggered when the flow reaches this action block. {% endhint %}
\
# HTTP request / API Performs an HTTP request with a third-party app's REST API endpoint. {% hint style="info" %} Available on the **PREMIUM** plan and above. {% endhint %} If you want to send data or fetch data from a third-party that WotNot does not have a native integration to, you can use the HTTP request action block. HTTP request allows you to invoke a API endpoint and perform a **GET / POST / PUT** operation. {% embed url="
Expected response when endpoint is invoked
{
"ok": true
}
{
"error": "ROLE_NOT_FOUND",
"ok": false,
"status": 404,
"message": "Role not found for this account."
}
# Website You can instantly launch your chatbot to your website with one click on WotNot. Follow the steps mentioned below if you are looking to add the WotNot chatbot on your website, webpage or web application. {% embed url="
| Meta | /pages/VZzzyOs2kedEqz6sRyGF | ||
| 360Dialog | /pages/KQbokzSB6nmLDXb1BEyd | ||
| Twilio | /pages/9iwvIYmIDreSvShRRjE3 | ||
| GupShup | /pages/TXofloHxhg5niDlOkpYg | ||
| TechAlpha | /pages/NOoo9BnBZoijUAGohz6S |
| Property | Setter | Default | Used For |
|---|---|---|---|
| accentPrimary | setAccentPrimary() | #0075ff | Buttons, headers, links |
| userMessageTextColor | setUserMessageTextColor() | #FFFFFF | User message text & timestamp |
| accentSecondary | setAccentSecondary() | #d4e3ffff | Secondary accents |
| gray8 | setGray8() | #F2F5F8 | Bot message background |
| botMessageTextColor | setBotMessageTextColor() | #1C1C1E | Bot text & timestamp |
| failurePrimary | setFailurePrimary() | #FF0000 | Error messages |
| failureSecondary | setFailureSecondary() | #FFEBEE | Error states |