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
Cms Slot → Create Cms Slot
AI-generatedOverview
This node operation creates a CMS Slot in the Shopware system. It is useful for users who want to programmatically add new content slots to their CMS blocks, enabling dynamic content management and customization within their Shopware storefronts. For example, a user can create a new slot with specific configurations, data, and custom fields to display unique content on their website.
Use Case Examples
- Creating a new CMS Slot with a specific type and slot name to add custom content to a page section.
- Adding a locked CMS Slot with detailed configuration and custom fields for advanced content control.
Properties
| Name | Meaning |
|---|---|
| Response | Data format for the response, either basic or detailed. |
| Id | Unique identifier for the CMS Slot. |
| Version Id | Version identifier for the CMS Slot. |
| Type | Type of the CMS Slot. |
| Slot | Name of the slot. |
| Locked | Indicates if the slot is locked. |
| Config | JSON configuration for the slot. |
| Custom Fields | Custom fields in JSON format for the slot. |
| Data | Data in JSON format associated with the slot. |
| Block Id | Identifier of the block to which the slot belongs. |
| Field Config | Field configuration in JSON format. |
| Cms Block Version Id | Version identifier for the CMS block. |
| Created At | Creation timestamp of the slot. |
| Updated At | Update timestamp of the slot. |
| Translated | Translated content in JSON format. |
| Block | Block data in JSON format, representing the structure and related entities of the CMS block. |
Output
JSON
id- Unique identifier of the created CMS Slot.type- Type of the created CMS Slot.slot- Name of the created slot.locked- Lock status of the created slot.config- Configuration details of the created slot.customFields- Custom fields associated with the created slot.data- Data associated with the created slot.blockId- Identifier of the block to which the slot belongs.fieldConfig- Field configuration of the created slot.cmsBlockVersionId- Version identifier of the CMS block.createdAt- Creation timestamp of the slot.updatedAt- Update timestamp of the slot.translated- Translated content of the slot.block- Block data representing the CMS block structure and related entities.
Dependencies
- An API key credential for Shopware Admin API
Troubleshooting
- Ensure all required fields (Id, Type, Slot, Block Id) are provided to avoid validation errors.
- Check the JSON format for fields like Config, Custom Fields, Data, Field Config, Translated, and Block to prevent parsing errors.
- Verify API credentials and base URL configuration to avoid authentication or connection issues.