Actions35
- Secret Actions
- Workplace Actions
- Workplace User Actions
- Workplace Role Actions
- Activity Log Actions
- Project Actions
- Project Role Actions
- Project Member Actions
- Config Actions
- Config Log Actions
- Environment Actions
- Trusted IP Actions
- Integration Actions
- Auth Actions
- Share Actions
Overview
This node integrates with the Doppler API to manage various resources related to project configurations and security. Specifically, for the Trusted IP resource with the List operation, it retrieves a list of trusted IP addresses associated with a given project configuration. This is useful in scenarios where you want to audit or manage IP addresses that are allowed to access certain project configurations securely.
Practical examples include:
- Auditing which IPs have trusted access to your project's configuration.
- Automating compliance checks by listing trusted IPs regularly.
- Integrating with security workflows to monitor changes in trusted IPs.
Properties
| Name | Meaning |
|---|---|
| Project | The identifier (string) of the project whose trusted IPs you want to list. |
| Config | The identifier (string) of the specific configuration within the project to query. |
Output
The output JSON contains the list of trusted IP addresses associated with the specified project and config. Each item in the list represents a trusted IP entry as returned by the Doppler API.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Doppler API.
- The node makes HTTP GET requests to the Doppler API endpoint
/v3/configs/config/trusted_ips. - No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Empty or missing trusted IP list: Ensure that the
ProjectandConfigproperties are correctly set and correspond to existing entities in Doppler. - Authentication errors: Verify that the API key credential is valid and has sufficient permissions to access trusted IP information.
- API request failures: Check network connectivity and Doppler service status. Also, confirm that the API endpoint URL has not changed.
- Incorrect property usage: Make sure to provide both
ProjectandConfigparameters when listing trusted IPs, as they are required query parameters.
Links and References
- Doppler API Documentation (for trusted IPs endpoint)
- n8n Documentation on Creating Custom Nodes