Mailchimp TransactionalSearch messages
BetaReads data
Finds sent messages by address, date, tag or sender.
Settings
| Setting | What it is |
|---|---|
| ConnectionRequired | The Mailchimp Transactional connection the step signs in with. |
| Search | Mailchimp's own search syntax — an address on its own works, and so does email:jane@example.com or subject:invoice. |
| From date | text |
| To date | text |
| Tags | Comma-separated. Only messages carrying one of these tags are returned. |
| Senders | Comma-separated from-addresses. Only messages sent from one of these count. |
| Messages at most | 1 to 1000. Mailchimp has no paging at all, so a search that finds more is cut off here without saying so — narrow the dates or the query instead of raising this. |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `mailchimp-transactional`) |
query | text |
dateFrom | text |
dateTo | text |
tags | text |
senders | text |
limit | number, by default 100 |
Output
| Field | Type |
|---|---|
messages | array |
messageCountMessages in this answer | number |
Sample output, and the expression for each field
- messageCount0
- messages[]
Errors
When a step of this node stops a run, the run page shows a code. Look it up:
Example step
The step as a flow file holds it. Replace each value in <…>.
{
"config": {
"connection": "<connection id>",
"dateFrom": "",
"dateTo": "",
"limit": 100,
"query": "",
"senders": "",
"tags": ""
},
"label": "Search messages",
"type": "mandrill.searchMessages",
"version": 1
}