Skip to main content
Open Connections to create reusable database and SaaS credentials.

Create a connection

  1. Click + New Connection.
  2. Choose the role: Source or Destination.
  3. Choose PostgreSQL, MySQL, MongoDB, Airtable, Asana, Linear, Notion, GitHub, HubSpot, or Stripe for a source. Choose PostgreSQL, MySQL, MongoDB, or Airtable for a destination.
  4. Fill the connection fields.
  5. Click Test Connection.
  6. Save after the test succeeds.

Source connections

PostgreSQL and MySQL source users should have read access to only the schemas or databases and tables you plan to include. Airtable sources use a Personal Access Token with schema and record read access. HubSpot sources use a read-only private app access token with the scopes required by the selected streams. See the HubSpot source guide. Stripe sources use a secret or restricted read key. See the Stripe source guide. See the Airtable source guide and MySQL source guide for connector-specific setup. MongoDB sources use a complete encrypted mongodb:// or mongodb+srv:// URI and a database name. Use a dedicated read-only database user. See the MongoDB source guide. Asana sources use a Personal Access Token and store workspace/project scope on each pipeline. See the Asana source guide. Linear Available Now sources use a Personal API Key and store team/project scope on each pipeline. See the Linear source guide. Notion sources use an internal integration token and can read only pages and databases shared with that integration. See the Notion source guide. GitHub Available Now sources use a Personal Access Token and read one GitHub.com repository per connection. See the GitHub source guide.

Destination connections

Destination users should have write access to pre-created destination tables. Airtable destinations also require an explicit writable-field mapping and at least one merge key. MantrixFlow validates destination contracts during pipeline runs. MongoDB destinations require one or more non-null Upsert keys. Pre-create a supporting unique index for production collections. See the MongoDB destination guide.

Good operating habits

  • Re-test connections after credential rotation.
  • Keep source users read-only where possible.
  • Keep destination table ownership and permissions explicit.