Algolia Connector Code Wiki

Algolia Connector Code Wiki

Page Summary

Integration Profile

Property	Value
Catalog status	OpenAPI
Runtime in Alto	Cataloged
Alto category	Personalization & A/B Testing
Setup complexity	medium
Vendor docs	www.algolia.com/doc/
Primary API host	Vendor-dependent
Last researched	2026-04-12

System Shape

1. Tajo authenticates against Algolia using the available API, MCP, or documented integration surface.
2. The connector reads source objects, events, and operational metadata from Algolia.
3. Tajo normalizes the records into stable external IDs and explicit sync resources.
4. Brevo receives the activation layer: contacts, attributes, lists, transactional sends, campaign triggers, or CRM context.
5. Logs, retries, and partial failures remain visible in Tajo so the integration can be operated safely.

Data Model

• Custom objects and operational metadata

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.

Implementation Map

Area	What to verify
Authentication	Confirm scopes, token lifetime, revocation, and whether OAuth or API key auth is supported.
Pagination	Prefer cursor or updated-at pagination; document offset fallbacks and maximum page size.
Webhooks	Verify signature headers, replay windows, event IDs, and retry behavior before enabling live ingestion.
Rate limits	Capture vendor-specific retry headers and backoff policy in connector smoke tests.
Brevo mapping	Decide which fields become contact attributes, which records become events, and which actions trigger campaigns.

Current Catalog Notes

Official OpenAPI spec drives 11 language SDKs.

API surface captured by Alto:

• Base URL or endpoint: https://github.com/algolia/api-clients-automation
• Documentation: Vendor docs
• Catalog source: /home/ubuntu/alto/src/data/connectors.v2.ts

Tajo Review Checklist

• Does Algolia have a verified auth path for production workspaces?
• Are primary resources mapped to stable external IDs?
• Is historical backfill separated from real-time webhook ingestion?
• Are retries idempotent for creates, updates, sends, and event ingestion?
• Are Brevo contact attributes, custom events, and campaign triggers named consistently?
• Are failure modes visible enough for an operator to resolve without reading code?

Sources

• Vendor documentation
• OpenAPI or schema source
• github.com/algolia/api-clients-automation
• www.algolia.com/blog/engineering/managing-11-sdks-from-one-openapi-spec