Skip to content
sandadocs

Connector catalogue

Every system sanda can bring into your warehouse, how a connector works, and what to do when yours is not listed.

A connector is sanda's way of reading one kind of system. It knows how to sign in, which tables or objects the system offers (sanda calls each one a stream), and how to read them, so nobody writes extraction code. You choose a connector when you add a connection. The connection is the saved link between that system and your warehouse.

Each page in this catalogue covers one connector: what to prepare in that system, and every field its setup form asks for. The field lists are generated from the connectors themselves, so they match what you see in the console. The popular connectors (PostgreSQL, MySQL, CSV / files, Google Sheets, Stripe, Xero, QuickBooks, Shopify, Salesforce and HubSpot) also carry notes on where to find each credential.

Find your system

Filter by name, or narrow the list to one family.

How a connector works

The steps are the same for every source, whatever it holds.

  1. You give sanda the details for the system. A host and a login for a database, an API key or app credentials for a SaaS product. The details go straight to sanda's managed sync over TLS, and sanda's own database never stores them.
  2. sanda reads what the system offers. Pressing Read schema signs in and lists the streams available. This doubles as the test: a wrong password or a closed firewall fails here, with a reason.
  3. You choose what to sync. Every table starts on Full refresh · Overwrite, which reads the whole table on every run and replaces what landed last time. For a large table, switch to an incremental mode with a cursor column so each run reads only the rows that have changed. See sync modes and choose what to sync.
  4. Each stream lands as a table in your warehouse. Rows go to the raw schema, one table per stream, named raw.<connection>__<stream>.
  5. Runs repeat on a schedule. You set the frequency, or run a sync by hand with Sync now. See sync schedules.

Connect a system

  1. Open Connections. In the console, go to Data · Connections and press New connection.
  2. Choose the source. Search by name, or pick from Popular or All sources.
  3. Fill in the form. The setup guide sits beside it, and the page for your connector here says where to find each credential.
  4. Read the schema and choose streams. Nothing moves until you save your choice of streams.
  5. Run the first sync. Press Sync now, or let the schedule start it.

Owners and admins add connections. The full walkthrough is in Add a connection. If the system sits behind a firewall, allow sanda's address first.

Connectors set up by arrangement

A few connectors have no setup form. MYOB is wired by hand, and so is Something else, which covers any system that is not in the catalogue. Zuora and BigCommerce are set up the same way, because the ready-made connectors for them are no longer maintained. In the console they carry a Concierge badge.

There is nothing to fill in. You create the connection with a name and a frequency, and a sanda engineer gets in touch to wire it up and confirm the first load with you. Until then the connection shows Setup incomplete in Data · Connections.

A connector that normally has a form can land here too. If sanda cannot read a connector's setup form, the console says so and offers the same route, and the connector's page in this catalogue says the same.

Ask for a connector

If the system you use is not in the catalogue, pick Something else when you add a connection. Give it a name and a frequency, and a sanda engineer gets in touch to find out what the system is and the best way to bring its data in.

If what you have is a file rather than a system, load a CSV straight into your warehouse. For anything else, see getting help.

Something unclear or out of date? Tell us, and we will fix the page.