Wiresk

Wiresk

Mailchimp Transactional – Messages and Senders

Estimated reading time: 11 min

What your automation will do…

A connection to your Mailchimp Transactional account is needed so we can sync it with our platform.
Refer to Mailchimp Transactional – create a connection.
Email scheduling is only available with Mailchimp Essentials plan or higher.
Cancel a specific scheduled emails.Note that, email scheduling is only available with Mailchimp Essentials plan or higher.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Cancel Scheduled Email
Connection*Select your connection or create one.
Scheduled Email ID*Select the specific scheduled email from a dynamic list.

(*) required field

Get details information of a specific recently sent message.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Get a Message
Connection*Select your connection or create one.
MAP FIELDS [+ Add Field] add optional fields from a dynamic list : If not Found Consider as.
Message ID*Select your recent message from a dynamic list.
If not Found Consider as:Success – When the record is not found during execution, the system does not treat this as an error. Instead, it considers the operation successful and continues with the workflow.

Failed – Wiresk treats this as an error or failure. The workflow stops or takes a predefined failure action.

(*) required field

Retrieve a list of your scheduled emails.
Note that, email scheduling is only available with Mailchimp Essentials plan or higher.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*List Scheduled Emails
Connection*Select your connection or create one.
MAP FIELDS [+ Add Field] add optional fields from a dynamic list : To.
ToOptional recipient address to filter results to.

(*) required field

icon mailchimp 1 Mailchimp Transactional - Messages and Senders Get a Message Content Copy Link

Get the full content of a recently sent message.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Get a Message Content
Connection*Select your connection or create one.
MAP FIELDS [+ Add Field] add optional fields from a dynamic list : If not Found Consider as.
Message ID*Select your recent message from a dynamic list.
If not Found Consider as:Success – When the record is not found during execution, the system does not treat this as an error. Instead, it considers the operation successful and continues with the workflow.

Failed – Wiresk treats this as an error or failure. The workflow stops or takes a predefined failure action.

(*) required field

This Method reschedules a scheduled email.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Reschedule Email
Connection*Select your connection or create one.
MAP FIELDS [+ Add Field] add optional fields from a dynamic list : If not Found Consider as.
Scheduled Email ID*Select the scheduled email from a dynamic list.
Send at*The new UTC timestamp when the message should sent. Mandrill can’t time travel, so if you specify a time in past the message will be sent immediately; for future dates, you’re limited to one year from the date of scheduling.

(*) required field

Search recently sent messages and optionally filter by date range, tags, senders, and API keys. If no date range is specified, results within the last 7 days are returned. This method may be called up to 20 times per minute.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Search Message by Date
Connection*Select your connection or create one.
MAP FIELDS [+ Add Field] add optional fields from a dynamic list:
Query(Search)This field allows you to search for messages using specific keywords or phrases.
Start dateSet the beginning date of the search range.
End DateSet the end date of the search range.
TagsYou can filter messages by specific tags. You can add multiple tags by clicking the “+Element” button.
SendersYou can filter messages by the sender’s email address. You can add multiple senders by clicking the “+Element” button.
API keyYou can specify an API key to narrow the search, this will return messages sent by ANY of the keys. You can add multiple API keys by clicking the “+Element” button.
LimitThe maximum number of results to return, defaults is 100, 1000 is the maximum.

(*) required field

Search recently sent messages and optionally filter by date range, tags, senders, and return the aggregated hourly stats for matching messages.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Search Message by Hour
Connection*Select your connection or create one.
MAP FIELDS [+ Add Field] add optional fields from a dynamic list:
SearchThis field allows you to search for messages using specific keywords or phrases.
Start dateSet the beginning date and time of the search range.
End DateSet the end date and time of the search range.
TagsYou can filter messages by specific tags. You can add multiple tags by clicking the “+Element” button.
SendersYou can filter messages by the sender’s email address. You can add multiple senders by clicking the “+Element” button.

(*) required field

Send a new transactional message through the Transactional API.

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 cid:THIS VALUE Mailchimp Transactional - Messages and Senders to reference the image in your HTML content.
Content: (Base64 Encoded), see more details in Base64 Encoding documentation.
AsyncEnable 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 PoolThe 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 atWhen 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

Send a new transactional message through the Transactional API using a template.

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 cid:THIS VALUE Mailchimp Transactional - Messages and Senders to reference the image in your HTML content.
Content: (Base64 Encoded), see more details in Base64 Encoding documentation.
AsyncEnable 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 PoolThe 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 atWhen 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

Adds a sender domain to your account. Sender domains are added automatically as you send, but you can use this call to add them ahead of time.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Add a Sender Domain
Connection*Select your connection or create one.
Domain*Enter your domain name.

(*) required field

Checks the SPF and DKIM settings for a domain, as well the domain verification. If you haven’t already added this domain to your account, it will be added automatically.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Check Domain Setting
Connection*Select your connection or create one.
Domain*Enter your domain name.

(*) required field

Return more detailed information about a single sender, including aggregates of recent stats.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Get Sender Info
Connection*Select your connection or create one.
Email Address*Enter the sender’s email address to retrieve their information.

(*) required field

Return the senders that have tried to use this account, both verified and unverified.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*List Account Senders
Connection*Select your connection or create one.

(*) required field

Returns the sender domains that have been added to this account.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*List Sender Domains
Connection*Select your connection or create one.

(*) required field

This process sends a verification email to confirm domain ownership. Domain verification is mandatory. After a domain is verified in one Transactional API account, other accounts cannot use it for message signing unless they also verify it. This prevents unauthorized use of your domain by other accounts.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Verify Domain
Connection*Select your connection or create one.
Domain*Domain name at which you can receive email
Mailbox*A mailbox at the domain where the verification email should be sent

(*) required field

Return the recent history (hourly stats for the last 30 days) for a sender.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*View Sender History
Connection*Select your connection or create one.
MAP FIELDS [+ Add Field] add optional fields from a dynamic list : If not Found Consider as.
Email Address*Enter the sender’s email address to retrieve historical data,
If not Found Consider as:Success – When the record is not found during execution, the system does not treat this as an error. Instead, it considers the operation successful and continues with the workflow.

Failed – Wiresk treats this as an error or failure. The workflow stops or takes a predefined failure action.

(*) required field

Once your Flow is configured, you can test or automate it using the Run panel or by managing Triggers from the Flow Management screen.

  • Run Flow: Manually runs the Flow once using sample data. Ideal for testing logic and field mapping. See How to Run a Flow.
  • Run Scheduler: Force-runs the Trigger immediately using live input. This bypasses the recurrence rule and is useful for verifying real data mapping. Learn more in Wiresk Scheduler – The Fundamentals.

From the Trigger management panel (clock icon), you can:

  • Activate or deactivate Triggers
  • Force-run the scheduler
  • Copy Routing Keys (for HTTP Triggers)

If your Flow uses a Webhook Trigger, it runs automatically on each incoming webhook—no scheduler required. It remains active until you manually deactivate it.