Core Operational Rules
AI assistants need valid workspace credentials and structured operational procedures to interact safely with ChatbotX resources. Configure your AI assistants with the following principles:- Discovery First: Start every session by querying workspace context with
capabilities_getand verifying permissions withtoken_get. Do not make assumptions about available tags, flows, channels, or fields. - ID Resolution Over Names: When performing actions on contacts, tags, custom fields, or flows, look up and verify the exact internal ID first (for example using
contacts_get,contacts_list, orcapabilities_get). - Validate Before Publishing: When creating or editing conversational automation with Flow Builder tools, compile and test flow graphs with
flows_validatebefore callingflows_publish. - Meta-Tool Discovery: For specialized API endpoints outside the 43 default tools (such as discount coupons, bot fields, or billing data), guide the AI to query
search_toolsand invoke them viacall_tool. - Draft and Review: For outbound communications, mass tagging, or bulk updates, have the AI draft the action and display target recipients for human review before execution.
Human-in-the-Loop Safeguards
Human-in-the-loop workflows ensure the AI assistant prepares, validates, and simulates changes, then pauses for your explicit approval before mutating any workspace data.Standard Safe Protocol
- Display target contacts, current tags, or matching counts before initiating updates.
- Draft message content, template names, and variable payloads before sending.
- Verify whether the active token has
fullorread_onlypermission withtoken_get. - Test on a single test contact before rolling out modifications across larger segments.
- Provide a summary report with execution status and IDs after completing actions.
Natural Language AI Prompts
Use the following production-ready prompt templates to guide your AI assistant across common automation, support, and marketing workflows.1. Workspace Discovery & Capability Check
2. Contact Lookup and Tagging
3. Safe Flow Validation and Publishing
4. Extended Resource Lookup via Meta-Tools
5. Audience Segmentation & Message Draft
Security Best Practices
Use Read-Only Tokens for Analytics & Reporting
Use Read-Only Tokens for Analytics & Reporting
When configuring AI assistants for audit, dashboard reporting, or conversation analytics, issue a workspace token with
read_only scope in Settings > Integrations > Workspace token. This guarantees that the assistant cannot accidentally delete contacts, publish flows, or dispatch broadcasts.Rotate Tokens Periodically
Rotate Tokens Periodically
If an AI client configuration file (
claude_desktop_config.json, .antigravity/settings.json, or environment files) is committed or shared across team members, revoke the old token immediately in your dashboard and issue a fresh workspace token.Keep Sensitive Identifiers Isolated
Keep Sensitive Identifiers Isolated
Instruct your AI assistant not to output full personally identifiable information (PII) such as payment tokens, raw email addresses, or unmasked credit data into shared chat transcripts or public logs.