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
Mail Header Footer → Create Mail Header Footer
AI-generatedOverview
This node operation allows users to create a Mail Header Footer entity in the Shopware system. It is useful for managing email templates by defining headers and footers in both HTML and plain text formats, along with metadata such as name, description, and system default status. This operation is beneficial for automating email template management in e-commerce workflows, ensuring consistent branding and messaging in customer communications.
Use Case Examples
- Creating a new mail header and footer template with custom HTML and plain text content for marketing emails.
- Setting up system default mail header and footer for transactional emails in an online store.
Properties
| Name | Meaning |
|---|---|
| Response | Specifies the data format for the response, either basic or detailed. |
| Id | Unique identifier for the mail header footer entity. |
| System Default | Indicates if this mail header footer is the system default. |
| Name | Name of the mail header footer. |
| Description | Description of the mail header footer. |
| Header Html | HTML content for the mail header. |
| Header Plain | Plain text content for the mail header. |
| Footer Html | HTML content for the mail footer. |
| Footer Plain | Plain text content for the mail footer. |
| Created At | Timestamp for when the mail header footer was created. |
| Updated At | Timestamp for when the mail header footer was last updated. |
| Translated | JSON object containing translations for the mail header footer. |
| Sales Channels | JSON array defining sales channels associated with the mail header footer. |
| Request Options | Node-level request options such as batching, SSL handling, proxy, and timeout settings. |
Output
JSON
id- Unique identifier of the created mail header footer.name- Name of the created mail header footer.description- Description of the created mail header footer.systemDefault- Indicates if the created mail header footer is the system default.headerHtml- HTML content of the mail header.headerPlain- Plain text content of the mail header.footerHtml- HTML content of the mail footer.footerPlain- Plain text content of the mail footer.createdAt- Creation timestamp of the mail header footer.updatedAt- Last update timestamp of the mail header footer.translated- Translations associated with the mail header footer.salesChannels- Sales channels linked to the mail header footer.
Dependencies
- An API key credential for Shopware Admin API
Troubleshooting
- Ensure all required fields such as 'Id' and 'Name' are provided to avoid validation errors.
- Check API credentials and base URL configuration if authentication errors occur.
- If the response format is not as expected, verify the '_response' property value (basic or detail).
- For large payloads in 'Sales Channels' or 'Translated' JSON fields, ensure the JSON is correctly formatted to prevent parsing errors.