The parts of a Provider integration
Keep these layers separate when writing or debugging a plugin. Changing a
definition changes the integration contract for every connection that uses it.
Changing a connection changes only one Workspace.
Browse Provider Plugins
Each page in this section documents one installed Provider Plugin: what it connects, the data streams it provides, setup, permissions, and troubleshooting. The same page is rendered in Mintlify and loaded into the Provider connection wizard. Its## sections become the app’s Overview, Setup guide, Permissions,
and Troubleshooting tabs, so the documentation has one authored source. The
Permissions tab keeps its two disclosure levels in the app: expand a data
stream row to read what it enables and its scope, then expand a field row for
that field’s developer identifier and interpretation.
What every Provider Plugin must preserve
Regardless of transport, a plugin must establish:- a stable Provider and plugin identity;
- an authentication or sender-verification boundary;
- named data streams with explicit record schemas;
- deterministic row identity and update ordering;
- bounded retry, concurrency, and rate-limit behavior; and
- a predictable projection into the Provider Pool.
Definition revisions and release
Creating a Provider Plugin gives it a stable connector identity indraft and
starts research. Research output and admin edits are candidate definition
versions; they do not change the active Plugin. An internal author reviews the
candidate diff, validation evidence, access requirements, and release scope
before activation.
Activation changes the definition used by new syncs. Syncs already in flight
keep their frozen definition. Catalog visibility, customer credential intake,
sync access, and deprecation are separate release controls and do not change
automatically when a definition activates or reaches another maturity level.
Internal authors use Validate and release
for the evidence and release path. The underlying version and lifecycle
decisions are EDR-0082
and EDR-0089.