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
Salutation → Create Salutation
AI-generatedOverview
This node operation allows creating a new Salutation resource in the Shopware system. It is useful for scenarios where you need to add personalized salutations for customers, such as Mr., Mrs., Dr., etc., to enhance customer communication and data management. For example, you can create a salutation with specific keys, display names, and associated customer data to tailor your e-commerce platform's user experience.
Use Case Examples
- Creating a new salutation entry with a unique ID, salutation key, display name, and letter name to be used in customer profiles.
- Adding custom fields and translations to a salutation to support multiple languages and additional metadata.
- Associating customers, customer addresses, order customers, order addresses, and newsletter recipients with the new salutation for comprehensive data linkage.
Properties
| Name | Meaning |
|---|---|
| Response | Data format for response, either basic or detailed. |
| Id | Unique identifier for the salutation. |
| Salutation Key | Key representing the salutation. |
| Display Name | Display name of the salutation. |
| Letter Name | Letter name associated with the salutation. |
| Custom Fields | Custom fields in JSON format for additional salutation data. |
| Created At | Creation timestamp of the salutation. |
| Updated At | Last update timestamp of the salutation. |
| Translated | Translations in JSON format for the salutation. |
| Customers | JSON array of customers associated with the salutation. |
| Customer Addresses | JSON array of customer addresses associated with the salutation. |
| Order Customers | JSON array of order customers associated with the salutation. |
| Order Addresses | JSON array of order addresses associated with the salutation. |
| Newsletter Recipients | JSON array of newsletter recipients associated with the salutation. |
Output
JSON
id- Unique identifier of the created salutation.salutationKey- Key representing the salutation.displayName- Display name of the salutation.letterName- Letter name associated with the salutation.customFields- Custom fields data of the salutation.createdAt- Creation timestamp of the salutation.updatedAt- Last update timestamp of the salutation.translated- Translations data of the salutation.customers- Associated customers data.customerAddresses- Associated customer addresses data.orderCustomers- Associated order customers data.orderAddresses- Associated order addresses data.newsletterRecipients- Associated newsletter recipients data.
Troubleshooting
- Ensure all required fields (Id, Salutation Key, Display Name, Letter Name) are provided to avoid validation errors.
- Verify JSON format correctness for fields like Custom Fields, Translated, Customers, Customer Addresses, Order Customers, Order Addresses, and Newsletter Recipients to prevent parsing errors.
- Check API credentials and endpoint URL configuration to ensure successful connection to the Shopware API.