DocsBot AI enables the creation of custom chatbots trained on your documentation, facilitating automated customer support and content generation.
DocsBot AI enables the creation of custom chatbots trained on your documentation, facilitating automated customer support and content generation. On Nagent, DocsBot AI is exposed as a fully-configurable ai chatbots integration that any agent can call — 38 actions, and API key authentication. No code is required to wire DocsBot AI into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use DocsBot AI to automate the kinds of tasks ai chatbots teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire DocsBot AI into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against DocsBot AI, with input parameters and output schema. Drop these into any step of an agent built in Helix.
DOCSBOT_AI_CAPTURE_CONVERSATION_LEADTool to capture lead information by updating conversation metadata and saving the lead. Works whether or not the conversation has been created yet.
Input parameters
The unique identifier of the bot. Obtain this from the List Bots action.
The unique identifier for the conversation. This can be any string identifier, even if the conversation hasn't been created yet.
The unique identifier of the team that owns the bot. Obtain this from the List Teams action.
Dictionary containing lead information such as name, email, phone, company, or any other custom fields you want to capture. All values should be strings.
If true, replaces all metadata. If false (default), merges with existing metadata.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_CREATE_BOTTool to create a new bot within a team. Use when you have a valid team ID and want to provision a new bot.
Input parameters
A descriptive name for the new bot (e.g., 'Customer Support Bot', 'Documentation Helper')
Privacy setting for the bot. 'public' allows anyone with the link to use it, 'private' restricts access to authenticated users (requires paid plan). Defaults to 'public'.
The unique identifier of the team to create the bot in. Obtain this from the List Teams action.
The language code for the bot's responses (ISO 639-1 format). Defaults to 'en' (English).
A brief description of what this bot does or is used for
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_CREATE_SOURCETool to create a new source for a bot. Sources can be URLs, files, sitemaps, and other types. Use when you have content to add to a bot's knowledge base. For file-based sources, first upload the file using the Upload File to Cloud Storage action.
Input parameters
Source URL. Required when type is 'url', 'sitemap', 'youtube', or 'rss'. Must be a valid HTTP/HTTPS URL.
Array of question-answer pairs. Required when type is 'qa'. Each item must have both 'question' and 'answer' fields.
Cloud storage file path obtained from the upload-url endpoint. Required when type is 'urls', 'csv', 'document', or 'wp'. Use the Upload File to Cloud Storage action to obtain this path.
Type of source to create. Choose based on your content: 'url' for single web pages, 'sitemap' for site crawling, 'document' for uploaded files, 'urls' for bulk URL imports, 'csv' for CSV files, 'wp' for WordPress exports, 'rss' for RSS feeds, 'qa' for Q&A pairs, 'youtube' for YouTube videos.
Title for the source. Required when type is 'document'. For other types, will be auto-generated from the URL if not provided.
The unique identifier of the bot. Obtain this from the List Bots action.
The unique identifier of the team. Obtain this from the List Teams action.
Schedule interval for automatic source refresh.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_CREATE_WEBHOOKTool to create a new webhook subscription for a bot. Use when you want to receive real-time notifications for specific events (lead.created, deep_research.done, conversation.escalated, conversation.rated). The target URL must be publicly accessible and support HTTPS.
Input parameters
A descriptive name for the webhook subscription to help identify its purpose
The unique identifier of the bot to create the webhook for. Obtain this from the List Bots action.
List of event types to subscribe to. Available events: lead.created, deep_research.done, conversation.escalated, conversation.rated
Origin identifier for tracking the source of the webhook (e.g., 'zapier', 'composio', 'custom')
The unique identifier of the team. Obtain this from the List Teams action.
The URL where webhook payloads will be delivered (must be publicly accessible HTTPS endpoint)
When the webhook subscription expires in ISO 8601 format (e.g., '2024-12-31T23:59:59Z'). Leave empty for no expiration.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_DELETE_BOTTool to delete a specific bot by its ID. Use after confirming the bot ID is correct to permanently remove a bot from the system.
Input parameters
The unique identifier of the bot to be deleted. Can be obtained from the List Bots action.
The unique identifier of the team containing the bot. Can be obtained from the List Teams action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_DELETE_CONVERSATIONTool to delete a specific conversation by its ID. Use after confirming the conversation ID is correct to permanently remove a conversation. Requires edit permission.
Input parameters
The unique identifier of the bot containing the conversation. Can be obtained from the List Bots action.
The unique identifier of the team containing the bot. Can be obtained from the List Teams action.
The unique identifier of the conversation to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_DELETE_LEADTool to delete a specific lead by ID. Use after confirming the lead ID to permanently remove a lead record from the system.
Input parameters
The unique identifier of the bot. Can be obtained from the List Bots action.
The unique identifier of the lead to delete.
The unique identifier of the team. Can be obtained from the List Teams action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_DELETE_QUESTIONTool to delete a specific question from history. Use after confirming the question ID to permanently remove a question log entry from the system.
Input parameters
The unique identifier of the bot. Can be obtained from the List Bots action.
The unique identifier of the team. Can be obtained from the List Teams action.
The unique identifier of the question to delete. Can be obtained from the List Questions action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_DELETE_SOURCETool to delete a specific source from a bot by its ID. Use after confirming the source ID is correct to permanently remove a source from the bot's knowledge base.
Input parameters
The unique identifier of the bot. Can be obtained from the List Bots action.
The unique identifier of the team. Can be obtained from the List Teams action.
The unique identifier of the source to delete. Can be obtained from the List Sources action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_DELETE_WEBHOOKTool to delete a webhook (unsubscribe) by its ID. Use after confirming the webhook ID is correct to permanently remove a webhook subscription.
Input parameters
The unique identifier of the bot. Can be obtained from the List Bots action.
The unique identifier of the team. Can be obtained from the List Teams action.
The unique identifier of the webhook to delete. Can be obtained from the List Webhooks action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_DOCSBOT_CONVERSATION_TICKET_CREATIONGenerates a structured support ticket from a Chat Agent conversation. Use this tool to convert an existing bot conversation into a formatted helpdesk ticket containing a subject line and message body written from the user's perspective. Prerequisites: - Requires a conversation created via the Chat Agent API (not the legacy Chat API) - Requires Standard plan or higher - The conversation must exist and be accessible with the provided credentials
Input parameters
The unique identifier for the bot within the team. Can be obtained from the list_bots action.
The unique identifier for the team. Can be obtained from the list_teams action.
The unique identifier for the conversation to generate a ticket from. Must be from a conversation created via the Chat Agent API.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_GET_BOTTool to fetch details of a specific bot by ID within a team. Use after confirming valid team and bot IDs.
Input parameters
The unique identifier of the bot to retrieve. Obtain this from the List Bots action.
The unique identifier of the team that owns the bot. Obtain this from the List Teams action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_GET_BOT_REPORTSTool to retrieve monthly statistical reports for a bot. Returns question resolution metrics for a selected month. Use this to analyze bot performance and track question resolution trends over time.
Input parameters
Month to get report for in YYYY-MM format (e.g., '2024-06'). If not provided, returns the latest available report.
The unique identifier of the bot to get reports for. Obtain this from the List Bots action.
The unique identifier of the team that owns the bot. Obtain this from the List Teams action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_GET_BOT_STATSTool to retrieve comprehensive statistics and analytics for a bot over a time period or date range. Returns key metrics (resolution rate, deflection rate, time saved), time series data for questions and ratings, distribution data for feedback and escalations, and agent mode conversation analytics. Use after confirming valid team and bot IDs from List Teams and List Bots actions.
Input parameters
The unique identifier of the bot to retrieve statistics for. Obtain this from the List Bots action.
End of date range in ISO 8601 or YYYY-MM-DD format. Must be provided together with start_date. Cannot be used with time_delta.
The unique identifier of the team that owns the bot. Obtain this from the List Teams action.
Start of date range in ISO 8601 or YYYY-MM-DD format. Must be provided together with end_date. Cannot be used with time_delta.
The time period in days to analyze. Common values: 7 (week), 30 (month), 90 (quarter), 365 (year). Cannot be used together with start_date/end_date. Defaults to 30 if no date parameters provided.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_GET_SOURCETool to retrieve detailed information about a specific source by its ID. Use when you need complete metadata about a source including indexed URLs, FAQs, and processing status.
Input parameters
The unique identifier of the bot. Obtain this from the List Bots action.
The unique identifier of the team. Obtain this from the List Teams action.
The unique identifier of the source to retrieve. Obtain this from the List Sources action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_GET_TEAMTool to fetch details of a specific team by its ID. Use when you need full team info including members and settings after confirming the team ID.
Input parameters
The unique identifier of the team to retrieve. Obtain valid team IDs using the List Teams action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_GET_UPLOAD_URLGet a presigned upload URL for uploading files as sources. Use this before uploading large files to DocsBot. The workflow is: 1) Get upload URL, 2) Upload file to the URL, 3) Create source with the file path.
Input parameters
The unique identifier of the bot to upload files for. Obtain this from the List Bots action.
The unique identifier of the team that owns the bot. Obtain this from the List Teams action.
The name of the file to upload (including extension). This will be used as the filename in cloud storage.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_GET_WEBHOOKTool to retrieve details of a specific webhook by ID. Use when you need webhook configuration, delivery status, or subscription details.
Input parameters
The unique identifier of the bot that owns the webhook. Obtain this from the List Bots action.
The unique identifier of the team that owns the webhook. Obtain this from the List Teams action.
The unique identifier of the webhook to retrieve. Obtain this from the List Webhooks action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_LIST_BOTSList all bots for a given team. Returns detailed information about each bot including configuration, statistics, and status. Use this action to discover available bots before performing operations like getting bot details or listing sources.
Input parameters
The unique identifier of the team to list bots for. Can be obtained from the List Teams action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_LIST_CONVERSATIONSTool to list conversation history for a bot with pagination. Returns a limited subset of conversation properties including titles, timestamps, sentiment, and status. Use this to discover conversations before retrieving full details.
Input parameters
Page number (0-indexed). Defaults to 0.
The unique identifier of the bot. Can be obtained from the List Bots action.
Results per page. Defaults to 25.
The unique identifier of the team. Can be obtained from the List Teams action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_LIST_LEADSTool to list captured leads for a bot with pagination and date filtering. Use after confirming valid team and bot IDs. Example: "List leads for bot abc123 starting from 2024-01-01."
Input parameters
Page number (0-indexed). Defaults to 0.
The unique identifier of the bot to list leads for. Obtain this from the List Bots action.
Filter by lead createdAt end time (ISO datetime format, e.g., '2024-12-31T23:59:59Z').
Results per page. Defaults to 50.
The unique identifier of the team that owns the bot. Obtain this from the List Teams action.
Filter by lead createdAt start time (ISO datetime format, e.g., '2024-01-01T00:00:00Z').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_LIST_QUESTIONSTool to list all questions asked of a specific bot. Use after confirming the bot's identifier. Example: "List questions for bot abc123 with status 'unanswered'."
Input parameters
Number of items to return.
The unique identifier of the bot.
Number of items to skip before starting to collect results.
Search term to filter the questions.
Filter by question status.
The unique identifier of the team.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_LIST_RESEARCH_JOBSTool to list all deep research jobs for a bot with pagination support. Use after confirming valid team and bot IDs. Returns details about each research job including status, question, and timestamps.
Input parameters
Page number (0-indexed). Defaults to 0.
The unique identifier of the bot to list research jobs for. Obtain this from the List Bots action.
Number of results per page. Defaults to 25.
The unique identifier of the team that owns the bot. Obtain this from the List Teams action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_LIST_SOURCESRetrieves a paginated list of all sources for a specific bot within a team. Sources are the content (URLs, files, sitemaps, etc.) that have been indexed for the bot's knowledge base. Use this to see what data sources a bot has been trained on.
Input parameters
Page number for pagination (0-based index). Defaults to 0 if not specified.
The unique identifier of the bot. Obtain this from the List Bots action.
The unique identifier of the team. Obtain this from the List Teams action.
Number of sources per page (max 100). Defaults to 100 if not specified.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_LIST_TEAM_MEMBERSTool to list all members of a team including their roles. Use when you need to see who has access to a team and their permission levels.
Input parameters
The unique identifier of the team whose members to list. Obtain valid team IDs using the List Teams action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_LIST_TEAMSTool to list all teams. Use when you need to retrieve every team associated with the authenticated user.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_LIST_WEBHOOKSList all registered webhooks for a bot. Returns webhook configurations including target URLs, subscribed events, and status. Use this action to discover configured webhooks before creating, updating, or deleting them.
Input parameters
The unique identifier of the bot to list webhooks for. Obtain this from the List Bots action.
The unique identifier of the team that owns the bot. Obtain this from the List Teams action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_RATE_ANSWERTool to rate an answer from chat APIs as positive (1), neutral (0), or negative (-1). Use when recording user feedback on bot responses for statistics shown in chat logs.
Input parameters
The unique identifier of the bot. Obtain this from the List Bots action.
The rating value for the answer. Must be 1 (positive/helpful), 0 (neutral), or -1 (negative/unhelpful). Used for recording statistics in chat logs.
The unique identifier of the team. Obtain this from the List Teams action.
The unique identifier of the answer to rate. Obtained from chat API responses or chat logs.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_REFRESH_SOURCETool to refresh a source to re-index its content. Use when a source needs to be updated with the latest content from its origin. Only works with failed sources for retry purposes.
Input parameters
The unique identifier of the bot. Obtain this from the List Bots action.
The unique identifier of the team. Obtain this from the List Teams action.
The unique identifier of the source to refresh. Obtain this from the List Sources action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_SEARCH_SEMANTICTool to perform semantic search on a bot's indexed content. Returns the most relevant source chunks for a query. Use when you need to search the bot's knowledge base without triggering a full conversation.
Input parameters
Balance between keyword and semantic search. An alpha of 1 is pure semantic vector search, an alpha of 0 is pure keyword search. Range: 0-1. Defaults to 0.75.
The search query to find relevant content chunks in the bot's knowledge base.
Number of most relevant results to return. Defaults to 5.
The unique identifier of the bot to search. Obtain this from the List Bots action. Note: the bot must be ready and have indexed sources.
Automatically cut results to a certain number of groups. Can be a boolean (false to disable) or an integer specifying the number of groups. Defaults to false.
The unique identifier of the team that owns the bot. Obtain this from the List Teams action.
Whether to use the bot's glossary to modify the search query. Defaults to false.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_TEST_ESCALATED_WEBHOOKTool to trigger a test delivery of the conversation.escalated webhook. Use to verify webhook configuration is working correctly.
Input parameters
The unique identifier of the bot to test the webhook for. Obtain this from the List Bots action.
The unique identifier of the team that owns the bot. Obtain this from the List Teams action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_TEST_LEAD_WEBHOOKTool to trigger a test lead webhook delivery. Use when you need to test webhook integration for lead capture events. Requires owner or admin permissions.
Input parameters
The unique identifier of the bot. Obtain this from the List Bots action.
The unique identifier of the team. Obtain this from the List Teams action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_TEST_RESEARCH_WEBHOOKTool to trigger a deep research webhook delivery test. Use to verify webhook configurations are working correctly.
Input parameters
The unique identifier of the bot to test research webhooks for. Obtain this from the List Bots action.
The unique identifier of the team that owns the bot. Obtain this from the List Teams action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_TRIGGER_RATED_WEBHOOK_TESTTool to trigger a conversation.rated webhook delivery test for a specific bot. Use when you need to test webhook integration for conversation rating events.
Input parameters
The unique identifier of the bot to test webhook delivery for. Obtain this from the List Bots action.
The unique identifier of the team that owns the bot. Obtain this from the List Teams action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_UPDATE_BOTUpdate a bot's configuration settings such as name, description, model, temperature, and appearance. Only fields provided in the request will be modified; omitted fields remain unchanged. Requires valid team_id and bot_id. Use LIST_BOTS to find available bot IDs first.
Input parameters
New display name for the bot. This is shown in embeds and share links.
Hex color value for the bot's widget theme (e.g., '#1292EE').
OpenAI model for the bot to use (e.g., 'gpt-4o', 'gpt-4o-mini', 'gpt-5-mini').
ID of the bot to update. Required to identify which bot to modify.
Bot visibility setting. Must be 'public' or 'private'.
ID of the team the bot belongs to. Required to identify the bot's parent team.
Language code for the bot (e.g., 'en', 'es', 'jp').
New description for the bot. Shown in embeds and share links.
URL shown as support link after bot replies. Empty string disables it.
Sampling temperature for model responses, between 0 and 2. Lower values are more deterministic.
Custom prompt instructions for the bot's behavior. Only editable on Pro plan and higher.
Whether to show copy-to-clipboard button for bot responses.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_UPDATE_TEAMTool to update specific fields for a team. Use after confirming the team ID when you need to change the team's name or OpenAI API key. Returns the updated team record.
Input parameters
The team name. At least one of 'name' or 'openai_key' must be provided.
The unique identifier of the team to update
The partial OpenAI API key used by the team's bots. At least one of 'name' or 'openai_key' must be provided.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_UPDATE_WEBHOOKTool to update a webhook's status, target URL, label, or expiration date. Use when you need to modify webhook configuration. Requires valid team_id, bot_id, and webhook_id. Only provided fields will be updated.
Input parameters
Label for the webhook to help identify it.
The unique identifier of the bot that owns the webhook. Obtain this from the List Bots action.
Array of event types to subscribe to (e.g., 'lead.created', 'deep_research.done').
The unique identifier of the team that owns the bot. Obtain this from the List Teams action.
The webhook target URL where events will be sent.
The unique identifier of the webhook to update.
ISO 8601 date string for webhook expiration. After this date, the webhook will no longer receive events.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCSBOT_AI_UPLOAD_FILE_TO_CLOUD_STORAGEUpload a file to cloud storage via a presigned URL. Use this tool after obtaining a presigned upload URL from the DocsBot API (GET /teams/:teamId/bots/:botId/upload-url?fileName=FILENAME). The workflow is: 1. Get presigned URL from DocsBot upload-url endpoint 2. Use this tool to upload the file to the presigned URL 3. Create a source using the 'file' path returned from step 1
Input parameters
The file to be uploaded to cloud storage.
Form fields for S3 POST multipart uploads. When provided, triggers multipart POST instead of PUT. Leave empty/null for standard DocsBot uploads which use PUT with Content-Type: application/octet-stream.
Additional headers for the upload request. For DocsBot uploads, Content-Type: application/octet-stream is added automatically for PUT uploads if not specified.
Presigned URL obtained from the DocsBot upload-url endpoint (GET /teams/:teamId/bots/:botId/upload-url?fileName=FILENAME). This URL contains authentication credentials for uploading to Google Cloud Storage.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 51 agents privately built on Nagent that already use DocsBot AI.
Build on Nagent
Connect DocsBot AI to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find DocsBot AI, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, DocsBot AI is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once DocsBot AI is connected, you configure its 38 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop DocsBot AI steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a DocsBot AI event fires, the agent kicks off automatically.
Every DocsBot AI action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While DocsBot AI ships with 38 pre-built ai chatbots actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching DocsBot AI together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build DocsBot AI-based workflows tailored to your business.