Gate97Docs
Sign up

Custom connectors

When the app you need isn't in the Connector Reference, define a custom connector instead — point Gate97 at your own (or any) HTTP API and use it as an action step in any workflow. Custom connectors are private to your organization; nobody outside it can see or use one you define.

Defining one

From the Custom Apps page, a custom connector needs:

  • Name — how it appears everywhere in the dashboard, including the connector picker in the workflow builder.
  • Base URL — the API's root, e.g. https://api.example.com.
  • Auth type — none, API key (sent as a header you name), bearer token, or basic (username + password).
  • Default request/response format — JSON, XML, CSV, or plain text. Gate97 serializes outgoing bodies and parses incoming responses in whichever format the API actually speaks, so a workflow step can still map fields normally even against an XML or CSV API.

Once defined, it shows up on the Connections page like any built-in app — connect it with the credentials its auth type calls for (or nothing, for none).

Using it in a workflow

A custom connector has one action, available in the workflow builder once you pick it as a step's connector:

  • Method — GET, POST, PUT, PATCH, or DELETE.
  • Path — appended to the base URL, template-able, e.g. /orders?status={{trigger.status}}.
  • Headers — a template-able JSON object of extra headers.
  • Body — template-able JSON, converted to the wire format you configured (XML/CSV/text) before it's sent.
  • Request / Response format — pre-filled from the connector's defaults, overridable per step.

Receiving data (inbound trigger)

A custom connector can optionally accept inbound data too — check Supports inbound trigger when defining it, and choose the format the sender will POST or PUT in. Once a workflow using it is active, its trigger step shows a real webhook URL, secured by an unguessable token embedded in the URL itself rather than a shared secret. Anything sent there is parsed per your chosen format and starts a run — see Webhooks for the full mechanics, which are shared with Stripe's built-in webhook trigger.

SAP Business One, Pantheon ERP, and WordPress

These three connectors appear pre-named on the Connections page but work differently underneath. SAP Business One talks to its Service Layer's real login/session API directly. Pantheon ERP and WordPress are, functionally, pre-named custom connectors — you supply your own server's URL and credentials, then build the exact request in the workflow step yourself, the same as any custom connector — because every installation of those systems is configured differently enough that no single hardcoded integration would work for everyone.