Skip to main content
Connections are reusable encrypted credentials. PostgreSQL, MySQL, MongoDB, Airtable, ClickHouse, and DuckDB are Available Now as sources and destinations. Stripe, HubSpot, GitHub, Asana, Linear, Notion, Zendesk, and Strapi are Available Now as sources. 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

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. 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 and ClickHouse destination for HTTP and native port handling, the clickhousedb SQLAlchemy dialect, MergeTree destination tables, and cross-connector setup. See the ClickHouse and MySQL pipeline example for the validated cross-connector matrix. See DuckDB source and DuckDB destination for the managed file_... reference contract, read-only source behavior, direct Upsert into pre-existing tables, write leasing, and optimistic version checks. See HubSpot source for its ten supported streams, private app token setup, UTC extraction window, and PostgreSQL requirements. See Stripe source for its 34 supported streams, authentication, sync modes, and empty-stream behavior. See Asana source for PAT setup, workspace/project scope, eight streams, task incremental behavior, and current limitations. See Notion source for integration sharing, data-source discovery, dlt-backed Full Table and Incremental behavior, stable staging names, and API safety limits. See Linear source for Personal API Key setup, team/project scope, eight resources, updatedAt incremental behavior, and current limitations. See GitHub source for Personal Access Token setup, repository permissions, 12 discoverable resources, Full Table behavior, pagination safety, and limitations. See Zendesk source for read-only OAuth, 13 Support resources, historical extraction windows, incremental ticket and event behavior, and reconnect guidance. See Strapi source for read-only API-token setup, dynamic Content API IDs, hosted URL restrictions, Strapi 5 response handling, and Full Table limitations.

​
Create a source connection

  1. Open Connections.
  2. Click + New Connection.
  3. Set the role to Source.
  4. Choose PostgreSQL, MySQL, MongoDB, Airtable, ClickHouse, DuckDB, Asana, Linear, Notion, GitHub, Zendesk, Strapi, HubSpot, or Stripe.
  5. Fill the connector-specific fields. Airtable and Asana use Personal Access Tokens; Linear uses a Personal API Key; Notion uses an internal integration token; GitHub uses a Personal Access Token; Zendesk uses OAuth; Strapi uses a read-only API 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, Airtable, ClickHouse, or DuckDB.
  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 MantrixFlow runtime before testing the connection. See Private database access.