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. Author Overview, Setup Guide, Permissions, and Troubleshooting as explicit Mintlify<Tab> sections. The app preserves those
boundaries and the order of their content: inner headings such as “Confluence
Cloud setup” remain in the tab where they were written.
The documentation loader carries tab boundaries as <!-- provider-doc-tab: Overview -->
markers in the existing Markdown payload. Plain Markdown without these markers
recognizes only exact ## Overview, ## Setup Guide, ## Permissions, and
## Troubleshooting section titles. Other headings remain in the current
section; content before a section stays readable in Overview. Fenced code is
always content, never a tab boundary. No heading keywords route content.
A page can scope a section to one authentication method with
{/* BEGIN AUTH STRATEGY type="..." */} and {/* END AUTH STRATEGY */}
lines. Mintlify shows every section; the wizard leaves out a scoped section
when the Provider does not offer that method.
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.