ActionTextLinkUpdated May 2026

How do I list SMS messages sent via TextLink?

Short answer: Drop the "TextLink → List Sent Messages" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 3 TextLink actions

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
Page page	string	Optional	Page number for pagination

Sample request

{
  "page": "1"
}

Returns

{
  "ok": true,
  "data": [
    {
      "cost": 0.01,
      "text": "Hello, this is a test message",
      "status": "delivered",
      "sent_at": "2025-03-15T10:00:00Z",
      "message_id": "msg_abc123",
      "phone_number": "+1234567890"
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for List Sent Messages.

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

Google Sheets → TextLink

2 Google Sheets triggers

HubSpot → TextLink

18 HubSpot triggers

FAQ

Questions about List Sent Messages.

What does the List Sent Messages action do in TextLink?

Lists SMS messages previously sent through TextLink with their status and timestamps. Use it for audit, reconciliation, or building a sends report.

What inputs does List Sent Messages require?

List Sent 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 TextLink returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Sent Messages support batch operations?

Yes. Run List Sent Messages inside a Loop node to process arrays. Tiny Command handles TextLink's rate limits automatically so you don't have to throttle manually.

More actions