Square Connector
Connector status: Live Verified. Tajo runs this connector today.
Illustration · sample data
Sync example
Source
Square
Connector status: Live
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 Square integration
Customers, orders, payments, catalog, and loyalty signals for syncing commerce events into Brevo.
Implementation Overview
Implement a Square 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.
mcp.squareup.com/sse
| Property | Value |
|---|---|
| Integration surface | API + MCP |
| Status | Live |
| Category | Payments |
| Setup complexity | medium |
| Vendor documentation | developer.squareup.com/reference/square |
| Allowed host | Not recorded |
| Base URL | Not recorded |
| OpenAPI schema | raw.githubusercontent.com/square/connect-api-specification/master/api.json |
| MCP server | mcp.squareup.com/sse |
| Last researched | 2026-10-15 |
Useful for customer, order, and purchase-event syncs to Brevo. The official OpenAPI document (square/connect-api-specification, api.json) is what the connector is built on. The MCP endpoint was verified by handshake on 2026-08-07: 401 with RFC 9728 metadata; it is its own authorization server and supports dynamic client registration.
Authentication
-
OAuth 2.0 (MCP mode).
- Authorize: mcp.squareup.com/authorize
- Token: mcp.squareup.com/token
- The authorization server publishes no scope list.
-
Use raw.githubusercontent.com/square/connect-api-specification/master/api.json to generate or validate typed API clients and request models.
-
Validate the MCP server endpoint at mcp.squareup.com/sse and document required headers, auth grants, and tool availability.
-
Keep developer.squareup.com/reference/square 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
- Commerce, payment, or subscription objects
- Events, webhooks, and behavioral activity
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 |
|---|---|---|
customers | bidirectional | source_wins, loop guard none |
orders | inbound | n/a |
catalog_objects | inbound | n/a |
payments | inbound | n/a |
Square is the record of the customer; the one write back (update_customer) carries identity fields and a note, and nothing the connector reads echoes that write as a change of its own.
Mapping To Tajo/Brevo
customers → Brevo contact
Requires: workspace api key.
| Source field | Brevo destination | Via | Note |
|---|---|---|---|
email | email | — | |
firstName | attributes.FIRSTNAME | — | |
lastName | attributes.LASTNAME | — | |
name | attributes.FULL_NAME | — | |
phone | attributes.PHONE | — | |
company | attributes.COMPANY | — | |
addressCity | attributes.CITY | — | |
addressCountry | attributes.COUNTRY | — | |
id | attributes.SQUARE_ID | — | |
createdAt | attributes.SQUARE_CREATED_AT | — | |
updatedAt | attributes.SQUARE_UPDATED_AT | — |
payments → Brevo transactional
Requires: workspace api key.
| Source field | Brevo destination | Via | Note |
|---|---|---|---|
orderRef | id | — | the order the payment paid, else the payment id |
status | status | — | COMPLETED -> completed; APPROVED and PENDING -> pending; CANCELED and FAILED -> cancelled |
totalMajor | amount | — | |
createdAt | createdAt | — | |
buyerEmail | email | — | |
tajo_email_marketing_consent | filter | — | the template is gated on the canonical consent pair, which no Square payment carries: it sends nothing until consent is joined from another source |
Read for context and not projected: orders, catalog_objects.
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.