WordPress Connector
Connector status: In progress Being built. Not verified yet.
Illustration · sample data
Sync example
Source
WordPress
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 WordPress integration
CMS and publishing platform with REST access to posts, pages, media, users, comments, and taxonomies.
Implementation Overview
Implement a WordPress 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.
developer.wordpress.org/rest-api/
| Property | Value |
|---|---|
| Integration surface | Docs |
| Status | In progress |
| Category | CMS |
| Setup complexity | advanced |
| Vendor documentation | developer.wordpress.org/rest-api/ |
| Allowed host | Not recorded |
| Base URL | Not recorded |
| OpenAPI schema | Not recorded |
| MCP server | Not recorded |
| Last researched | 2026-05-13 |
WordPress ships an official REST API and self-describing route index per site; no single vendor OpenAPI spec or official MCP server is published.
Authentication
-
Keep developer.wordpress.org/rest-api/ 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
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 |
|---|---|---|
posts | inbound | n/a |
pages | inbound | n/a |
contacts | inbound | n/a |
comments | inbound | n/a |
media | inbound | n/a |
engagement_bridge | inbound | n/a |
Mapping To Tajo/Brevo
WordPress has a typed contract, and every resource on it is read for context rather than projected into Brevo. That is a recorded decision, not a gap: no field of this connector currently becomes a Brevo contact, list, or event.
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.