DOCUMENTATION
OpenConnector catalog coverage & verification
Understand provider catalog entries, local Action executors, live upstream API verification, and checks before production use.
Source checked 2026-09-09. These examples were checked against the linked source revision. They are not a claim of live API verification; your deployed version may differ.
Catalog definitions
A catalog entry describes a provider, its authentication methods, Actions, and schemas. Its presence alone does not establish that every Action can execute in your deployment.
Local execution
An executor implements an Action in the runtime. Inspect the implementation at the linked revision and confirm that your running version includes it.
Upstream verification
A working schema or executor is not proof of a successful upstream API call. Check verification records and test the specific Action with your own account, scopes, and resources.
When a call fails
Check the runtime URL and token, selected account, required input and provider scopes. Use the returned executionId to inspect redacted run logs. Avoid automatically repeating Actions that may have already changed provider data.
Record what you actually verified
For each check, record the runtime revision or image, Action ID, account type, scopes, non-sensitive input, result and date. Label source inspection, local executor tests and real provider API calls separately. Never publish credentials, private content or unredacted logs as evidence.