Wiresk

Wiresk

Mailchimp T. – Tags & Metadata

Estimated reading time: 3 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.
MAILCHIMP TRANSACTIONAL 2 Mailchimp T. - Tags & Metadata

List, delete, or get information on your Tags and their sending statistics.

Deletes a tag permanently. Deleting a tag removes the tag from any messages that have been sent, and also deletes the tag’s stats. There is no way to undo this operation, so use it carefully.

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 Tag
Connection*Select your connection or create one.
MAP FIELDS [+ Add Field] add optional fields from a dynamic list : If not Found Consider as.
Tag*Select the Tag to delete.
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 more detailed information about a single tag, 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 Tag
Connection*Select your connection or create one.
MAP FIELDS [+ Add Field] add optional fields from a dynamic list : If not Found Consider as.
Tag*Select the Tag to get info from.
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 the recent history (hourly stats for the last 30 days) for a tag.

Configuration Table:

Input Options:

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

Return the recent history (hourly stats for the last 30 days) for all tags.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*List All Tags History
Connection*Select your connection or create one.
MAP FIELDS [+ Add Field] add optional fields from a dynamic list : If not Found Consider as.
If not Found Consider asSuccess – 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 all of the user-defined tag information.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*List Tags
Connection*Select your connection or create one.
If not Found Consider asSuccess – 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

MAILCHIMP TRANSACTIONAL 2 Mailchimp T. - Tags & Metadata
Add a new custom metadata field to be indexed for the account.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Create Metadata Field
Connection*Select your connection or create one.
MAP FIELDS [+ Add Field] add optional fields from a dynamic list.
Name*Give a unique identifier for the metadata field.
View TemplateMustache template to control how the metadata is rendered in your activity log.

(*) required field

Delete an existing custom metadata field. Deletion isn’t instantaneous, and /metadata/list will continue to return the field until the asynchronous deletion process is complete.

Configuration Table:

Input Options:

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

(*) required field

Get the list of custom metadata fields indexed for the 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 Metadata Fields
Connection*Select your connection or create one.

(*) required field

Update an existing custom metadata field.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Update Metadata Field
Connection*Select your connection or create one.
MAP FIELDS [+ Add Field] add optional fields from a dynamic list.
Metadata Name*Select the metadata field to update.
View TemplateMustache template to control how the metadata is rendered in your activity log.

(*) 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.