ActionTwilioUpdated September 2026

How do I list Twilio messages?

Short answer: You can list messages in Twilio by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Twilio List Messages action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Messages in Twilio — start free All 7 Twilio actions

List Messages in Twilio — start free

Inputs

The fields this action accepts.

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)

Sample request

{
  "To": "+15551234567",
  "From": "+15559876543",
  "PageSize": "50",
  "DateSent": "e.g. 2025-01-15"
}

Returns

{
  "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.

Triggered by

Apps that pair well as the trigger for List Messages.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Twilio

2 Google Sheets triggers

HubSpot → Twilio

18 HubSpot triggers

FAQ

Questions about List Messages.

What does the List Messages action do in Twilio?

Retrieves a list of sent and received messages on your Twilio account, with filters for to, from, status, and date sent. Used for audit and reporting.

What inputs does List Messages require?

List Messages has no required inputs. Sensible defaults are applied if you leave fields blank.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Twilio returns an error?

The run history shows the failed step with its input and the error message Twilio returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does List Messages support batch operations?

Run List Messages inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Twilio's rate limits.

More actions