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
Language → Create Language
AI-generatedOverview
This node operation creates a new language entity in the Shopware system. It is useful for managing multilingual content by adding new languages with detailed configurations such as locale, translation codes, parent-child relationships, sales channels, customers, orders, and other related entities. For example, it can be used to add a new language to an e-commerce platform to support additional customer regions or to customize language settings for specific sales channels.
Use Case Examples
- Adding a new language with specific locale and translation code to support a new market.
- Creating a language with custom fields and parent-child relationships for advanced localization setups.
Properties
| Name | Meaning |
|---|---|
| Response | Data format for response, either basic or detailed. |
| Id | Unique identifier for the language entity. |
| Parent Id | Identifier of the parent language, if any. |
| Locale Id | Identifier for the locale associated with the language. |
| Translation Code Id | Identifier for the translation code associated with the language. |
| Name | Name of the language. |
| Custom Fields | Custom fields for additional language metadata. |
| Created At | Creation timestamp of the language entity. |
| Updated At | Last update timestamp of the language entity. |
| Parent | JSON object representing the parent language entity with nested relations. |
| Locale | JSON object representing the locale details associated with the language. |
| Translation Code | JSON object representing the translation code details associated with the language. |
| Children | JSON array representing child languages of this language. |
| Sales Channels | JSON array representing sales channels associated with the language. |
| Sales Channel Default Assignments | JSON array representing default assignments for sales channels. |
| Sales Channel Domains | JSON array representing sales channel domains associated with the language. |
| Customers | JSON array representing customers associated with the language. |
| Newsletter Recipients | JSON array representing newsletter recipients associated with the language. |
| Orders | JSON array representing orders associated with the language. |
| Product Search Keywords | JSON array representing product search keywords associated with the language. |
| Product Keyword Dictionaries | JSON array representing product keyword dictionaries associated with the language. |
| Product Reviews | JSON array representing product reviews associated with the language. |
| Product Search Config | JSON object representing product search configuration associated with the language. |
Output
JSON
id- Unique identifier of the created language.name- Name of the created language.localeId- Locale identifier associated with the language.parentId- Parent language identifier, if any.translationCodeId- Translation code identifier associated with the language.customFields- Custom fields data of the language.createdAt- Creation timestamp of the language.updatedAt- Last update timestamp of the language.parent- Parent language entity details.locale- Locale details associated with the language.translationCode- Translation code details associated with the language.children- Child languages of the created language.salesChannels- Sales channels associated with the language.salesChannelDefaultAssignments- Default assignments for sales channels.salesChannelDomains- Sales channel domains associated with the language.customers- Customers associated with the language.newsletterRecipients- Newsletter recipients associated with the language.orders- Orders associated with the language.productSearchKeywords- Product search keywords associated with the language.productKeywordDictionaries- Product keyword dictionaries associated with the language.productReviews- Product reviews associated with the language.productSearchConfig- Product search configuration associated with the language.
Dependencies
- An API key credential for Shopware Admin API
Troubleshooting
- Ensure all required fields (Id, Locale Id, Name) are provided to avoid validation errors.
- Verify JSON format correctness for complex JSON input fields like Parent, Locale, Translation Code, Children, Sales Channels, etc.
- Check API credentials and base URL configuration to ensure successful API communication.
- If the API returns errors related to relationships (e.g., parent or translation code), verify that referenced entities exist in the Shopware system.