Skip to main content
If the provider you need is not in the connector catalog, describe the workflow you want to support and the provider’s public API or webhook contract. Include:
  • provider name and account type;
  • the application workflow and direction of data movement;
  • required actions or events;
  • authentication method and scopes;
  • whether the integration is project-scoped or workspace-scoped;
  • links to the provider’s public API documentation.
P2HS evaluates requests against the platform capability model, security requirements, and connector readiness process. Do not send API keys, access tokens, webhook secrets, or other credentials in a request.
A provider appearing in a request or internal catalog does not mean that it is publicly available. Public availability is announced through the connector catalog and product configuration.