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 → Create Note
AI-generatedOverview
This node operation creates a note associated with a privacy request using the Didomi API. It is useful in scenarios where additional information or comments need to be added to a privacy request for tracking or documentation purposes. For example, a compliance officer might add notes about the status or details of a user's data access or deletion request.
Use Case Examples
- Adding a note to a privacy request to document communication with the user.
- Creating a note to record internal comments on the progress of a privacy request.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | Optional parameters to filter or modify the request, such as organization user ID, request ID, status, limit, etc. |
| Request Body | The JSON body of the note to be created, containing the note details. |
Output
JSON
id- The unique identifier of the created note.request_id- The ID of the privacy request the note is associated with.content- The content of the note.created_at- Timestamp when the note was created.updated_at- Timestamp when the note was last updated.
Dependencies
- Didomi API with API Key and Secret for authentication
Troubleshooting
- Ensure that the API Key and API Secret credentials are correctly set and valid, as missing or invalid credentials will cause authentication failures.
- Verify that the Request Body JSON is correctly formatted and contains all required fields for creating a note, otherwise the API may reject the request.
- Check that the 'privacyRequestNoteCreatePost' operation is selected and that the resource is set to 'Privacy Request' to avoid operation mismatch errors.
- If the API returns an error, review the error message for details such as missing required parameters like request ID or note content, and correct accordingly.