Wiresk

Wiresk

Mailchimp Transactional – Sub Accounts and Templates

Estimated reading time: 5 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.
Delete an existing subaccount. Any email related to the subaccount will be saved, but stats will be removed and any future sending calls to this subaccount will fail.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Delete a Sub Account
Connection*Select your connection or create one.
Sub Account ID*Select the Subaccount to delete from your Mailchimp transactional.

(*) required field

Get information about a selected Sub Account.

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 Sub Accounts
Connection*Select your connection or create one.
MAP FIELDS [+ Add Field] add optional fields from a dynamic list : If not Found Consider as.
Sub Account ID*Select the Sub Account to get it info.
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

Get the list of subaccounts defined for the account, optionally filtered by a search.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*List Sub Accounts
Connection*Select your connection or create one.
MAP FIELDS [+ Add Field] add optional fields from a dynamic list : Search.
SearchFilter the result with a search.

(*) required field

Pause a subaccount’s sending. Any future emails delivered to this subaccount will be queued for a maximum of 3 days until the subaccount is resumed.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Pause a Sub Account
Connection*Select your connection or create one.
Sub Account ID*Select the Subaccount to Pause.

(*) required field

Resume a paused subaccount’s sending.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Pause a Sub Account
Connection*Select your connection or create one.
Sub Account ID*Select the Subaccount to Resume.

(*) required field

This method updates a sub-account. If the specified sub-account ID doesn’t exist, a new sub-account will be created instead.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Upsert a Sub Account
Connection*Select your connection or create one.
MAP FIELDS [+ Add Field] add optional fields from a dynamic list : Name, Notes, Custom Quota.
Sub Account ID*Enter your Sub Account ID (any name)
NameOptional display name to further identify the subaccount. If not specified, the Sub Account ID will be used.
NotesOptional extra text to associate with the subaccount.
Custom QuotaOptional manual hourly quota for the subaccount. If not specified, Mandrill will manage this based on reputation.

(*) required field

Add a new Template.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Create Template
Connection*Select your connection or create one.
MAP FIELDS [+ Add Field] add optional fields from a dynamic list.
Name*The name for the new template – must be unique.
Optional Fields:
From EmailDefault sending address for emails sent using this template.
From NameDefault from name to be used.
SubjectDefault subject line to be used.
CodeThe HTML code for the template with mc:edit attributes for the editable elements.
For more details, see Mailchimp Template language, Create editable content.
TextDefault text part to be used when sending with this template.
PublishSet to false to add a draft template without publishing.
Labels[+Element] Add multiple Labels, maximum 10 for filtering templates.
Value: Label name

(*) required field

Delete a template from your Mailchimp Transactional.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Delete Template
Connection*Select your connection or create one.
Template Name*Select the Template to delete.

(*) required field

Return the recent history (hourly stats for the last 30 days) for 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*Get Template History
Connection*Select your connection or create one.
MAP FIELDS [+ Add Field] add optional fields from a dynamic list : If not Found Consider as.
Template Name*Select the Template to get it history.
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 information about a specific template.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Get Template Info
Connection*Select your connection or create one.
MAP FIELDS [+ Add Field] add optional fields from a dynamic list : If not Found Consider as.
Template Name*Select the Template to get it info.
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

Return a list of all the templates available or of templates containing specific label.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*List Templates
Connection*Select your connection or create one.
Optional Field
LabelTo filter the listing with templates containing this label.

(*) required field

icon mailchimp 1 Mailchimp Transactional - Sub Accounts and Templates Publish Template Content Copy Link

Publish the content for the template. Any new messages sent using this template will start using the content that was previously in draft.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Publish Template Content
Connection*Select your connection or create one.
MAP FIELDS [+ Add Field] add optional fields from a dynamic list : If not Found Consider as.
Template Name*Select the Template to publish it content.
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

Inject content and optionally merge fields into a template, returning the HTML that results.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Render HTML Template
Connection*Select your connection or create one.
MAP FIELDS [+ Add Field] add optional fields from a dynamic list.
Template Name*Select the Template.
Template Content*Template content to render.
[+Element] add more template content.
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.
Merge VariablesOptional merge variables to use for injecting merge field content. If this is not provided, no merge fields will be replaced.
[+Element] add more element.
Name: the merge variable’s name. Merge variable names are case-insensitive and may not start with” _”.
Content: the merge variable’s content.

(*) required field

Update the code for an existing template. If null is provided for any fields, the values will remain unchanged.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Update Template
Connection*Select your connection or create one.
MAP FIELDS [+ Add Field] add optional fields from a dynamic list.
Template Name*Select the template to update from a dynamic list.
Optional Fields:
From EmailDefault sending address for emails sent using this template.
From NameDefault from name to be used.
SubjectDefault subject line to be used.
CodeThe HTML code for the template with mc:edit attributes for the editable elements.
For more details, see Mailchimp Template language, Create editable content.
TextDefault text part to be used when sending with this template.
PublishSet to false to add a draft template without publishing.
Labels[+Element] Add multiple Labels, maximum 10 for filtering templates.
Value: Label name

(*) required field


After setting up your Flow, you can choose to:

  • “Run once”, your Flow will run only a single time. You can use this function to test your Flow. Refer to how to set up an HTTP Trigger, in the “Create a Flow” step.
  • “Run Scheduler” will automate your Flows with the recurrence rule you previously defined.


For more details, refer to How to run a Flow tutorial in our Help Center.
 
If you are using a Webhook Trigger, the Flow will initiate automatically when a webhook is received from your connected apps. This means that the Flow is automated without a scheduler and will run until you deactivate the Flow manually. Refer to Webhook documentation in our Help Center.

Learn more about Wiresk, explore our user guide.

If you need an integration that you cannot find in Wiresk, you can make a request to our team, and we will try our best to satisfy your needs.