Actions75
- Compliance Report Actions
- Consent And Preference Actions
- Data Manager Actions
- Add Preference Into Your Configuration Tree
- Add Purpose Into Your Configuration Tree
- Create Preference
- Create Purpose
- Delete Preference
- Delete Purpose
- Delete Selected Preference
- Delete Selected Purpose
- Get Available Regulations and Related Information
- Get Configuration Tree
- Get Preference
- Get Purpose
- Get Vendor
- List Preferences
- List Purposes
- List User Rights
- List Vendors
- Update Preference
- Update Purpose
- Privacy Request Actions
- Widget Actions
- Create Authentication Provider
- Create Consent Notice
- Create Widget
- Delete Widget
- Get Archived Widget
- Get Current Draft Configuration For Notice
- Get Custom Theme
- Get Deployment
- Get Entity
- Get Widget
- List Archived Widget
- List Custom Themes
- List Deployments
- List Entities
- List Widgets
- Publish Current Draft Configuration For Notice
- Publish Widget
- Set Default Authentication Provider
- Update Component
- Update Current Draft Configuration For Notice
- Update Custom Theme
- Update Entity
- Update Multiple Components
- Update Multiple Entities
- Update Widget
Privacy Request → Get Note
AI-generatedOverview
This node operation retrieves a specific note related to a privacy request from the Didomi API. It is useful in scenarios where users need to access detailed notes or comments associated with privacy requests, such as data access or deletion requests, to review or process them further.
Use Case Examples
- A data privacy officer retrieves notes attached to a user's data deletion request to verify the request details.
- An automated workflow fetches notes on privacy requests to generate reports or trigger follow-up actions.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | Optional parameters to filter or modify the retrieval of the privacy request note, such as filtering by organization user ID, request ID, status, limit, and other metadata fields. |
Output
JSON
note- The retrieved privacy request note data returned from the Didomi API.
Dependencies
- Didomi API credentials (API Key and API Secret)
Troubleshooting
- Ensure that the required 'Request ID' and other necessary parameters are provided; missing these will cause errors.
- Verify that the Didomi API credentials (API Key and API Secret) are correctly configured and valid.
- Check network connectivity and API endpoint availability if requests fail.
- Error messages related to missing IDs indicate that the required parameter for the operation is not set; provide the correct ID to resolve.