Connect to any REST API using a bearer token for authentication.
The Generic Bearer Token connector provides a powerful, flexible method for integrating with a vast range of modern APIs and services. Many SaaS platforms and internal microservices use bearer tokens as a secure, standardized way to manage API access. This connector simplifies the process by handling the `Authorization` header automatically. All you need to provide is the token. Use it to read data from, write data to, or orchestrate workflows across any RESTful API that relies on this common authentication scheme. It's the go-to tool for connecting to custom-built services or public APIs that aren't yet in our specific connector directory.
Common use cases
- – Connect to internal, custom-built applications and microservices.
- – Integrate with modern SaaS platforms that use bearer tokens.
- – Automate data synchronization between a new-to-market application and your existing systems.
- – Pull reports and data from proprietary business intelligence tools.
- – Build workflows that interact with any REST API secured by a bearer token.
Sync scenarios
- – Send GET requests to read data from any API endpoint.
- – Use POST or PUT requests to create or update records.
- – Automate DELETE requests to remove data.
- – Paginate through large data sets from a source API.
- – Authenticate and maintain sessions with token-based services.
Objects supported
- Record
Actions
- list_records
- get_record
Frequently asked questions
What is a bearer token?
A bearer token is a type of access token used for authentication. The "bearer" is authorized to use it to access protected resources (like an API) without needing a private key, as the token itself is proof of authorization.
When should I use this connector?
Use the Generic Bearer Token connector when you need to connect to a service that uses this authentication method and does not have a dedicated, pre-built connector in our directory. It's ideal for custom tools and modern APIs.
How do I secure my bearer token in Flows360?
All credentials, including bearer tokens, are encrypted and stored securely within the Flows360 platform. We recommend using tokens with the minimum required permissions and employing environment-specific variables for management.
- Auth method: Bearer Token
- Required scopes: 1
- Supported objects: 1
- Supported actions: 2
Overview
The Generic Bearer Token connector provides a flexible method for integrating with any RESTful API that uses a static bearer token for authentication. This is a common authorization standard for many SaaS platforms, custom applications, and internal microservices.
This connector automates the inclusion of the `Authorization: Bearer <token>` header in every API request. You provide the API Base URL for the target service and the static token, and the connector handles the authentication details. Use it to configure custom API calls to read from or write data to any service that employs this authentication scheme. It is ideal for connecting to services not yet available in the main connector directory.
Setup steps
1. Locate the API documentation for the service you wish to connect to.
2. Find the Base URL for the service's REST API. This is the common prefix for all API endpoints (e.g., `https://api.example.com/v1`).
3. Generate or find your API Key or Bearer Token within the target service's user interface. This is typically located in your account settings under a section named "API", "Developer Tools", or "Integrations".
4. In Flows360, create a new connection using the Generic Bearer Token connector.
5. Enter the Base URL and the Bearer Token into the corresponding fields in the connection configuration modal.
Required scopes
]
Supported objects
- Record
Supported actions
- list_records — Fetches a list of records from a user-specified endpoint path.
- get_record — Fetches a single record from a user-specified endpoint path.
Use cases
- Revenue Operations
- Customer 360
- CRM to ERP Sync
- Data Warehousing
Limitations
* Static Tokens Only: This connector is designed for static, non-expiring bearer tokens or API keys. It does not support OAuth 2.0 flows or any mechanism for automatic token refresh. You must manually update the token in the connection settings if it expires or is rotated.
* No Scope Discovery: The connector has no insight into the permissions (scopes) associated with the provided token. You must ensure the token has the necessary privileges in the target service to perform the API calls you configure.
* Manual Endpoint Configuration: You are responsible for providing the exact API endpoint path, HTTP method (e.g., GET, POST, PUT), and request body for each action you build.
