Skip to content
Bindato
Registry11 triggers and 17 actions, declared in code

7 systems, one flow engine.

Each connector declares its triggers and actions in code. What is listed here is what a flow can use — nothing more, nothing hidden.

Shopify
NetSuite
Amazon
BrightPearl
ShipStation
Shiptheory
Cin7
Book a demoCreate an account
StorefrontEvery other connector
  • Shopify
  • NetSuite
  • Amazon
  • BrightPearl
  • ShipStation
  • Shiptheory
  • Cin7
7
Connectors in the registry
2
Installable bundles
11
Triggers
17
Actions

Connectors

Every system Bindato connects

Grouped by the job each system does in a merchant's stack. Counts, auth type and bundle membership are read from the registry.

1 connector

Storefront

Where orders originate and where fulfillment and stock are written back.

3 connectors

ERP and inventory

Systems of record for sales orders, stock levels and goods-out.

1 connector

Marketplace

A second sales channel whose orders and shipments need the same handling.

2 connectors

Shipping

Rates, labels and carrier tracking for the parcels that leave the warehouse.

Built on one SDK

Every connector is held to the same contract

A connector is a typed module the engine validates at boot. The three rules below are enforced, not advised.

  1. Rate limits per action

    Each action can declare requests per window and a burst allowance, because one API's order lookup is throttled to a request a minute while its shipment confirmation is not.

  2. One retry policy

    Every step carries a policy: halt, skip the record, or retry with exponential backoff on 429, 500, 502 and 503. The default is five retries; a bundle can tighten it per step.

  3. Verified or re-fetched webhooks

    A provider that signs its webhooks is verified on receipt. One that does not may only tell Bindato that a record changed — the connector must re-fetch it by id before a flow acts, and the boot check refuses a connector that skips this.

Questions

About connectors

Can I connect a system that is not listed?
Not yet from the dashboard. Connectors are written against the connector SDK and go through its compliance check; if your stack needs one that is missing, tell us on the demo call and we will scope it.
What is the difference between a webhook and a polling trigger?
A webhook trigger receives the event from the provider as it happens. A polling trigger asks the provider for changes on a fixed interval and carries a cursor so nothing is handled twice. The badge on each trigger says which it is.
Do I need a bundle to use a connector?
No. A bundle is a set of pre-built flows between two connectors, plus a settings tab where the bundle needs one. Any connector's triggers and actions can also be used in a flow you build yourself.
How are credentials stored?
Encrypted at rest, scoped to your tenant by database row-level security, and decrypted only for the duration of a call.

See one order flow end to end.

Thirty minutes with a Shopify store you control. We connect it, install a bundle, and walk the run record together.

Book a demoCreate an account