Wiresk

Wiresk

Mailchimp T. – Messages & Senders

Estimated reading time: 20 min

What your automation will do…

You can include between 1 and 255 Methods to build complex Flows.
MAILCHIMP TRANSACTIONAL 2 Mailchimp T. - Messages & Senders
Email scheduling is only available with Mailchimp Essentials plan or higher.

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* Cancel Scheduled Email
Connection* Select your connection or create one.

MAP FIELDS

Scheduled Email ID*

Select the specific scheduled email from a dynamic list.

Or Map it ID from Method “List Scheduled Emails“.

Sample response 
[
  {
    "_id": "string",
    "created_at": "2019-08-24T14:15:22Z",
    "send_at": "2019-08-24T14:15:22Z",
    "from_email": "user@example.com",
    "to": "user@example.com",
    "subject": "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* Get a Message
Connection* Select your connection or create one.

MAP FIELDS

Message ID*

Select your recent message from a dynamic list.

Or Map it ID from input or step response.

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": "string",
    "created_at": "2019-08-24T14:15:22Z",
    "send_at": "2019-08-24T14:15:22Z",
    "from_email": "user@example.com",
    "to": "user@example.com",
    "subject": "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* List Scheduled Emails
Connection* Select your connection or create one.

MAP FIELDS

To

Optional recipient address to filter results to.

Sample response 
[
  {
    "_id": "string",
    "created_at": "2019-08-24T14:15:22Z",
    "send_at": "2019-08-24T14:15:22Z",
    "from_email": "user@example.com",
    "to": "user@example.com",
    "subject": "string"
  }
]
Expand

Get a Message Content Copy Link

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 a Message Content
Connection* Select your connection or create one.

MAP FIELDS

Message ID*

Select your recent message from a dynamic list.

Or Map it ID from input or step response.

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 
{
  "ts": 0,
  "_id": "string",
  "from_email": "user@example.com",
  "from_name": "string",
  "subject": "string",
  "to": {
    "email": "user@example.com",
    "name": "string"
  },
  "tags": [
    "string"
  ],
  "headers": {},
  "text": "string",
  "html": "string",
  "attachments": [
    {
      "name": "string",
      "type": "string",
      "content": "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* Reschedule Email
Connection* Select your connection or create one.

MAP FIELDS

Scheduled Email ID*

Select the specific scheduled email from a dynamic list.

Or Map it ID from Method “List Scheduled Emails“.

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.

Sample response 
[
  {
    "_id": "string",
    "created_at": "2019-08-24T14:15:22Z",
    "send_at": "2019-08-24T14:15:22Z",
    "from_email": "user@example.com",
    "to": "user@example.com",
    "subject": "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* Search Message by Date
Connection* Select your connection or create one.
MAP FIELDS + Add Field ↓
Additional fields to configure the Method.

Tags

Tag names to narrow the search to, will return messages that contain ANY of the tags.

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

Element 1: Represents the first tag.

Value*: Tag name

Senders

Sender addresses to narrow the search to, will return messages sent by ANY of the senders.

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

Element 1: Represents the first email.

Email*: sender address

API Keys

API keys to narrow the search to, will return messages sent by ANY of the keys.

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

Element 1: Represents the first key.

Key*: API Key

Query

This field allows you to search for messages using specific keywords or phrases.

Start Date

Set the beginning date of the search range.

End Date

Set the end date of the search range.

Limit

The maximum number of results to return, defaults is 100, 1000 is the maximum.

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 
[
  {
    "ts": 0,
    "_id": "string",
    "sender": "user@example.com",
    "template": "string",
    "subject": "string",
    "email": "user@example.com",
    "tags": [
      "string"
    ],
    "opens": 0,
    "opens_detail": [
      {
        "ts": 0,
        "ip": "string",
        "location": "string",
        "ua": "string"
      }
    ],
    "clicks": 0,
    "clicks_detail": [
      {
        "ts": 0,
        "url": "string",
        "ip": "string",
        "location": "string",
        "ua": "string"
      }
    ],
    "state": "sent",
    "metadata": {}
  }
]
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* Search Message by Hour
Connection* Select your connection or create one.
MAP FIELDS + Add Field ↓
Additional fields to configure the Method.

Tags

Tag names to narrow the search to, will return messages that contain ANY of the tags.

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

Element 1: Represents the first tag.

Value*: Tag name

Senders

Sender addresses to narrow the search to, will return messages sent by ANY of the senders.

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

Element 1: Represents the first email.

Email*: sender address

Query

This field allows you to search for messages using specific keywords or phrases.

Start Date

Set the beginning date of the search range.

End Date

Set the end date of the search range.

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

Async

Enable 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 Pool

The 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 at

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

Message*

the information on the message to send.

From Email*

The sender email address.

From Name*

From name to be used.

Subject*

The message subject.

Body HTML

The full HTML content to be sent.

Body Text

Optional full text content to be sent.

To

Recipient information

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

Element 1: Represents the first recipient.

Email*: the email address of the recipient.

Name: the optional display name to use for the recipient.

Type: choices: To, CC, BCC

+ Add Field ↓
Additional fields to configure Message.

Headers: optional extra headers to add to the message (most headers are allowed)

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

Element 1: Represents the first Header.

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 +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first global merge variable.

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 +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first merge variable.

Recipient*: the email address of the recipient that the merge variables should apply to.

Variables*: the recipient’s merge variables

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

Element 1: Represents the first variable.

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 +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first tag.

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 +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first URL.

Value*: URL

Google Analytics Campaign: 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 +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first recipient metadata.

Recipient*: the email address of the recipient that the metadata is associated with.

Values.User ID*: 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 +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first attachment.

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 +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first image.

MIME Type*: the MIME type of the image – must start with “image/”
Name*: the Content ID of the image – use cid:THIS VALUE Mailchimp T. - Messages & Senders to reference the image in your HTML content.
Content*: (Base64 Encoded), see more details in Base64 Encoding documentation.

Sample response 
[
  {
    "email": "user@example.com",
    "status": "sent",
    "reject_reason": "hard-bounce",
    "queued_reason": "attachments",
    "_id": "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* Send Message Template
Connection* Select your connection or create one.
MAP FIELDS + Add Field ↓
Additional fields to configure the Method.

Async

Enable 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 Pool

The 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 at

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

Template Name*

Select the template to send from a dynamic list.

Message*

the information on the message to send.

From Email*

The sender email address.

From Name*

From name to be used.

Subject*

The message subject.

Body HTML

The full HTML content to be sent.

Body Text

Optional full text content to be sent.

To*

Recipient information

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

Element 1: Represents the first recipient.

Email*: the email address of the recipient.

Name: the optional display name to use for the recipient.

Type: choices: To, CC, BCC

+ Add Field ↓
Additional fields to configure Message.

Headers: optional extra headers to add to the message (most headers are allowed)

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

Element 1: Represents the first Header.

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 +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first global merge variable.

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 +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first merge variable.

Recipient*: the email address of the recipient that the merge variables should apply to.

Variables*: the recipient’s merge variables

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

Element 1: Represents the first variable.

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 +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first tag.

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 +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first URL.

Value*: URL

Google Analytics Campaign: 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 +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first recipient metadata.

Recipient*: the email address of the recipient that the metadata is associated with.

Values.User ID*: 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 +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first attachment.

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 +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first image.

MIME Type*: the MIME type of the image – must start with “image/”
Name*: the Content ID of the image – use cid:THIS VALUE Mailchimp T. - Messages & Senders to reference the image in your HTML content.
Content*: (Base64 Encoded), see more details in Base64 Encoding documentation.

Template Content

Template content to send. For more details, see Mailchimp Template language, Create editable content.

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

Element 1: Represents the first template content.

Name*: the name of the mc:edit editable region to inject into
Content*: the content to inject

Sample response 
[
  {
    "email": "user@example.com",
    "status": "sent",
    "reject_reason": "hard-bounce",
    "queued_reason": "attachments",
    "_id": "string"
  }
]
Expand
MAILCHIMP TRANSACTIONAL 2 Mailchimp T. - Messages & Senders

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 a Sender Domain
Connection* Select your connection or create one.

MAP FIELDS

Domain*

Provide the domain name

Sample response 
{
  "domain": "string",
  "created_at": "2019-08-24T14:15:22Z",
  "last_tested_at": "2019-08-24T14:15:22Z",
  "spf": {
    "valid": true,
    "valid_after": "2019-08-24T14:15:22Z",
    "error": "string"
  },
  "dkim": {
    "valid": true,
    "valid_after": "2019-08-24T14:15:22Z",
    "error": "string"
  },
  "verified_at": "2019-08-24T14:15:22Z",
  "valid_signing": true,
  "verify_txt_key": "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* Check Domain Setting
Connection* Select your connection or create one.

MAP FIELDS

Domain*

Provide the domain name

Sample response 
{
  "domain": "string",
  "created_at": "2019-08-24T14:15:22Z",
  "last_tested_at": "2019-08-24T14:15:22Z",
  "spf": {
    "valid": true,
    "valid_after": "2019-08-24T14:15:22Z",
    "error": "string"
  },
  "dkim": {
    "valid": true,
    "valid_after": "2019-08-24T14:15:22Z",
    "error": "string"
  },
  "dkim2": {
    "valid": true,
    "valid_after": "2019-08-24T14:15:22Z",
    "error": "string"
  },
  "dmarc": {
    "valid": true,
    "error": "string"
  },
  "verified_at": "2019-08-24T14:15:22Z",
  "valid_signing": true,
  "verify_txt_key": "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* Get Sender Info
Connection* Select your connection or create one.

MAP FIELDS

Email Address*

Enter the sender’s email address to retrieve their information.

Sample response 
{
  "address": "user@example.com",
  "created_at": "2019-08-24T14:15:22Z",
  "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* List Account Senders
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 
[
  {
    "address": "user@example.com",
    "created_at": "2019-08-24T14:15:22Z",
    "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* List Sender Domains
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 
[
  {
    "domain": "string",
    "created_at": "2019-08-24T14:15:22Z",
    "last_tested_at": "2019-08-24T14:15:22Z",
    "spf": {
      "valid": true,
      "valid_after": "2019-08-24T14:15:22Z",
      "error": "string"
    },
    "dkim": {
      "valid": true,
      "valid_after": "2019-08-24T14:15:22Z",
      "error": "string"
    },
    "dkim2": {
      "valid": true,
      "valid_after": "2019-08-24T14:15:22Z",
      "error": "string"
    },
    "dmarc": {
      "valid": true,
      "error": "string"
    },
    "verified_at": "2019-08-24T14:15:22Z",
    "valid_signing": true,
    "verify_txt_key": "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* Verify Domain
Connection* Select your connection or create one.

MAP FIELDS

Domain*

Domain name at which you can receive email.

Mailbox*

A mailbox at the domain where the verification email should be sent.

Sample response 
{
  "status": "string",
  "domain": "string",
  "email": "user@example.com"
}
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* View Sender History
Connection* Select your connection or create one.

MAP FIELDS

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 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,
    "opens": 0,
    "unique_opens": 0,
    "clicks": 0,
    "unique_clicks": 0
  }
]
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.