← Workers / workers / configuration

Integrations

One of the key features of Cloudflare Workers is the ability to integrate with other services and products. In this document, we will explain the types of integrations available with Cloudflare Workers and provide step-by-step instructions for using them.

Cloudflare Workers offers several types of integrations, including:

• Databases: Cloudflare Workers can be integrated with a variety of databases, including SQL and NoSQL databases. This allows you to store and retrieve data from your databases directly from your Cloudflare Workers code.
• APIs: Cloudflare Workers can be used to integrate with external APIs, allowing you to access and use the data and functionality exposed by those APIs in your own code.
• Third-party services: Cloudflare Workers can be used to integrate with a wide range of third-party services, such as payment gateways, authentication providers, and more. This makes it possible to use these services in your Cloudflare Workers code.

To use any of the available integrations:

• Determine which integration you want to use and make sure you have the necessary accounts and credentials for it.
• In your Cloudflare Workers code, import the necessary libraries or modules for the integration.
• Use the provided APIs and functions to connect to the integration and access its data or functionality.
• Store necessary secrets and keys using secrets via wrangler secret put <KEY>.

To help you get the most out of using integrations with Cloudflare Workers:

• Secure your integrations and protect sensitive data. Ensure you use secure authentication and authorization where possible, and ensure the validity of libraries you import.
• Use caching to improve performance and reduce the load on an external service.
• Split your Workers into service-oriented architecture using Service bindings to make your application more modular, easier to maintain, and more performant.
• Use Custom Domains when communicating with external APIs and services, which create a DNS record on your behalf and treat your Worker as an application instead of a proxy.