WooCommerce Connector
Connector status: In progress Being built. Not verified yet.
Illustration · sample data
Sync example
Source
WooCommerce
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.
Tajo’s WooCommerce connector is in progress. The code exists, but it has not yet passed a run against a live WooCommerce store.
A partial run on 14 October 2026 tested only the WordPress plugin, on a local test site. Tajo’s side was not run, because Tajo’s connections accept public HTTPS sites only.
What the code does
- Reads customers, orders, products, product categories, coupons, refunds and product reviews through the WooCommerce REST API. It does not infer marketing consent from a customer record.
- Receives signed WooCommerce webhooks for orders, customers, products and coupons through the Tajo WordPress plugin, which is not published on wordpress.org.
Not available today
- Abandoned-cart recovery
- WordPress multisite installations
- Custom meta fields mapped to contact attributes
Open-Source Implementation Map
This section is derived from official or public repository material discovered for the WooCommerce connector. Use it as the engineering companion to the setup guide above: it shows where the API surface lives, what implementation assets exist, and how Tajo should translate them into reliable Brevo sync behavior.
Repository Snapshot
| Repository | Commit | Languages / formats | Files |
|---|---|---|---|
| wtx-labs/woocommerce-api-openapi-specification | b534704 | YAML (4), Markdown (1), png (1) | 6 |
Integration Shape
graph LR Source["WooCommerce API / repository"] --> Auth["Auth and scopes"] Source --> Objects["Objects, events, and schemas"] Auth --> Tajo["Tajo connector runtime"] Objects --> Tajo Tajo --> Brevo["Brevo contacts, attributes, lists, campaigns"] Tajo --> Ops["Backfill, cursor, retries, logs"]What To Reuse
- WooCommerce REST API specification in OpenAPI 3.0 format
- The WooCommerce REST API specification in OpenAPI 3.0 format.
- 📦 Version Information
-
- Current Version: ‘1.0.0’
-
- OpenAPI Specification Version: ‘3.0’
Tajo Revamp Checklist
- Keep authentication setup aligned with the vendor docs and the public repository’s current API shape.
- Map primary resources into explicit Tajo sync objects with stable external IDs.
- Prefer cursor-based or updated-at incremental sync where the API exposes it; otherwise document the fallback.
- Treat webhook handlers as idempotent and replay-safe, especially for order, contact, ticket, and campaign events.
- Capture pagination, rate limits, retry headers, and partial-failure behavior in connector smoke tests.
- Keep examples small and runnable against sandbox or test-mode accounts.