Mailchimp Transactional – Messages and Senders

Configuration Table:

Input Options:

• Input: Allows dynamic inputs, e.g., from a previous step.
• Default Value: You can specify a fixed attribute.

(*) required field

Configuration Table:

Input Options:

• Input: Allows dynamic inputs, e.g., from a previous step.
• Default Value: You can specify a fixed attribute.

(*) required field

Configuration Table:

Input Options:

• Input: Allows dynamic inputs, e.g., from a previous step.
• Default Value: You can specify a fixed attribute.

(*) required field

Configuration Table:

Input Options:

• Input: Allows dynamic inputs, e.g., from a previous step.
• Default Value: You can specify a fixed attribute.

(*) required field

Configuration Table:

Input Options:

• Input: Allows dynamic inputs, e.g., from a previous step.
• Default Value: You can specify a fixed attribute.

(*) required field

Configuration Table:

Input Options:

• Input: Allows dynamic inputs, e.g., from a previous step.
• Default Value: You can specify a fixed attribute.

(*) required field

Configuration Table:

Input Options:

• Input: Allows dynamic inputs, e.g., from a previous step.
• Default Value: You can specify a fixed attribute.

(*) required field

Configuration Table:

Input Options:

• Input: Allows dynamic inputs, e.g., from a previous step.
• Default Value: You can specify a fixed attribute.

Name*	Send Message
Connection*	Select your connection or create one.
MAP FIELDS [+ Add Field] add optional fields from a dynamic list: Async, IP Pool, Send at.
Message* the information on the message to send.	From Email*: the sender email address. From Name*: optional from name to be used. To*: Recipient information [+Element] add additional recipient. Email: the email address of the recipient. Name: the optional display name to use for the recipient. Subject*: the message subject. [+ Add Field] add optional field in Message: CC ВСС Body HTML: the full HTML content to be sent. Body Text: optional full text content to be sent. Headers: optional extra headers to add to the message (most headers are allowed) [+Element] can add additional element by clicking on this button. Type Value Important: whether or not this message is important, and should be delivered ahead of non-important messages. Track Opens: whether or not to turn on open tracking for the message. Track Clicks: whether or not to turn on click tracking for the message. Auto Text: whether or not to automatically generate a text part for messages that are not given text. Auto HTML: whether or not to automatically generate an HTML part for messages that are not given HTML. Inline CSS: whether or not to automatically inline all CSS styles provided in the message HTML – only for HTML documents less than 256KB in size. URL Stripe Query String: whether or not to strip the query string from URLs when aggregating tracked URL data. Preserve Recipients: whether or not to expose all recipients in to “To” header for each email. View Content Link: set to false to remove content logging for sensitive emails. BCC Address: an optional address to receive an exact copy of each recipient’s email. Tracking Domain: a custom domain to use for tracking opens and clicks instead of mandrillapp.com. Signing Domain: a custom domain to use for SPF/DKIM signing instead of mandrill (for “via” or “on behalf of” in email clients). Return path Domain: a custom domain to use for the messages’s return-path. Merge: whether to evaluate merge tags in the message. Will automatically be set to true if either merge_vars or global_merge_vars are provided. Merge Language: the merge tag language to use when evaluating merge tags, either mailchimp or handlebars Possible values: "mailchimp" or "handlebars". Global Merge Variables: global merge variables to use for all recipients. You can override these per recipient. [+Element] add additional element. Name: the global merge variable’s name. Merge variable names are case-insensitive and may not start with” _”. Content: the global merge variable’s content. Merge Variables: per-recipient merge variables, which override global merge variables with the same name. [+Element] add additional element. Recipient: the email address of the recipient that the merge variables should apply to Variables: the recipient’s merge variables [+Element] add additional element. Name: the merge variable’s name. Merge variable names are case-insensitive and may not start with “_”. Content: the merge variable’s content. Tags: an array of string to tag the message with. Stats are accumulated using tags, though we only store the first 100 we see, so this should not be unique or change frequently. Tags should be 50 characters or less. Any tags starting with an underscore are reserved for internal use and will cause errors. [+Element] add additional element. Value: Tag name Sub Account ID: the unique id of a subaccount for this message – must already exist or will fail with an error. Google Analytics Domains: an array of strings indicating for which any matching URLs will automatically have Google Analytics parameters appended to their query string automatically. [+Element] add additional element. Google Analytics Domains: optional string indicating the value to set for the utm_campaign tracking parameter. If this isn’t provided the email’s from address will be used instead. Metadata: metadata an associative array of user metadata. Mandrill will store this metadata and make it available for retrieval. In addition, you can select up to 10 metadata fields to index and make searchable using the Mandrill search api. Website: a valid website url Recipient Metadata: Per-recipient metadata that will override the global values specified in the metadata parameter. [+Element] add additional element. Recipient: the email address of the recipient that the metadata is associated with. Values: an associated array containing the recipient’s unique metadata. If a key exists in both the per-recipient metadata and the global metadata, the per-recipient metadata will be used. Attachments: attachments to add to the message. [+Element] add additional element. MIME Type: the MIME type of the attachment Name: the file name of the attachment Content: (Base64 Encoded), see more details in Base64 Encoding documentation. Images: an array of embedded images to add to the message [+Element] add additional element. MIME Type: the MIME type of the image – must start with “image/” Name: the Content ID of the image – use  to reference the image in your HTML content. Content: (Base64 Encoded), see more details in Base64 Encoding documentation.
Async	Enable a background sending mode that is optimized for bulk sending. In async mode, messages/send will immediately return a status of “queued” for every recipient. To handle rejections when sending in async mode, set up a webhook for the ‘reject’ event. Defaults to false for messages with no more than 10 recipients; messages with more than 10 recipients are always sent asynchronously, regardless of the value of async.
IP Pool	The name of the dedicated ip pool that should be used to send the message. If you do not have any dedicated IPs, this parameter has no effect. If you specify a pool that does not exist, your default pool will be used instead.
Send at	When this message should be sent as a UTC timestamp in YYYY-MM-DD HH:MM:SS format. If you specify a time in the past, the message will be sent immediately; for future dates, you’re limited to one year from the date of scheduling.

