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
Rule Condition → Create Rule Condition
AI-generatedOverview
This node operation creates a new Rule Condition in the Shopware system. It is useful for automating the creation of rule conditions that define specific criteria or logic within Shopware's rule engine, such as conditions for promotions, shipping methods, or other business rules. For example, a user can create a rule condition specifying a type, associated rule ID, and other parameters to dynamically manage business logic in Shopware.
Use Case Examples
- Create a rule condition with a specific type and rule ID to apply a discount only to certain products.
- Add a nested rule condition with custom fields and script conditions to handle complex business logic.
Properties
| Name | Meaning |
|---|---|
| Response | Data format for response, either basic or detailed. |
| Id | Unique identifier for the rule condition. |
| Type | Type of the rule condition. |
| Rule Id | Identifier of the rule to which this condition belongs. |
| Script Id | Identifier for an associated script, if any. |
| Parent Id | Identifier of the parent rule condition, if nested. |
| Value | JSON object representing the value or parameters of the condition. |
| Position | Position or order of the condition within the rule. |
| Custom Fields | Custom fields as a JSON object for additional data. |
| Created At | Timestamp of when the condition was created. |
| Updated At | Timestamp of the last update to the condition. |
| Rule | JSON object representing the full rule structure associated with the condition. |
| App Script Condition | JSON object representing app script conditions related to the rule condition. |
| Parent | JSON object representing the parent rule condition structure. |
| Children | JSON array representing child rule conditions nested under this condition. |
| Request Options | Settings for request behavior such as batching, SSL, proxy, and timeout. |
Output
JSON
id- Unique identifier of the created rule condition.type- Type of the created rule condition.ruleId- Identifier of the rule associated with the condition.scriptId- Identifier of the associated script, if any.parentId- Identifier of the parent condition, if nested.value- Value or parameters of the condition as a JSON object.position- Position of the condition within the rule.customFields- Custom fields data as JSON.createdAt- Creation timestamp.updatedAt- Last update timestamp.rule- Full rule structure as JSON.appScriptCondition- App script condition data as JSON.parent- Parent condition structure as JSON.children- Child conditions as JSON array.
Dependencies
- Shopware API with authentication credentials
Troubleshooting
- Ensure all required fields (Id, Type, Rule Id) are provided to avoid validation errors.
- Check JSON formatting for fields like Value, Custom Fields, Rule, App Script Condition, Parent, and Children to prevent parsing errors.
- Verify API credentials and endpoint URL to avoid authentication or connection issues.
- If using custom scripts or nested conditions, ensure the JSON structure matches Shopware's expected schema to prevent errors.