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 → Publish Widget
AI-generatedOverview
This node operation publishes a widget using the Didomi API. It is useful for scenarios where you need to make a widget's current draft configuration live, such as deploying consent and preference interfaces on websites or applications. For example, after customizing a widget's settings or content, you can use this operation to publish those changes so they become active for end users.
Use Case Examples
- Publishing a consent notice widget after updating its configuration to comply with new privacy regulations.
- Deploying a customized preference center widget to reflect updated user consent options.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | Optional parameters to filter or modify the publish request, such as limiting results or specifying IDs. These include options like 'By Organization User ID', 'Cursor', 'Generate TCFCS', 'ID', 'Limit', 'Merge Users', 'Notice ID', 'Or', 'Organization ID', 'Organization User ID', 'Property ID', 'Regulation', 'Request ID', 'Request Type', 'Score', 'Skip', 'Status', 'Tracker Count', 'Translations', and 'Vendors Count'. |
Output
JSON
Status Code- HTTP status code indicating the result of the publish operation, e.g., '204 No Content' for success without content.
Dependencies
- Didomi API with API Key and API Secret credentials
Troubleshooting
- Missing or invalid API Key or API Secret will cause authentication failure.
- Required parameters such as Widget ID must be provided; otherwise, the node throws an error indicating the missing parameter.
- API errors from Didomi are caught and rethrown with detailed messages to help diagnose issues.
Links
- Didomi API - Publish Widget - Official API documentation for the Publish Widget operation in Didomi API.