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 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.
Capability summary
Authentication
Auth method: Bearer Token
Required scopes
]
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Record | Yes | Yes | A generic object representing any data structure. Read/write capabilities depend entirely on the user's endpoint configuration and the permissions of the provided token. |
Supported actions
| Action | Description |
|---|---|
| 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. |
Setup steps
- Locate the API documentation for the service you wish to connect to.
- 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). - 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".
- In Flows360, create a new connection using the Generic Bearer Token connector.
- Enter the Base URL and the Bearer Token into the corresponding fields in the connection configuration modal.
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.
Troubleshooting
I am receiving a '401 Unauthorized' or '403 Forbidden' error. What does this mean?
This error indicates a problem with the provided Bearer Token or its permissions.nn1. Verify the Token: Double-check that the token entered in the connection configuration is identical to the one from the source application. Ensure there are no leading/trailing spaces or missing characters.n2. Check Token Expiration: Confirm that the token has not expired or been revoked in the source application.n3. Confirm Permissions: Log into the source application and verify that the token has the required permissions (scopes) to access the specific API resource and perform the HTTP method (e.g., GET, POST) you are attempting.