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 → Get Entity
AI-generatedOverview
This node operation retrieves a specific entity from the Didomi Widget resource using the entity's unique ID. It is useful for scenarios where you need to fetch detailed information about a particular widget entity, such as layout entities in a consent or preference center, to display or process within an automation workflow.
Use Case Examples
- Fetch a widget entity by its ID to display its configuration details in a dashboard.
- Retrieve an entity to verify or audit widget layout components in a compliance workflow.
Properties
| Name | Meaning |
|---|---|
| Entity ID | The unique identifier of the widget entity to retrieve. |
| Query Parameters | Optional parameters to refine or control the data returned by the API, such as pagination, filtering, or other flags. |
Output
JSON
entity- The retrieved widget entity object with its details.
Dependencies
- Didomi API key and secret credentials for authentication.
Troubleshooting
- Ensure the Entity ID is provided; otherwise, the node will throw an error indicating the missing ID.
- Verify that the Didomi API credentials (API key and secret) are correctly configured and valid to avoid authentication errors.
- Check the network connectivity and Didomi API endpoint availability if requests fail.
- If the API returns an error, review the error message for details such as invalid parameters or permissions issues.
Links
- Didomi API - Get Entity - Official API documentation for retrieving a widget entity from Didomi.