Twilio

Adding the Data Source

1) Log in to your Twilio account with a user that has administrator permissions;

2) On the left side menu, click on Dashboard > Settings > General;

3) Look for the “API Credentials” > “LIVE Credentials” section and copy the “Account SID” and “Auth Token” values;

4) On the Kondado platform, go to the add new sources page and select the Twilio data source;

5) In “Name” give a name for your data source and in “Account SID” and “Auth Token” copy the values obtained in step (3);

Now just click on SAVE and start creating pipelines to replicate data from Twilio to your Data Warehouse or Data Lake.

Pipelines

Relationship chart

Messages

FieldType 
sidtext[en] The unique string that that we created to identify the Message resource.
account_sidtext[en] The SID of the Account that sent the message that created the resource.
bodytext[en] (Available for up to 30 DAYS) The message text. Can be up to 1,600 characters long.
date_createdtimestamp[en] The date and time in GMT that the resource was created
date_senttimestamp[en] The date and time in GMT that the resource was sent. For outgoing messages, this is when we sent the message. For incoming messages, this is when we made the HTTP request to your application.
date_updatedtimestamp[en] The date and time in GMT that the resource was last updated
directiontext[en] The direction of the message. Can be: inbound for incoming messages, outbound-api for messages initiated by a REST API, outbound-call for messages initiated during a call, or outbound-reply for messages initiated in response to an incoming message.
error_codetext[en] The error code returned if your message status is failed or undelivered . The error_code provides more information about the failure. If the message was successful, this value is null.
error_messagetext[en] The description of the error_code if your message status is failed or undelivered . If the message was successful, this value is null.
fromtext[en] (Available for up to 120 DAYS) The phone number (in E.164 format), alphanumeric sender ID , or Wireless SIM that initiated the message. For incoming messages, this will be the number of the sending phone. For outgoing messages, this value will be one of your Twilio phone numbers or the alphanumeric sender ID used.
messaging_service_sidtext[en] The SID of the Messaging Service used with the message. The value is null if a Messaging Service was not used.
num_mediafloat[en] The number of media files associated with the message. A message can send up to 10 media files.
num_segmentsfloat[en] The number of segments that make up the complete message. A message body that is too large to be sent in a single SMS message is segmented and charged as multiple messages. Inbound messages over 160 characters are reassembled when the message is received. Note: When using a Messaging Service to send messages, num_segments will always be 0 in Twilio’s response to your API request.
pricefloat[en] The amount billed for the message, in the currency specified by price_unit . Note that your account is charged for each segment we send to the handset. Populated after the message has been sent. May not be immediately available.
price_unittext[en] The currency in which price is measured, in ISO 4127 format (e.g. usd , eur , jpy ).
statustext[en] The status of the message. Can be: accepted , scheduled (Pilot only), queued , sending , sent , failed , delivered , undelivered , receiving , received , or read (WhatsApp only). For more information, See https://www.twilio.com/docs/sms/api/message-resource#message-status-values
totext[en] (Available for up to 120 DAYS) The phone number in E.164 format that received the message. For incoming messages, this will be one of your Twilio phone numbers. For outgoing messages, this will be the sending phone.

Add Twilio as a Data Source on Kondado

Connect your Twilio account to Kondado by extracting API credentials and configuring the source for pipeline creation.

1
Log in to Twilio with admin permissions

Access your Twilio account using a user that has administrator permissions to ensure you can view API credentials.

2
Navigate to API Credentials in Settings

On the left side menu, go to Dashboard > Settings > General and locate the "API Credentials" > "LIVE Credentials" section.

3
Copy Account SID and Auth Token

Copy the "Account SID" and "Auth Token" values from the LIVE Credentials section—these are required for authentication on Kondado.

4
Add Twilio source on Kondado platform

On the Kondado platform, go to the add new sources page and select the Twilio data source connector.

5
Configure and save the data source

Enter a name for your data source, paste the Account SID and Auth Token values, then click SAVE.

6
Create pipelines to your destination

Start building data pipelines to replicate Twilio data to your Data Warehouse, Data Lake, or other destinations.

Frequently asked questions

What Twilio permissions do I need to connect to Kondado?
You need to log in to Twilio with a user that has administrator permissions. This ensures you can access the API Credentials section under Dashboard > Settings > General.
Where do I find my Twilio Account SID and Auth Token?
In your Twilio account, navigate to Dashboard > Settings > General and look for the "API Credentials" > "LIVE Credentials" section. Copy both the "Account SID" and "Auth Token" values.
What Twilio data can I replicate through Kondado pipelines?
You can replicate Twilio Messages data, including fields such as sid, body, date_created, date_sent, direction, status, from, to, price, and more. Some fields like body are available for up to 30 days, while from/to are available for up to 120 days.
Can I send Twilio data to a BI tool or spreadsheet?
Yes. After saving the Twilio source, you can create pipelines to replicate data to your Data Warehouse or Data Lake, then connect to BI tools or spreadsheets for analysis.
Is there a pre-built dashboard for Twilio data?
Yes, you can explore Data Studio dashboards for Twilio or check other report templates available on Kondado to visualize your messaging data.

Written by·Published 2023-06-16·Updated 2026-04-25