Chatbase Connector
Connector status: In progress Being built. Not verified yet.
Illustration · sample data
Sync example
Source
Chatbase
Connector status: In progress
Destination
Your other tool
Connector status: Custom tool
Field mapping
| Source field | Destination field | Sample value |
|---|---|---|
record.id | source_id | record_1042 |
record.updated_at | updated_at | 2026-10-18T08:00:00Z |
record.value | value | sample_value |
- Draft
- Review one record
- Approve this version
Statuses describe individual connectors; they do not guarantee this sync is ready. Illustrative fields. Review the actual schema and permissions before a sync runs.
Connector implementation
Build the Chatbase integration
Customer service AI chatbots with leads, contacts and conversations
Implementation Overview
Implement a Chatbase connector that authenticates to the vendor surface, normalizes source records in Tajo, and activates eligible data in Brevo.
Treat this as an implementation guide. Build and validate the auth, mapping, sync, and operations paths before production use.
| Property | Value |
|---|---|
| Integration surface | OpenAPI |
| Status | In progress |
| Category | Messaging & Chatbots |
| Setup complexity | medium |
| Vendor documentation | www.chatbase.co/docs/api-reference |
| Allowed host | Not recorded |
| Base URL | Not recorded |
| OpenAPI schema | www.chatbase.co/docs/api-v2-openapi.json |
| MCP server | Not recorded |
| Last researched | 2026-10-31 |
Two official OpenAPI documents, v2 and the deprecated v1 that alone has leads and contacts (2026-10-31). The API needs a Basic plan or higher and Chatbase has no free plan.
Authentication
-
Use www.chatbase.co/docs/api-v2-openapi.json to generate or validate typed API clients and request models.
-
Keep www.chatbase.co/docs/api-reference linked from the connector runbook so operators can confirm vendor behavior during incidents.
-
Store credentials per Tajo workspace and keep tenant-specific secrets out of connector configuration files.
-
Add a credential smoke test that verifies read access to a harmless resource before running backfills or enabling webhooks.
Data To Sync
Start with these inferred data domains, then confirm exact vendor resources and permissions from the source documentation:
- Contact and identity records
- Campaign, messaging, or audience state
- Tickets, conversations, and support context
The connector should make source records idempotent by keeping a stable key such as a vendor object ID, email address, event ID, ticket ID, order ID, or campaign ID. If the vendor only exposes list APIs, Tajo should store the cursor strategy and replay policy explicitly.
Sync Shape
| Resource | Direction | Conflict handling |
|---|---|---|
leads | inbound | n/a |
contacts | inbound | n/a |
conversations | inbound | n/a |
chatbots | inbound | n/a |
Mapping To Tajo/Brevo
leads → Brevo contact
Requires: workspace api key.
| Source field | Brevo destination | Via | Note |
|---|---|---|---|
email | email | — | |
name | attributes.FULL_NAME | — | |
phone | attributes.PHONE | — | |
id | attributes.CHATBASE_ID | — | |
createdAt | attributes.CHATBASE_CREATED_AT | — |
Read for context and not projected: contacts, conversations, chatbots.
The conventions that apply to every connector — stable external IDs, normalization, backfill and sync strategy, error handling, and the builder checklist — are documented once under “Applies to every connector” on the connector catalog.