Skip to main content
A data stream is one collection of records exposed by a Provider Plugin, such as Linear issues, GitHub pull requests, or Slack channels. The historical protocol name for a data stream is a tap. The Provider Plugin owns how each stream is fetched: transport, pagination, incremental behavior, extraction, traversal, and rate limits. A Workspace controls whether the stream is enabled and any supported connection-level overlay.
The Workspace API has no public address yet. Contact your Parable representative to change which streams a connection syncs. See Availability.

​
List streams

Filter by the Provider connection identifier when working with one connection. The result combines the plugin’s stream definition with the Workspace’s current state.

​
Enable, update, or disable a stream

Enabling a stream makes it eligible for synchronization; data does not appear until the connection successfully runs that stream. Inspect the SQL catalog before assuming a table has rows: a stream that ran successfully and found nothing leaves its table queryable. An empty first run returns zero rows. An empty incremental run keeps rows from earlier runs. A stream removes a prior row only when it reports that deletion or completes an exhaustive result that proves the row is absent. To understand the resulting table names and columns, see the Provider Pool. To define transport, pagination, traversal, or schema behavior for a custom plugin, use the Provider Plugin authoring guides.