Every integration catalog is also a list of what you don't support

WorkOS Pipes supports more than 300 preconfigured integrations while allowing developers to add unsupported services as custom providers through the dashboard or API without changing the credential-retrieval code used for catalog providers. Customization covers using an organization’s own OAuth credentials, setting organization-specific scopes or provider availability, and defining entirely new OAuth, API key, or client-credentials providers. OAuth provider configuration includes endpoints, credentials, scopes, and compatibility options for differences such as PKCE, scope separators, token formats, and client authentication methods, while API key providers require minimal setup and securely collect, display, update, and vend user-provided keys. A unified credentials endpoint returns the relevant credential type and connection status, with WorkOS handling OAuth token refreshes, while Relay can make provider requests without exposing credentials to an application environment. Authentication method selection is permanent after provider creation, deleting a custom provider also removes associated connected accounts, and existing OAuth connections can be migrated into Pipes using previously held tokens without requiring users to authorize again.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.