Skip to main content
Connections are reusable encrypted credentials. PostgreSQL, MySQL, MongoDB, and Airtable are Available Now as sources and destinations. ClickHouse, and HubSpot are Available Now as sources. ClickHouse as a destination is Coming Soon. Each connector retains the role and limitations documented below.
Available Now means owner-approved and code-supported. It is not an independent production certification. Automated evidence and pending manual UI validation are tracked separately in the engineering audit documents.

Current live connectors

See Supported SaaS streams for the current stream list, preview evidence, limitations, and planned additions.

Coming Soon

Stripe setup is hidden, including direct setup links. The other Coming Soon catalog cards are disabled. New connections cannot be created for these connectors. This availability change applies to the connection UI; DuckDB continues to provide internal staging for pipeline runs. Other connector tiles may appear in the catalog, but they are not available until their create, test, save, pipeline, and run path is enabled in the app.

Available connector guides

See Airtable source and Airtable destination for Personal Access Token scopes, base/table discovery, field mapping, and Upsert behavior. See MySQL source and MySQL destination for database grants, table contracts, sync modes, and verification queries. See MongoDB source and MongoDB destination for encrypted URI setup, collection discovery, inferred schemas, BSON handling, Incremental cursors, and key-required Upsert delivery. The MongoDB and PostgreSQL example records the three currently verified real data-movement paths. See ClickHouse source for port handling, table engines, and incremental behavior. See ClickHouse source pipelines for the validated route. ClickHouse as a destination is Coming Soon. See HubSpot source for its 18 supported streams, private app token setup, UTC extraction window, and PostgreSQL requirements. Stripe source is Coming Soon; its retained URL is a status notice.

Create a source connection

  1. Open Connections.
  2. Click + New Connection.
  3. Set the role to Source.
  4. Choose PostgreSQL, MySQL, MongoDB, Airtable, ClickHouse, or HubSpot.
  5. Fill the connector-specific fields. Airtable uses a Personal Access Token; HubSpot uses a private app access token.
  6. Click Test Connection.
  7. Save after the test succeeds.

Create a destination connection

  1. Open Connections.
  2. Click + New Connection.
  3. Set the role to Destination.
  4. Choose PostgreSQL, MySQL, MongoDB, or Airtable.
  5. Fill the destination database credentials.
  6. Click Test Connection.
  7. Save after the test succeeds.
Database destination users need write access to existing tables or MongoDB collections and permission to create or reconcile targets only when the connector contract permits it. Airtable destinations need an existing base/table, writable mapped fields, and record read/write access.

Network access

If your database is hosted behind a provider firewall, allow traffic from the Arcyria runtime before testing the connection. See Private database access.