Wiresk

Wiresk

Mailchimp – Segment, Event, Member & Report

Estimated reading time: 9 min

What your automation will do…

You can include between 1 and 255 Methods to build complex Flows.
MAILCHIMP TRANSACTIONAL Mailchimp - Segment, Event, Member & Report

Manage segments for a specific Mailchimp list. A segment is a section of your list that includes only those subscribers who share specific common field information.

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* Add Segment
Connection* Select your connection or create one.
MAP FIELDS + Add Field ↓
Additional fields to configure the Method.

Use Archive Bar

Whether campaigns for this list use the Archive Bar in archives by default.

Notify On Subscribe

The email address to send subscribe notifications to.

Notify On Unsubscribe

The email address to send unsubscribe notifications to.

Double Optin

Whether or not to require the subscriber to confirm subscription via email.

Marketing Permissions

Whether or not the list has marketing permissions (eg. GDPR) enabled.

Audience/List ID*

Select your audience from a list.

Or Map the ID from Trigger “Search Audience/List“.

Name*

Name of the segment.

Option

⚠️ You must provide either an “options” field or a “static segment” field, not both.

Match

Match type. Possible values: "any" or "all".

Conditions

The conditions of the segment. Static Segments don’t have conditions.

+Element +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first condition.

Condition Type*: The type of condition to apply. There are multiple possible types, see the condition types documentation.

Field*: The value of field depends on the condition type.
Operator*: The type of operator depends on the condition type.

Value*: The value depends on the condition type.

Extra: optional extra information.

Static Segment

An array of emails to be used for a static segment. Any emails provided that are not present on the list will be ignored.

⚠️ You must provide either an “options” field or a “static segment” field, not both.

+Element +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first email.

Email*

Sample response 
{}
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* Add Subscriber to Static Segment
Connection* Select your connection or create one.
MAP FIELDS + Add Field ↓
Additional fields to configure the Method.

Use Archive Bar

Whether campaigns for this list use the Archive Bar in archives by default.

Notify On Subscribe

The email address to send subscribe notifications to.

Notify On Unsubscribe

The email address to send unsubscribe notifications to.

Double Optin

Whether or not to require the subscriber to confirm subscription via email.

Marketing Permissions

Whether or not the list has marketing permissions (eg. GDPR) enabled.

Audience/List ID*

Select your audience from a list.

Or Map the ID from Trigger “Search Audience/List“.

Segment ID*

Select the Segment from a dynamic list.

Or Map the ID from Trigger or step responses.

Email*

Email address of a Member/Contact/subscriber from your Mailchimp List.

