Square Connector

Connector status: Live Verified. Tajo runs this connector today.

Illustration · sample data

Sync example

Review one record

Source

Square

Connector status: Live

Destination

Your other tool

Connector status: Custom tool

Source fieldDestination fieldSample value
record.id source_id record_1042
record.updated_at updated_at 2026-10-18T08:00:00Z
record.value value sample_value
  1. Draft
  2. Review one record
  3. 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.

Payments
SquareAPI / MCP / docsTajo connectorauth, mapping, syncretries, logs, checksBrevo activationcontacts, events, campaignsbackfill, webhooks, validation
Square connector flow from source system to Tajo mapping and Brevo activation.

Implementation Overview

Build target

Implement a Square connector that authenticates to the vendor surface, normalizes source records in Tajo, and activates eligible data in Brevo.

Current status

Treat this as an implementation guide. Build and validate the auth, mapping, sync, and operations paths before production use.

Primary surface

mcp.squareup.com/sse

PropertyValue
Integration surfaceAPI + MCP
StatusLive
CategoryPayments
Setup complexitymedium
Vendor documentationdeveloper.squareup.com/reference/square
Allowed hostNot recorded
Base URLNot recorded
OpenAPI schemaraw.githubusercontent.com/square/connect-api-specification/master/api.json
MCP servermcp.squareup.com/sse
Last researched2026-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

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

ResourceDirectionConflict handling
customersbidirectionalsource_wins, loop guard none
ordersinboundn/a
catalog_objectsinboundn/a
paymentsinboundn/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 fieldBrevo destinationViaNote
emailemail—
firstNameattributes.FIRSTNAME—
lastNameattributes.LASTNAME—
nameattributes.FULL_NAME—
phoneattributes.PHONE—
companyattributes.COMPANY—
addressCityattributes.CITY—
addressCountryattributes.COUNTRY—
idattributes.SQUARE_ID—
createdAtattributes.SQUARE_CREATED_AT—
updatedAtattributes.SQUARE_UPDATED_AT—

payments → Brevo transactional

Requires: workspace api key.

Source fieldBrevo destinationViaNote
orderRefid—the order the payment paid, else the payment id
statusstatus—COMPLETED -> completed; APPROVED and PENDING -> pending; CANCELED and FAILED -> cancelled
totalMajoramount—
createdAtcreatedAt—
buyerEmailemail—
tajo_email_marketing_consentfilter—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.

Sources

Request early access

Enter your first name and email address. We will email you a link to confirm your request for Tajo access.

AI Assistant

Hi! Ask me anything about the docs.

This page as Markdown: square.md

Loading Markdown…