Skip to main content
This recipe walks the full connector authoring workflow using the build-a-connector-stripe-clone example as the worked model. You will copy the scaffold, fill in manifest.ts with your vendor’s details, implement the Banking and Screening capability interfaces, run the contract tests, and confirm the package is ready to publish. Audience: engineers who want to plug a new payment rail or compliance vendor into the Glide OSS stack.

Prerequisites

  • The axtior-neobank repo cloned locally with pnpm install run at the root.
  • Node 22+ and pnpm.
  • Read the ConnectorManifest schema before starting — the manifest is the contract between your connector and the registry.

Steps

1. Copy the example scaffold

No scaffolding CLI exists. Copy the working example directly:
The scaffold gives you:
Rename the package in package.json and update the slug in manifest.ts before doing anything else.

2. Write the ConnectorManifest

Edit src/manifest.ts. Every field is validated by the registry at boot and by the M5 CI gate.
isMock: true blocks loading in NODE_ENV=production unless GLIDE_ALLOW_MOCKS_IN_PROD=true is set. Validate the manifest against the published JSON Schema at glide.co/schemas/agent-banking/v1/ConnectorManifest.json using any AJV-based tool, or run the contract test suite in step 5 — it validates the manifest as its first check.

3. Implement the Banking capability

The Banking interface lives in @repo/connectors-base (workspace-internal package). Import BankTransferArgs from there — not from @glideco/schemas.
BankTransferArgs fields: fromAccountRef, toAccountRef, amount (string decimal), currency, and optional reference.

4. Implement the Screening capability

5. Run the contract test suite

The suite from @repo/connectors-base validates three things in order:
  1. Manifest is valid against ConnectorManifest v1.
  2. Every declared capability has a runtime implementation.
  3. No undeclared egress hosts.
Run:
The repo has 8 CI gates; all must pass before a PR is reviewed. Run pnpm validate at the root to chain turbo lint + check-types alongside the contract tests.

6. Open a PR

Follow CONTRIBUTING.md. The checklist items a connector PR must cover:
  • Contract tests pass (manifest valid, no missing capabilities, no undeclared egress hosts).
  • DISCLAIMER.md and COMPLIANCE.md present and filled in (copy from an existing connector as a template).
  • egressHosts verified against the vendor’s live API docs.
  • isMock: false set OR a note in the PR that sandbox credentials are pending.
  • trust: 'community' until the Trusted Partner Agreement is signed.

Run it

Expected output:

Extend it

  • Add a card capability to handle card issuance if the vendor supports it — declare 'card' in manifest.capabilities and implement the Card interface from @repo/connectors-base.
  • Wire the connector into the demo stack by setting GLIDE_USE_MOCK_CONNECTORS=false in .env once you have real sandbox credentials.
  • Publish under @glideco/connector-my-vendor using node scripts/publish-glide-connector.mjs my-vendor once the TPA is signed and trust is bumped to 'verified'.

Source

github.com/darshanbathija/axtior-neobank/tree/main/examples/build-a-connector-stripe-clone

Reading list