Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.mantrixflow.com/llms.txt

Use this file to discover all available pages before exploring further.

Connections are the starting point for almost every successful deployment. A clean connection setup makes the rest of the pipeline flow much easier because the builder only works well after credentials, reachability, and permissions are correct.

​
Relevant routes

  • List: /workspace/connections
  • Catalog: /workspace/connections/new?role=source or role=destination
  • Connector form: /workspace/connections/new/[type]
  • Edit: /workspace/connections/[id]/edit

​
Supported connectors in the current flow

This guide tracks the connectors that complete the live create, test, save, and pipeline workflow. Partial rollout tiles are intentionally not treated as supported here until the end-to-end path is ready. Sources:
  • PostgreSQL
  • MySQL
  • MariaDB
  • SQLite
  • CockroachDB
  • Stripe
  • Shopify
  • HubSpot
  • GitHub
  • Notion
Destinations:
  • PostgreSQL
  • MySQL
  • MariaDB
  • SQLite
  • CockroachDB
  1. Create the source connection first.
  2. Test it until the result is clean.
  3. If it is a database source, refresh or discover tables before building the first pipeline.
  4. Create the destination connection.
  5. Test again before you build a pipeline.
For PostgreSQL source or destination connections that are protected by a provider firewall, open the Private database access panel in the form and copy MantrixFlow’s /32 allowlist value before testing. Private-only databases with no public endpoint require a later SSH tunnel or self-hosted agent release.

​
Create a new connection

  1. Click + New Connection from the list page.
  2. Choose Source when MantrixFlow should read from the system or Destination when it should write into it.
  3. Pick the connector tile.
  4. Fill the connector-specific fields exactly as shown in the form.
  5. Click Test Connection. The save action is only useful after a successful test.
  6. Save the connection and move into the pipeline flow.

​
Discover tables and resources

For database sources, use Discover Tables or refresh the source metadata before the first pipeline. This is the fastest way to confirm that grants, schemas, and table visibility are correct. For SaaS sources, validate one concrete resource first. In practice that usually means:
  • Shopify: orders or customers
  • Stripe: invoices or subscriptions
  • HubSpot: deals or contacts
  • GitHub: pull_requests or issues
  • Notion: databases or pages

​
Edit a connection safely

Use Edit when credentials rotate, hosts change, or a default schema needs to be updated. After any edit:
  1. Re-test the connection.
  2. Refresh source metadata if schemas or permissions changed.
  3. Run at least one manual pipeline sync before trusting the schedule again.

​
Delete with care

Deleting a connection that is still attached to a pipeline will break future runs. Before deletion, confirm that no active pipeline uses it and that any schedules have been moved to a replacement connection.

​
Good production habits

  • Use separate connections for staging and production.
  • Use least-privilege users instead of reusing admin credentials.
  • Put environment names in the connection name, such as Shopify Production or Postgres Staging.
  • Re-test connections after network, SSL, or password changes.