WotNot

The HTTP request block calls external REST services with GET, POST and PUT methods, authentication headers and JSON or mapped form bodies. Response fields can be saved into flow variables for later steps. AI functions choose an API or JavaScript handler from its description and collect missing parameters before execution. Native connectors also create helpdesk tickets and calendar bookings. Function calling and HTTP requests require Premium or Enterprise.

Sourcehelp.wotnot.io/build/integrations/http-request-apiread 2026-10-20

The visual builder combines an AI agent with action blocks and intent based exit paths. An agent normally loops inside its block until a configured condition selects another path; Execute Only Once instead continues immediately to the next step. A demo booking path can require name and email before entering the calendar flow, while a request for staff routes to live chat. Functions supply live data or external changes within that conversation process.

Sourcehelp.wotnot.io/build/action-blocks/agentread 2026-10-20

Knowledge bases combine website domains, sitemaps, selected URLs, uploaded files and pasted text. Domain imports support a refresh frequency that applies to child pages, with individual overrides available. Documents are divided into retrievable chunks supplied to the selected model when answering. Supported uploads include CSV, spreadsheets, text, PDF and Word files up to 5 MB. Operators can inspect source details and remove irrelevant pages from the maintained collection.

Sourcehelp.wotnot.io/build/knowledge-baseread 2026-10-20

Staff can inspect an active chatbot conversation and use Join conversation to take control and reply. Agent paths also route requests for a person into live chat, carrying the conversation to the support team. The Premium copilot drafts suggested responses for staff to edit and send. Oversight centers on transfer, manual takeover and response assistance; external function calls do not pass through a dedicated approve or reject queue before execution.

Sourcehelp.wotnot.io/monitor/live-chatread 2026-10-20

Enterprise customers can use SAML 2.0 single sign on, and every account supports two factor authentication. Secret variables hold API credentials encrypted at rest and hide saved values from teammates, administrators included.

WotNot holds its own SOC 2 Type 2 report and ISO 27001 certification, separate from the accreditations of the Oracle data centers it runs on, and shares SOC 2 audit summaries on request.

Regular penetration tests by certified testers back the program, with findings summaries offered to Enterprise customers, alongside TLS transport, separate credential storage and handling of deletion requests.

Sourcewotnot.io/securityread 2026-10-20

HTTP request logs record each attempt with its status, retry number, request details, response or error and execution timestamp. Operators open these logs from the HTTP Request integration to inspect calls made by their flows. Test Bot and Live Chat also expose chronological conversation logs with model details, latency and message flow. The function test view shows detected arguments and outputs, making failed tool execution inspectable alongside the conversation.

Sourcehelp.wotnot.io/build/integrations/http-request-apiread 2026-10-20

Conversation variables hold selections, intermediate results and other temporary values until the session ends, when they reset. Contact variables preserve names, email addresses, preferences and lead status across conversations with the same visitor, always holding the latest value written. Variables can be archived, and a chat history variable carries the current transcript. What persists between visits is the contact record itself; the agent keeps no separate store of what it learned about a customer, with retention or deletion controls of its own.

Sourcehelp.wotnot.io/build/interface/variablesread 2026-10-20

Customers can run the platform in WotNot's public cloud, in a private cloud or on their own premises, with on premises installation and a review of the deployment included in Enterprise. The managed service runs on Oracle Cloud Infrastructure, and the security page names data centers in the United States, Europe, Abu Dhabi and the United Kingdom, while its encryption section places stored data in Chicago. Static IP addresses let customers allowlist the service in their own firewalls.

Sourcewotnot.io/pricingread 2026-10-20

The builder offers editable templates for customer support, lead generation, appointment booking and property showcasing. Customers select a template by use case or industry and adapt its conversation blocks. The appointment template supplies date and timeslot selection, contact collection and confirmation. These are starting conversation flows; teams add their own knowledge sources, agent blocks and connected actions when they want open ended AI responses and business specific execution.

Sourcewotnot.io/blog/how-to-create-a-chatbotread 2026-10-20

Inbound customer messages start the configured conversation flow through its Trigger block. Web deployments can initialize contact and conversation variables from query parameters or a JSON session payload, while messaging channels supply the incoming response. Outbound bots extend the same builder to proactive conversations. Customers select the channel and trigger conditions when creating the bot, and can also start a conversation from their own application through the API.

Sourcehelp.wotnot.io/build/action-blocks/triggerread 2026-10-20

The agent configuration lets customers select models from OpenAI, Anthropic and Google Gemini, with custom models available on Enterprise. Maximum response tokens and temperature can be set for the chosen agent. Billing varies by the selected model's credit rate and by input and output token volume. Function tests also permit a model selection, so teams can inspect responses from the configuration they intend to use before deploying the flow.

Sourcehelp.wotnot.io/build/action-blocks/agentread 2026-10-20

Developers can publish a bot on the API channel and run its conversation logic in a custom application. Authenticated REST endpoints start a conversation and submit subsequent visitor messages using bearer tokens. The start request accepts a bot key, an external visitor identifier and contact, system and conversation variables. Message contracts cover text, button selections, files and JavaScript results, allowing an external interface to advance the same deployed flow.

Sourcehelp.wotnot.io/deploy/publishing-agents/apiread 2026-10-20

Test Bot opens the current conversation flow in a preview drawer, and a block level Test control starts from a selected point so builders can exercise changed steps. Functions have a Save and Run test view with detected arguments, generated output and a model selector. HTTP requests can also be tested before use. Testing remains a manually driven sequence of queries and inspections, without a stored test suite that replays and scores customer scenarios automatically.

Sourcehelp.wotnot.io/deploy/testing-the-chatbotread 2026-10-20

Website crawling prepares source material for the agent's knowledge base. Its settings can wait for page load, wait for a CSS selector or execute supplied JavaScript to avoid indexing unwanted popups. The support agent itself works through conversation blocks, API requests and connected integrations. An embedded chat widget provides its user interface; it does not give the agent a browser session for navigating websites, clicking through applications or controlling a desktop.

Sourcehelp.wotnot.io/build/knowledge-baseread 2026-10-20