Pipes allows users to securely connect third-party accounts to applications without the hassle of managing OAuth flows, token refresh logic, or credential storage. It supports popular services like GitHub, Slack, Google, and Salesforce. To start integrating a provider, you configure it in the WorkOS Dashboard by selecting it from the list. If a required provider isn’t listed, you can reach out to WorkOS for assistance. For quick setups, use WorkOS-managed shared credentials in sandbox environments to bypass the need for creating OAuth applications for each provider. When setting up a provider for production, you need to create an OAuth application within the provider’s dashboard. This involves following specific instructions in the setup modal, providing a redirect URI, and entering the client ID and secret. You also specify required scopes and can include an optional description that informs users how their data will be used. The documentation recommends checking each provider's site for a complete list of available scopes. The Pipes Widget streamlines user interaction by providing a UI for connecting and managing accounts. It shows available providers and initiates the authorization flow, while also communicating with the WorkOS API. If there are issues with the access token, the widget prompts users to reauthorize. Once connected, access tokens can be fetched from the backend for API calls to the service on behalf of users, with Pipes managing token refreshes to ensure access remains uninterrupted. The article includes a code example using the Octokit library to list GitHub repositories, demonstrating how to handle access tokens and potential errors.