Get Sent Messages

iterable.get_sent_messages
ActionEmailconnection required

Calls the Iterable API with the connection's credentials.

List the messages Iterable has sent to one user.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Iterable
Secret shape
the API key, or {"api_key": "…"}
Config it needs
region, base_url
Resolved by
config.connection_id, else node.connection_id

Configuration

8 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
email
The email address that identifies the user. Provide this or 'user_id'.
stringNo—email format—
user_id
The userId that identifies the user. Provide this or 'email'.
stringNo———
limit
How many messages to return. Iterable defaults to 10 and caps this at 1000.
integerNo101–1000—
campaign_ids
Only messages from these campaign ids, as a JSON array of numbers.
arrayNo—array of integer—
start_date_time
Earliest send time, formatted 'yyyy-MM-dd HH:mm:ss ZZ'.
stringNo———
end_date_time
Latest send time, formatted 'yyyy-MM-dd HH:mm:ss ZZ'.
stringNo———
exclude_blast_campaigns
Leave out messages sent by blast campaigns.
booleanNo———
message_medium
Only messages of this medium.
stringNo—one of "Email", "Push", "InApp", "SMS"—
  • At least one of email, user_id must be set.

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "limit": 10
}

Output

One shape.

result

FieldTypeExample
messages
The messages Iterable sent, newest first.
array—
count
How many messages were returned.
number—
{
  "count": 0,
  "messages": []
}

See Get Sent Messages run in a workflow.

In a technical demo we add the Iterable connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.