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
Widget → Update Entity
AI-generatedOverview
This node operation updates an existing entity within the Didomi Widget resource. It is useful for modifying the configuration or details of a specific widget entity, such as updating layout or preference center entities in the Didomi consent management platform. For example, it can be used to change the properties of a widget entity to reflect new compliance requirements or user interface adjustments.
Use Case Examples
- Updating a widget entity's layout configuration to comply with new privacy regulations.
- Modifying preference center entities to add or remove user consent options.
Properties
| Name | Meaning |
|---|---|
| Entity ID | The unique identifier of the widget entity to update. This is required to specify which entity will be modified. |
| Query Parameters | Optional parameters to refine or control the update request, such as pagination or filtering options. |
Output
JSON
response- The JSON response from the Didomi API after updating the widget entity, containing the updated entity details or status information.
Dependencies
- Didomi API with API Key and API Secret credentials
Troubleshooting
- Ensure the Entity ID is provided; otherwise, the node will throw an error indicating the missing Entity ID.
- Verify that the API Key and API Secret credentials are correctly set and valid to obtain an access token.
- Check the request body JSON format for correctness when sending update data; malformed JSON will cause request failures.
- Common error messages include missing required parameters (e.g., Entity ID) and authentication failures due to invalid or missing API credentials.