Skip to main content
A connector is Parable’s integration with one of the tools your company uses: GitHub, Jira, Slack, Linear, Workday, and dozens more. When you configure a connector in your workspace, Parable syncs data from that tool into your data lake.
Connectors use read-only API access. Parable never writes to, modifies, or deletes anything in your source systems.

​
The model

Every connector is a definition Parable ships, plus an instance you configure in your workspace. The definition is the same for every workspace. Your instance is yours: credentials, which streams are on, and health. You can read the definition nested on an instance. List yours, then look at connector.supportedAuthStrategies and connector.taps:
Browse the catalog (including auth strategies on a leaf grouping) without configuring anything:

​
What your workspace controls

  • Which connectors are configured, with which auth strategy and credentials. Credentials are encrypted at rest and never returned by the API.
  • Which taps are enabled. Some streams are on by default; others are opt-in.
  • Sync health. Each instance has connectionStatus, hasValidCredentials, and last-sync fields.
You do not pick pagination style or sync mode. Those are part of each tap’s definition so Parable can walk that source API correctly. You inspect them; you do not set them. How ingestion walks a source is the field-by-field map of that walk.

​
Rate limits

Each connector definition includes rate limits so Parable stays inside the source API’s budget: requests per second, max concurrent calls, and whether to honor Retry-After. Some taps override the connector-level limits. You do not configure these; they explain why a large backfill is paced.

​
Requesting a connector Parable does not have yet

If a tool you rely on is missing, file a connector request through the API (POST /api/connector-requests/connector-requests) or in the app.
Step-by-step setup guides (OAuth apps, API keys, scopes) live in the product documentation.