Nexra
All connectors
Implemented
Messaging, collaboration & support
Twilio logo

Twilio

Send SMS and WhatsApp messages, track message status, and read call logs, recording metadata and phone numbers.

Monitor message history and delivery status across customer communications.

Build a flow with TwilioProvider API documentation

Source actions

6

Destination actions

1

Data types

4

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

calls
  • Get call
    Source

    One call with status, duration and price.

  • List calls
    Source
    Incremental

    Call log, newest first, optionally filtered by number, status or start date.

messages
  • Get message
    Source

    Current status, segments, price and error details for one message.

  • List Messages
    Source

    List operation for Messages.

  • Send message
    Destination
    Not retried automatically

    Sends an SMS, MMS or WhatsApp message from a Messaging Service or sender, with text, media or an approved content template.

phone numbers
  • List phone numbers
    Source

    Phone numbers on the account with capabilities and webhook configuration.

recordings
  • List recordings
    Source
    Incremental

    Recording metadata, optionally for one call or created on or after a date.

Authentication

API key SID and secret with account SID

Plans and access

Any Twilio account; trial accounts can only message verified numbers. Senders must be registered for the destination (A2P 10DLC, toll-free verification, WhatsApp sender approval).

Test environment

Trial accounts and the WhatsApp Sandbox can be used; test credentials do not support listing resources.

Rate limits

Account-level concurrency limit; HTTP 429 with error 20429. Message queues send at sender throughput (MPS).

Provider events

StatusCallback for message and call status; incoming message webhooks per number. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

  • Sending SMS or WhatsApp messages must be explicitly enabled on the connection and runs only in an approved flow. Twilio has no idempotency key, so a send with an uncertain outcome is never repeated automatically; check the Twilio message log before retrying. Credential-backed validation remains pending.
  • Sending is high risk and billable: Twilio has no idempotency key for message creation, so an uncertain send is never repeated automatically.
  • A queued or sent status is not delivery; read the message later for delivered, undelivered or failed.
  • Conversations (conversations.twilio.com) and Lookup (lookups.twilio.com) are on separate hosts and are not implemented.
  • Recording media and message media files are not downloaded; only metadata is read.