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
Locale → Create Locale
AI-generatedOverview
This node operation creates a new Locale in the Shopware system. It is useful for scenarios where you need to add localization settings such as language, territory, and other locale-specific details to support multi-language or region-specific content in an e-commerce platform. For example, you can create a locale for a new market by specifying its code, name, territory, and associated languages and users.
Use Case Examples
- Creating a new locale for the French market with code 'fr-FR', name 'French (France)', and territory 'France'.
- Adding custom fields and translated content to a locale to support specific business requirements.
Properties
| Name | Meaning |
|---|---|
| Response | Data format for the response, either basic or detailed. |
| Id | Unique identifier for the locale to be created. |
| Code | Locale code representing the language and region, e.g., 'en-US'. |
| Name | Name of the locale. |
| Territory | Territory or region associated with the locale. |
| Custom Fields | Custom JSON fields to add additional data to the locale. |
| Created At | Timestamp for when the locale was created. |
| Updated At | Timestamp for when the locale was last updated. |
| Translated | JSON object containing translated content for the locale. |
| Languages | JSON array defining languages associated with the locale. |
| Users | JSON array defining users associated with the locale. |
Output
JSON
id- Unique identifier of the created locale.code- Locale code of the created locale.name- Name of the created locale.territory- Territory of the created locale.customFields- Custom fields associated with the locale.createdAt- Creation timestamp of the locale.updatedAt- Last update timestamp of the locale.translated- Translated content of the locale.languages- Languages associated with the locale.users- Users associated with the locale.
Dependencies
- An API key credential for Shopware Admin API
Troubleshooting
- Ensure all required fields (Id, Code, Name, Territory) are provided to avoid validation errors.
- If the API returns authentication errors, verify that the Shopware Admin API credentials are correctly configured.
- For JSON fields like Custom Fields, Translated, Languages, and Users, ensure the JSON is well-formed to prevent parsing errors.