Short answer: Drop the "Twilio → List Messages" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
To Phone Number To | string | Optional | Filter by recipient phone number in E.164 format |
From Phone Number From | string | Optional | Filter by sender phone number in E.164 format |
Page Size PageSize | string | Optional | Number of messages to return (max 1000) |
Date Sent DateSent | string | Optional | Filter messages sent on this date (YYYY-MM-DD format) |
{"To": "+15551234567","From": "+15559876543","PageSize": "50","DateSent": "e.g. 2025-01-15"}
{"page": 0,"messages": [{"to": "+15551234567","sid": "SM1234567890abcdef","body": "Hello!","from": "+15559876543","status": "delivered","date_sent": "2025-01-15T12:00:00Z"}],"page_size": 50}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.