Beyond the engineered connectors, xMatix carries a catalog tier: connectors defined as reviewed configuration for REST partners with standard authentication. To an administrator they use the same picker, generated typed configuration form, secret references and resilient HTTP client as built-in connectors. Their Test Connection action is a transport probe: each shipped manifest treats any response below HTTP 500 as reachable, so a green result can include a 401 or 403 and does not prove that the credential or business scopes are valid. Confirm those with a safe read as well.
What a catalog connector provides
- A connection form generated from the connector's declaration — exactly the fields that partner needs, typed and validated, with secret fields handled as secret references.
- Reads that fetch the partner's records and hand the record list (not the raw response envelope) to the next flow step.
- Writes that post a payload to the partner in the shape it expects.
- A test probe that verifies the configured endpoint can be reached and reports its HTTP status. The current manifests do not treat every 4xx as a failed test.
What it does not provide: OAuth token-exchange flows, batch/bulk writes, and paginated multi-page reads. Partners that need those get built-in connectors — which is precisely the boundary between the tiers.
ClearTax GSP (e-invoicing)
For India GST compliance through ClearTax as the GST Suvidha Provider. The current manifest implements two operations: submit an e-invoice to /einvoice/v2/eInvoice, and read e-invoice status by IRN. Although the connector's display name mentions e-way bills, no e-way-bill operation is declared in the shipped manifest; do not design a flow around that capability until the manifest adds the endpoint.
| Field | Notes |
|---|---|
| GSP host | ClearTax's sandbox or production API host — start on sandbox |
| GSTIN | The 15-character GSTIN this connection files for. One connection per GSTIN |
| Owner id | The ClearTax workspace identifier issued at onboarding |
| Auth token | The ClearTax API token, stored as a secret |
The one-connection-per-GSTIN rule matters for multi-GSTIN businesses: each registration files separately, with its own credentials, so model each as its own connection. The test calls the configured health path and accepts any status below 500; follow it with a non-destructive e-invoice-status request to prove the owner id, GSTIN and token together.
HubSpot CRM
Reads and writes HubSpot CRM objects — contacts, companies or deals, chosen per connection — over HubSpot's v3 API. Configuration: the object type, a page size, and a private-app access token stored as a secret. Writes send the payload as the object's properties, so a flow's transform step maps xMatix fields to HubSpot property names.
Shopify Admin
Reads and writes Shopify orders through the Admin API. Configuration: the shop name (the {shop} in {shop}.myshopify.com), the Admin API version, an Admin API access token (secret), and optionally an order-status filter (any/open/closed) and page size. The typical use is pulling orders into xMatix on a schedule for fulfilment and finance.
Zendesk Support
Reads and writes Zendesk tickets over the v2 API. Configuration: your Zendesk subdomain, an agent email, and an API token (secret). Useful for pulling support tickets against customer records, or creating tickets from xMatix events through an outbound flow.
Using them in a flow
Catalog connectors slot into flows like any other: a connector-read source pulls the partner's records (already unwrapped to a list), a transform maps fields, and a sink writes into xMatix — or the mirror image for outbound. Reads return one page per run at the configured page size, so for large backfills prefer a one-time import and let the scheduled flow carry the ongoing changes.
Common questions
How is this different from the generic HTTP/REST connector?
The generic connector is a blank slate: you supply URLs, headers and auth on every use. A catalog connector packages one partner's specifics — host layout, auth scheme, request shapes and where records live in the response — behind a typed form. Required fields are caught in the form, but provider-side credential, scope and payload mistakes still surface in a test read or run. Both paths use the same retry and secret machinery.
Can these power a sync profile?
No — sync profiles require a sync-capable provider (currently the Salesforce, Zoho and Tally families). Catalog connectors are used in directly-authored flows: scheduled pulls, event-driven pushes, staged imports. The practical difference is that change detection, conflict handling and the record ledger are yours to arrange — upsert write modes and external keys do most of that work.
We use a REST system that is not listed — what are our options?
Two. Today: the generic HTTP/REST connector reaches any JSON-over-HTTPS API with header-based auth, at the cost of hand-writing the request shapes in your flow steps. Longer-term: partners with clean REST APIs and standard auth are candidates for the catalog — raise it with your xMatix contact, since adding one is a reviewed configuration exercise rather than a product build.
Is the ClearTax connector all we need for e-invoicing?
It is the transport. The connector submits what your flow sends and returns what ClearTax answers; building the compliant e-invoice payload from your invoice data is the flow's transform step, and your ClearTax onboarding (owner id, GSTIN registration, token) is a prerequisite. Plan the payload mapping as part of the implementation.