(*) required field

Configuration Table:

Input Options:

• Input: Allows dynamic inputs, e.g., from a previous step.
• Default Value: You can specify a fixed attribute.

Name*	Send Message Template
Connection*	Select your connection or create one.
MAP FIELDS [+ Add Field] add optional fields from a dynamic list: Async, IP Pool, Send at.
Template Name*	Select the template to send from a dynamic list.
Template Content* Template content to send.	Name: the name of the mc:edit editable region to inject into Content: the content to inject For more details, see Mailchimp Template language, Create editable content.
Message* the other information on the message to send.	From Email*: the sender email address. From Name*: optional from name to be used. To*: Recipient information [+Element] add additional recipient. Email: the email address of the recipient. Name: the optional display name to use for the recipient. Subject*: the message subject. [+ Add Field] add optional field in Message: CC ВСС Body HTML: the full HTML content to be sent. Body Text: optional full text content to be sent. Headers: optional extra headers to add to the message (most headers are allowed) [+Element] can add additional element by clicking on this button. Type Value Important: whether or not this message is important, and should be delivered ahead of non-important messages. Track Opens: whether or not to turn on open tracking for the message. Track Clicks: whether or not to turn on click tracking for the message. Auto Text: whether or not to automatically generate a text part for messages that are not given text. Auto HTML: whether or not to automatically generate an HTML part for messages that are not given HTML. Inline CSS: whether or not to automatically inline all CSS styles provided in the message HTML – only for HTML documents less than 256KB in size. URL Stripe Query String: whether or not to strip the query string from URLs when aggregating tracked URL data. Preserve Recipients: whether or not to expose all recipients in to “To” header for each email. View Content Link: set to false to remove content logging for sensitive emails. BCC Address: an optional address to receive an exact copy of each recipient’s email. Tracking Domain: a custom domain to use for tracking opens and clicks instead of mandrillapp.com. Signing Domain: a custom domain to use for SPF/DKIM signing instead of mandrill (for “via” or “on behalf of” in email clients). Return path Domain: a custom domain to use for the messages’s return-path. Merge: whether to evaluate merge tags in the message. Will automatically be set to true if either merge_vars or global_merge_vars are provided. Merge Language: the merge tag language to use when evaluating merge tags, either mailchimp or handlebars Possible values: "mailchimp" or "handlebars". Global Merge Variables: global merge variables to use for all recipients. You can override these per recipient. [+Element] add additional element. Name: the global merge variable’s name. Merge variable names are case-insensitive and may not start with” _”. Content: the global merge variable’s content. Merge Variables: per-recipient merge variables, which override global merge variables with the same name. [+Element] add additional element. Recipient: the email address of the recipient that the merge variables should apply to Variables: the recipient’s merge variables [+Element] add additional element. Name: the merge variable’s name. Merge variable names are case-insensitive and may not start with “_”. Content: the merge variable’s content. Tags: an array of string to tag the message with. Stats are accumulated using tags, though we only store the first 100 we see, so this should not be unique or change frequently. Tags should be 50 characters or less. Any tags starting with an underscore are reserved for internal use and will cause errors. [+Element] add additional element. Value: Tag name Sub Account ID: the unique id of a subaccount for this message – must already exist or will fail with an error. Google Analytics Domains: an array of strings indicating for which any matching URLs will automatically have Google Analytics parameters appended to their query string automatically. [+Element] add additional element. Google Analytics Domains: optional string indicating the value to set for the utm_campaign tracking parameter. If this isn’t provided the email’s from address will be used instead. Metadata: metadata an associative array of user metadata. Mandrill will store this metadata and make it available for retrieval. In addition, you can select up to 10 metadata fields to index and make searchable using the Mandrill search api. Website: a valid website url Recipient Metadata: Per-recipient metadata that will override the global values specified in the metadata parameter. [+Element] add additional element. Recipient: the email address of the recipient that the metadata is associated with. Values: an associated array containing the recipient’s unique metadata. If a key exists in both the per-recipient metadata and the global metadata, the per-recipient metadata will be used. Attachments: attachments to add to the message. [+Element] add additional element. MIME Type: the MIME type of the attachment Name: the file name of the attachment Content: (Base64 Encoded), see more details in Base64 Encoding documentation. Images: an array of embedded images to add to the message [+Element] add additional element. MIME Type: the MIME type of the image – must start with “image/” Name: the Content ID of the image – use  to reference the image in your HTML content. Content: (Base64 Encoded), see more details in Base64 Encoding documentation.
Async	Enable a background sending mode that is optimized for bulk sending. In async mode, messages/send will immediately return a status of “queued” for every recipient. To handle rejections when sending in async mode, set up a webhook for the ‘reject’ event. Defaults to false for messages with no more than 10 recipients; messages with more than 10 recipients are always sent asynchronously, regardless of the value of async.
IP Pool	The name of the dedicated ip pool that should be used to send the message. If you do not have any dedicated IPs, this parameter has no effect. If you specify a pool that does not exist, your default pool will be used instead.
Send at	When this message should be sent as a UTC timestamp in YYYY-MM-DD HH:MM:SS format. If you specify a time in the past, the message will be sent immediately; for future dates, you’re limited to one year from the date of scheduling.

(*) required field

Configuration Table:

Input Options:

• Input: Allows dynamic inputs, e.g., from a previous step.
• Default Value: You can specify a fixed attribute.

(*) required field

Configuration Table:

Input Options:

• Input: Allows dynamic inputs, e.g., from a previous step.
• Default Value: You can specify a fixed attribute.

(*) required field

Configuration Table:

Input Options:

• Input: Allows dynamic inputs, e.g., from a previous step.
• Default Value: You can specify a fixed attribute.

(*) required field

Configuration Table:

Input Options:

• Input: Allows dynamic inputs, e.g., from a previous step.
• Default Value: You can specify a fixed attribute.

(*) required field

Configuration Table:

Input Options:

• Input: Allows dynamic inputs, e.g., from a previous step.
• Default Value: You can specify a fixed attribute.

(*) required field

Configuration Table:

Input Options:

• Input: Allows dynamic inputs, e.g., from a previous step.
• Default Value: You can specify a fixed attribute.

(*) required field

Configuration Table:

Input Options:

• Input: Allows dynamic inputs, e.g., from a previous step.
• Default Value: You can specify a fixed attribute.

(*) required field