Everything you need to take a workflow from plain-English description to a running AI assistant: how schema generation works, how to connect each major assistant, and how access control, tokens, and the OpenAPI contract fit together.
ChatData Sync gives your AI assistant a private, structured place to read and write data. You describe what you want to track in plain English, ChatData Sync generates the data model and assistant actions, and you connect your assistant with a single copy-paste step.
For the full conceptual overview, see How it works.
A good description names the things you want to track and how they relate. You do not need technical vocabulary — entity names, fields, and relationships are inferred.
Example:
Track customers and their vehicles. Each vehicle can have
multiple repair orders. Each repair order includes inspection
findings, parts used, an estimate with line items, customer
approval, and technician notes. Track open vs. completed
orders and which invoices are unpaid.Schema descriptions are normalized and scanned for prompt-injection patterns before being sent to the schema generator. See Security for details on input hardening.
Before any data is created, you see the full structure — tables, fields, types, and relationships. You can adjust field names, remove tables you do not need, or approve as-is.
Once approved, the tracking space is live immediately. The data model, role-based access policy, assistant action endpoints, and OpenAPI contract are all generated together.
Each tracking space generates two connection options. Pick the one your assistant supports.
Paste a single connection string into a custom GPT's Actions settings. Ready in under two minutes.
Register your tracker's MCP endpoint with a scoped token in Claude.ai or the Anthropic API.
Use the generated OpenAPI contract to register the tracker as a Gemini tool.
The same contract works for any client that consumes OpenAPI 3.1 specs and bearer tokens.
Every tracking space exposes an OpenAPI 3.1 specification that mirrors the generated data model. The contract is what assistants use to discover available actions: create a record, list records, fetch by ID, patch, and delete.
The reference spec for the public actions surface is available at /openapi.actions.json. Your tracking space provides a project-specific contract under /api/v1/projects/{projectId}/openapi.json.
Account-level operations (creating trackers, schema generation) require a Firebase ID token. Assistant access uses a project-scoped API key passed as x-api-key. The key authorizes sync operations on one specific tracker only — it cannot reach your account or any other tracker.
Keys can be rotated from the tracker's settings. Rotation is rate-limited and requires the existing key. Once rotated, the previous key is invalidated immediately and any assistant configured with it must be reconnected.
Annual billing saves 15–17%. All plans include CSV export. See Pricing for the full breakdown.
Request body size, object depth, field count, and string length limits are enforced on every endpoint. Endpoint-specific rate limits apply to AI, schema, sync, and key rotation routes.
The full conceptual picture: problem, three-step setup, and what gets generated.
Tenant isolation, scoped tokens, default-deny Firestore rules, and prompt sanitization.
Real workflows including auto repair, service businesses, and assistant integrations.
Common questions about setup, pricing, supported assistants, and data handling.
The longer-form explanation of why structured assistant data matters and how ChatData Sync delivers it.
How ChatData Sync compares to spreadsheet-style tools for AI-assistant workflows.
Describe your workflow in plain English. Review the generated schema. Connect your assistant. The Free plan includes one tracking space and 200 assistant actions per month.
Start free