Skip to main content
Treat an AI assistant connected through MCP like an automated operator working inside your ChatbotX workspace. Always establish safety boundaries, verify token capabilities, and require explicit confirmation for state mutations.

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_get and verifying permissions with token_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, or capabilities_get).
  • Validate Before Publishing: When creating or editing conversational automation with Flow Builder tools, compile and test flow graphs with flows_validate before calling flows_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_tools and invoke them via call_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

Instruct your AI assistant to follow this sequence whenever working with production workspace data:
  • 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 full or read_only permission with token_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

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