Sample response 
{
  "id": "string",
  "email_address": "string",
  "full_name": "string",
  "unique_email_id": "string",
  "email_type": "string",
  "status": "subscribed",
  "merge_fields": {
    "property1": null,
    "property2": null
  },
  "interests": {
    "property1": true,
    "property2": true
  },
  "stats": {
    "avg_open_rate": 0,
    "avg_click_rate": 0
  },
  "ip_signup": "string",
  "timestamp_signup": "2019-08-24T14:15:22Z",
  "ip_opt": "string",
  "timestamp_opt": "2019-08-24T14:15:22Z",
  "member_rating": 0,
  "last_changed": "2019-08-24T14:15:22Z",
  "language": "string",
  "vip": true,
  "email_client": "string",
  "location": {
    "latitude": 0,
    "longitude": 0,
    "gmtoff": 0,
    "dstoff": 0,
    "country_code": "string",
    "timezone": "string"
  },
  "last_note": {
    "note_id": 0,
    "created_at": "2019-08-24T14:15:22Z",
    "created_by": "string",
    "note": "string"
  },
  "list_id": "string",
  "_links": [
    {
      "rel": "string",
      "href": "string",
      "method": "GET",
      "targetSchema": "string",
      "schema": "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 Segment
Connection* Select your connection or create one.

MATCHING CRITERIA

Audience/List ID*

Select your audience from a list.

Or Map the ID from Trigger “Search Audience/List“.

Segment ID*

Select the Segment from a dynamic list.

Or Map the ID from Trigger or step responses.

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 
{}
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 Segment
Connection* Select your connection or create one.

MATCHING CRITERIA

Audience/List ID*

Select your audience from a list.

Or Map the ID from Trigger “Search Audience/List“.

Segment ID*

Select the Segment from a dynamic list.

Or Map the ID from Trigger or step responses.

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 
{
  "id": 0,
  "name": "string",
  "member_count": 0,
  "type": "saved",
  "created_at": "2019-08-24T14:15:22Z",
  "updated_at": "2019-08-24T14:15:22Z",
  "options": {
    "match": "any",
    "conditions": [
      null
    ]
  },
  "list_id": "string",
  "_links": [
    {
      "rel": "string",
      "href": "string",
      "method": "GET",
      "targetSchema": "string",
      "schema": "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* Remove List Member From Static Segment
Connection* Select your connection or create one.

MAP FIELDS

Audience/List ID*

Select your audience from a list.

Or Map the ID from Trigger “Search Audience/List“.

Segment ID*

Select the Segment from a dynamic list.

Or Map the ID from Trigger or step responses.

Subscriber Email*

Email address of the Member/Contact/Subscriber.

Sample response 
{}
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 Segment
Connection* Select your connection or create one.

MATCHING CRITERIA

Audience/List ID*

Select your audience from a list.

Or Map the ID from Trigger “Search Audience/List“.

Segment ID*

Select the Segment from a dynamic list.

Or Map the ID from Trigger or step responses.

MAP FIELDS

Name*

Name of the segment.

Option

⚠️ You must provide either an “options” field or a “static segment” field, not both.

Match

Match type. Possible values: "any" or "all".

Conditions

The conditions of the segment. Static Segments don’t have conditions.

+Element +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first condition.

Condition Type*: The type of condition to apply. There are multiple possible types, see the condition types documentation.

Field*: The value of field depends on the condition type.
Operator*: The type of operator depends on the condition type.

Value*: The value depends on the condition type.

Extra: optional extra information.

Static Segment

An array of emails to be used for a static segment. Any emails provided that are not present on the list will be ignored.

⚠️ You must provide either an “options” field or a “static segment” field, not both.

+Element +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first email.

Email*

Sample response 
{
  "id": 0,
  "name": "string",
  "member_count": 0,
  "type": "saved",
  "created_at": "2019-08-24T14:15:22Z",
  "updated_at": "2019-08-24T14:15:22Z",
  "options": {
    "match": "any",
    "conditions": [
      null
    ]
  },
  "list_id": "string",
  "_links": [
    {
      "rel": "string",
      "href": "string",
      "method": "GET",
      "targetSchema": "string",
      "schema": "string"
    }
  ]
}
Expand
MAILCHIMP TRANSACTIONAL Mailchimp - Segment, Event, Member & Report

Use the Events endpoint to collect website or in-app actions and trigger targeted automations.

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* Add Event
Connection* Select your connection or create one.
MAP FIELDS + Add Field ↓
Additional fields to configure the Method.

Properties

An optional list of properties (custom fields):

+Element +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first email.

Key*: custom field name.

Value*: value of the custom field.

Is Syncing*

Events created with the is_syncing value set to true will not trigger automations.

Occurred at*

The date and time the event occurred in ISO 8601 format.

Audience/List ID*

Select your audience from a list.

Or Map the ID from Trigger “Search Audience/List“.

Subscriber Email Or ID*

Email address of the Member/Contact/Subscriber.

Name*

The name for this type of event (‘purchased’, ‘visited’, etc). Must be 2-30 characters in length. Event name must only contain letters, numbers, underscores, and dashes.

Sample response 
{}
Expand
MAILCHIMP TRANSACTIONAL Mailchimp - Segment, Event, Member & Report

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* Upsert Member Tags
Connection* Select your connection or create one.
MAP FIELDS + Add Field ↓
Additional fields to configure the Method.

Is Syncing*

Events created with the is_syncing value set to true will not trigger automations.

Audience/List ID*

Select your audience from a list.

Or Map the ID from Trigger “Search Audience/List“.

Subscriber Email Or ID*

Email address of the Member/Contact/Subscriber.

Tags*

A list of tags assigned to the list member.

+Element +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first tag.

Name*: Tag name

Status*: The status for the tag on the member, pass in active to add a tag or inactive to remove it. Possible values: "inactive" or "active".

Sample response 
{}
Expand
MAILCHIMP TRANSACTIONAL Mailchimp - Segment, Event, Member & Report

Get detailed information about links clicked in campaigns.

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 Click Report
Connection* Select your connection or create one.

MATCHING CRITERIA

Campaign ID*

Specify the Campaign ID.

Or Map the Campaign ID form a step response like “List Campaigns”.

Link ID*

The id for the link.

To view click data for a specific link, choose that link from your Campaign.

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 
{
  "id": 0,
  "name": "string",
  "member_count": 0,
  "type": "saved",
  "created_at": "2019-08-24T14:15:22Z",
  "updated_at": "2019-08-24T14:15:22Z",
  "options": {
    "match": "any",
    "conditions": [
      null
    ]
  },
  "list_id": "string",
  "_links": [
    {
      "rel": "string",
      "href": "string",
      "method": "GET",
      "targetSchema": "string",
      "schema": "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.