Custom Connections
Custom Connections allow you to connect GRiPOFlow with services that do not have a dedicated provider.
Instead of selecting a predefined provider such as Azure or AWS, you can create a custom connection by choosing an authentication method supported by the target service. This gives you the flexibility to integrate internal APIs, third-party platforms, or proprietary applications while securely storing authentication credentials.
Like Provider Connections, Custom Connections can be reused across multiple workflows and plugins, making them easy to manage and maintain.
When to Use a Custom Connection
Use a Custom Connection when:
- The service is not available as a built-in provider.
- You are connecting to an internal or private API.
- A third-party application requires a custom authentication method.
- You need more control over how authentication credentials are configured.
If a dedicated provider is available, we recommend using a Provider Connection, as it includes provider-specific validation and configuration.
Supported Authentication Methods
GRiPOFlow currently supports the following authentication methods for Custom Connections.
| Authentication Method | Description | Documentation |
|---|---|---|
| API Key | Authenticate using an API key issued by the service provider. | API Key |
| OAuth 2.0 | Authenticate using the OAuth 2.0 authorization flow. | OAuth 2.0 |
| Key-Value | Authenticate using one or more custom key-value pairs or HTTP headers. | Key-Value |
Choosing the Right Authentication Method
| Authentication Method | Best Used For |
|---|---|
| API Key | Services that provide a single API key for authentication. |
| OAuth 2.0 | Applications requiring user authorization, delegated access, or refresh tokens. |
| Key-Value | APIs that require custom headers, tokens, or proprietary authentication fields. |
If you’re unsure which authentication method to use, refer to your service provider’s API documentation.
Security Best Practices
To keep your integrations secure:
- Store credentials only in Connections.
- Never hardcode API keys or tokens inside workflows.
- Use descriptive connection names.
- Rotate credentials regularly.
- Remove unused or expired connections.
- Grant only the minimum permissions required by the external service.