Actions778
- Acl Role Actions
- App Actions
- App Action Button Actions
- App Administration Snippet Actions
- App Cms Block Actions
- App Flow Action Actions
- App Flow Event Actions
- App Payment Method Actions
- App Script Condition Actions
- App Shipping Method Actions
- App Template Actions
- Category Actions
- Cms Block Actions
- Cms Page Actions
- Cms Section Actions
- Cms Slot Actions
- Country Actions
- Country State Actions
- Currency Actions
- Currency Country Rounding Actions
- Custom Entity Actions
- Custom Field Actions
- Custom Field Set Actions
- Custom Field Set Relation Actions
- Customer Actions
- Customer Address Actions
- Customer Group Actions
- Customer Recovery Actions
- Customer Wishlist Actions
- Customer Wishlist Product Actions
- Delivery Time Actions
- Document Actions
- Document Base Config Actions
- Document Base Config Sales Channel Actions
- Document Type Actions
- Flow Actions
- Flow Sequence Actions
- Flow Template Actions
- Import Export File Actions
- Import Export Log Actions
- Import Export Profile Actions
- Integration Actions
- Landing Page Actions
- Language Actions
- Locale Actions
- Log Entry Actions
- Mail Header Footer Actions
- Mail Template Actions
- Mail Template Type Actions
- Main Category Actions
- Media Actions
- Media Default Folder Actions
- Media Folder Actions
- Media Folder Configuration Actions
- Media Thumbnail Actions
- Media Thumbnail Size Actions
- Newsletter Recipient Actions
- Notification Actions
- Number Range Actions
- Number Range Sales Channel Actions
- Number Range State Actions
- Number Range Type Actions
- Order Actions
- Order Customer Actions
- Order Delivery Actions
- Order Delivery Position Actions
- Order Line Item Actions
- Order Line Item Download Actions
- Order Transaction Actions
- Order Transaction Capture Actions
- Order Transaction Capture Refund Actions
- Order Transaction Capture Refund Position Actions
- Payment Method Actions
- Plugin Actions
- Product Actions
- Product Configurator Setting Actions
- Product Cross Selling Actions
- Product Cross Selling Assigned Products Actions
- Product Download Actions
- Product Export Actions
- Product Feature Set Actions
- Product Keyword Dictionary Actions
- Product Manufacturer Actions
- Product Media Actions
- Product Price Actions
- Product Review Actions
- Product Search Config Actions
- Product Search Config Field Actions
- Product Search Keyword Actions
- Product Sorting Actions
- Product Stream Actions
- Product Stream Filter Actions
- Product Visibility Actions
- Promotion Actions
- Promotion Discount Actions
- Promotion Discount Prices Actions
- Promotion Individual Code Actions
- Promotion Sales Channel Actions
- Promotion Setgroup Actions
- Property Group Actions
- Property Group Option Actions
- Rule Actions
- Rule Condition Actions
- Sales Channel Actions
- Sales Channel Analytics Actions
- Sales Channel Domain Actions
- Sales Channel Type Actions
- Salutation Actions
- Scheduled Task Actions
- State Machine Transition Actions
- System Config Actions
- Tag Actions
- Tax Actions
- Tax Provider Actions
- Tax Rule Actions
- Tax Rule Type Actions
- Theme Actions
- Unit Actions
- User Actions
- User Access Key Actions
- User Config Actions
- User Recovery Actions
- Webhook Actions
- Webhook Event Log Actions
- System Info Health Check Actions
- Bulk Operations Actions
- Document Management Actions
- Asset Management Actions
- Mail Operations Actions
- System Operations Actions
- Customer Impersonation Actions
- Order Management Actions
- Order Address Actions
- Authorization Authentication Actions
Document Type → Update Document Type
AI-generatedOverview
This node operation updates an existing Document Type in the Shopware system. It allows users to modify various attributes of a Document Type such as its identifier, name, technical name, timestamps, custom fields, translations, and associated documents and configurations. This operation is useful in scenarios where document metadata or configurations need to be changed or maintained programmatically within an automation workflow.
Use Case Examples
- Updating the name and technical name of a Document Type to reflect new business requirements.
- Modifying custom fields or translations of a Document Type to support localization or additional metadata.
- Adjusting associated documents or document base configurations linked to a Document Type for compliance or operational changes.
Properties
| Name | Meaning |
|---|---|
| Id | Identifier for the document_type, used to specify which Document Type to update. |
| Response | Data format for response; controls the response format returned by the API call. |
| Name | The new name to assign to the Document Type. |
| Technical Name | The new technical name to assign to the Document Type. |
| Created At | Timestamp indicating when the Document Type was created. |
| Updated At | Timestamp indicating when the Document Type was last updated. |
| Custom Fields | Custom JSON fields to add or update on the Document Type. |
| Translated | Translated fields in JSON format for localization support. |
| Documents | JSON array representing documents associated with the Document Type. |
| Document Base Configs | JSON array representing base configurations related to the Document Type. |
| Document Base Config Sales Channels | JSON array representing sales channel configurations for the Document Base Configs. |
Output
JSON
id- Identifier of the updated Document Type.name- Name of the updated Document Type.technicalName- Technical name of the updated Document Type.createdAt- Creation timestamp of the Document Type.updatedAt- Last update timestamp of the Document Type.customFields- Custom fields associated with the Document Type.translated- Translated fields for localization.documents- Documents associated with the Document Type.documentBaseConfigs- Base configurations related to the Document Type.documentBaseConfigSalesChannels- Sales channel configurations for the Document Base Configs.
Dependencies
- An API key credential for Shopware Admin API
Troubleshooting
- Ensure the 'Id' property is correctly set to the existing Document Type identifier to avoid 'not found' errors.
- Validate JSON format for 'Custom Fields', 'Translated', 'Documents', 'Document Base Configs', and 'Document Base Config Sales Channels' to prevent parsing errors.
- Check API credentials and permissions to ensure the node can update Document Types in Shopware.
- Timeout or network issues may occur; adjust 'Timeout' and 'Proxy' settings in Request Options if needed.