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 interacts with the Doppler API to retrieve a specific activity log entry. It is useful for users who want to fetch detailed information about a particular activity recorded in Doppler's logging system. Typical scenarios include auditing changes, investigating security events, or monitoring user actions within Doppler.
For example, if you have an activity log ID from Doppler and want to get all details related to that event, this node operation will retrieve that data for further processing or analysis in your workflow.
Properties
| Name | Meaning |
|---|---|
| Log ID | The unique identifier of the activity log entry to retrieve. This specifies which log to fetch. |
Output
The node outputs JSON data representing the retrieved activity log entry from Doppler. This JSON contains all details associated with the specified log ID, such as timestamps, user actions, affected resources, and other metadata recorded by Doppler.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Doppler API.
- The node makes HTTP GET requests to the Doppler API endpoint:
https://api.doppler.com/v3/logs/log. - The "Log ID" parameter is passed as a query string parameter named
logafter URL encoding.
Troubleshooting
- Missing or invalid Log ID: If the Log ID is not provided or incorrect, the API call will fail or return no results. Ensure the Log ID is correct and properly set.
- Authentication errors: If the API key credential is missing or invalid, the request will be rejected. Verify that the Doppler API key is correctly configured in n8n credentials.
- Network or API issues: Temporary network failures or Doppler API downtime can cause errors. Retry later or check Doppler status.
- Permission issues: The API key used must have sufficient permissions to access activity logs; otherwise, the request may be denied.
Common error messages typically relate to HTTP 401 Unauthorized (invalid credentials), 404 Not Found (invalid log ID), or 400 Bad Request (malformed parameters).
Links and References
- Doppler API Documentation (for more details on activity logs and API usage)
- n8n Documentation (general guidance on using API nodes and credentials)