Wiresk

Wiresk

Mailchimp T. – Tags & Metadata

Estimated reading time: 6 min

What your automation will do…

You can include between 1 and 255 Methods to build complex Flows.
MAILCHIMP TRANSACTIONAL 2 Mailchimp T. - Tags & Metadata

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

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature (⚡ icon).

(*) required field

Name* List Tags
Connection* Select your connection or create one.

MAP FIELDS

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 Flow.

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

Sample response 
{
  "tag": "string",
  "reputation": 0,
  "sent": 0,
  "hard_bounces": 0,
  "soft_bounces": 0,
  "rejects": 0,
  "complaints": 0,
  "unsubs": 0,
  "opens": 0,
  "clicks": 0,
  "unique_opens": 0,
  "unique_clicks": 0
}
Expand

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature (⚡ icon).

(*) required field

Name* Get Tag
Connection* Select your connection or create one.

MAP FIELDS

Tag*

Select the tag name from a dynamic list.

Or Map it from Method “List Tags“.

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 Flow.

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

Sample response 
{
  "tag": "string",
  "sent": 0,
  "hard_bounces": 0,
  "soft_bounces": 0,
  "rejects": 0,
  "complaints": 0,
  "unsubs": 0,
  "opens": 0,
  "clicks": 0,
  "stats": {
    "today": {
      "sent": 0,
      "hard_bounces": 0,
      "soft_bounces": 0,
      "rejects": 0,
      "complaints": 0,
      "unsubs": 0,
      "opens": 0,
      "unique_opens": 0,
      "clicks": 0,
      "unique_clicks": 0
    },
    "last_7_days": {
      "sent": 0,
      "hard_bounces": 0,
      "soft_bounces": 0,
      "rejects": 0,
      "complaints": 0,
      "unsubs": 0,
      "opens": 0,
      "unique_opens": 0,
      "clicks": 0,
      "unique_clicks": 0
    },
    "last_30_days": {
      "sent": 0,
      "hard_bounces": 0,
      "soft_bounces": 0,
      "rejects": 0,
      "complaints": 0,
      "unsubs": 0,
      "opens": 0,
      "unique_opens": 0,
      "clicks": 0,
      "unique_clicks": 0
    },
    "last_60_days": {
      "sent": 0,
      "hard_bounces": 0,
      "soft_bounces": 0,
      "rejects": 0,
      "complaints": 0,
      "unsubs": 0,
      "opens": 0,
      "unique_opens": 0,
      "clicks": 0,
      "unique_clicks": 0
    },
    "last_90_days": {
      "sent": 0,
      "hard_bounces": 0,
      "soft_bounces": 0,
      "rejects": 0,
      "complaints": 0,
      "unsubs": 0,
      "opens": 0,
      "unique_opens": 0,
      "clicks": 0,
      "unique_clicks": 0
    }
  }
}
Expand

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature (⚡ icon).

(*) required field

Name* Get Tag History
Connection* Select your connection or create one.

MAP FIELDS

Tag*

Select the tag name from a dynamic list.

Or Map it from Method “List Tags“.

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 Flow.

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

Sample response 
[
  {
    "time": "2019-08-24T14:15:22Z",
    "sent": 0,
    "hard_bounces": 0,
    "soft_bounces": 0,
    "rejects": 0,
    "complaints": 0,
    "unsubs": 0,
    "opens": 0,
    "unique_opens": 0,
    "clicks": 0,
    "unique_clicks": 0
  }
]
Expand

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature (⚡ icon).

(*) required field

Name* List All Tags History
Connection* Select your connection or create one.

MAP FIELDS

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 Flow.

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

Sample response 
[
  {
    "time": "2019-08-24T14:15:22Z",
    "sent": 0,
    "hard_bounces": 0,
    "soft_bounces": 0,
    "rejects": 0,
    "complaints": 0,
    "unsubs": 0,
    "opens": 0,
    "unique_opens": 0,
    "clicks": 0,
    "unique_clicks": 0
  }
]
Expand

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature (⚡ icon).

(*) required field

Name* Delete a Tag
Connection* Select your connection or create one.

MAP FIELDS

Tag*

Select the tag name to be deleted.

Or Map it from Method “List Tags“.

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 Flow.

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

Sample response 
{
  "tag": "string",
  "reputation": 0,
  "sent": 0,
  "hard_bounces": 0,
  "soft_bounces": 0,
  "rejects": 0,
  "complaints": 0,
  "unsubs": 0,
  "opens": 0,
  "clicks": 0,
  "unique_opens": 0,
  "unique_clicks": 0
}
Expand
MAILCHIMP TRANSACTIONAL 2 Mailchimp T. - Tags & Metadata

Manage your custom metadata fields in your account.

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature (⚡ icon).

(*) required field

Name* List Metadata Fields
Connection* Select your connection or create one.

MAP FIELDS

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 Flow.

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

Sample response 
{
  "name": "string",
  "state": "active",
  "view_template": "string"
}
Expand

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature (⚡ icon).

(*) required field

Name* Create Metadata Field
Connection* Select your connection or create one.

MAP FIELDS

Name*

Give a unique identifier for the metadata field.

View Template

Mustache template to control how the metadata is rendered in your activity log.

Sample response 
{
  "name": "string",
  "state": "active",
  "view_template": "string"
}
Expand

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature (⚡ icon).

(*) required field

Name* Update Metadata Field
Connection* Select your connection or create one.

MAP FIELDS

Name*

Select the Metadata field to be updated.

Or Map it from Method “List Metadata fields“.

View Template

Mustache template to control how the metadata is rendered in your activity log.

Sample response 
{
  "name": "string",
  "state": "active",
  "view_template": "string"
}
Expand

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature (⚡ icon).

(*) required field

Name* Delete Metadata Field
Connection* Select your connection or create one.

MAP FIELDS

Name*

Select the Metadata field to be deleted.

Or Map it from Method “List Metadata fields“.

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 Flow.

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

Sample response 
{
  "name": "string",
  "state": "active",
  "view_template": "string"
}
Expand

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.