The parts of a Provider integration
A Provider Plugin sets the same 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 also appears on the Provider’s connector page in the app. Learn shows its Overview, Permissions, and other sections as accordions. The second tab, Connect or Manage, shows its Setup Guide and Troubleshooting as accordions. This site shows the setup for every authentication method. The connector page shows the docs of the authentication method that you choose there. 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 guarantees
Every Provider Plugin has:- 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.