Lookup Phone Number: Twilio action

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
Phone Number phone_number	string	Required	E.164 format
Lookup Type fields	options	Optional	Lookup Type. Options: Line Type (mobile/landline/VoIP), Caller Name (CNAM), Validation

Sample request

{
  "phone_number": "+15551234567",
  "fields": "{{trigger.fields}}"
}

Returns

{
  "valid": true,
  "country_code": "US",
  "phone_number": "+15551234567",
  "national_format": "(555) 123-4567",
  "calling_country_code": "1",
  "line_type_intelligence": {
    "type": "mobile",
    "carrier_name": "T-Mobile"
  }
}

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

FAQ

Questions about Lookup Phone Number.

What does the Lookup Phone Number action do in Twilio?

Looks up information about a phone number via Twilio Lookup: country, carrier, line type (mobile/landline/voip), and validity. Use to filter signups, fraud-score, or pre-validate before sending SMS.

What inputs does Lookup Phone Number require?

Required: Phone Number. Every input accepts a static value or a variable from any upstream node in your workflow.

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 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 Lookup Phone Number support batch operations?

Yes. Run Lookup Phone Number inside a Loop node to process arrays. Tiny Command handles Twilio's rate limits automatically so you don't have to throttle manually.

More actions