Twilio
This page contains the setup guide and reference information for Twilio.
Prerequisites
- Twilio Account SID
- Auth Token
Setup guide
Step 1: Obtain Twilio credentails
Sign in to your Twilio account.
You will find your Account SID and Auth Token on your Twilio dashboard. Copy them.
Step 2: Set up Twilio in Daspire
Select Twilio from the Source list.
Enter a Source Name.
Enter the Account SID you obtained in Step 1.
Enter the Auth Token you obtained in Step 1.
For Start Date, enter a UTC date and time in the format
YYYY-MM-DDTHH:mm:ssZ. The data added on and after this date will be replicated.For Lookback Window, enter the number of days you want data to be replicated.
Click Save & Test.
Supported sync modes
| Feature | Supported? |
|---|---|
| Full Refresh Sync | Yes |
| Incremental Sync | Yes |
| Replicate Incremental Deletes | No |
| SSL connection | Yes |
| Namespaces | No |
Output schema
This Source is capable of syncing the following core Streams:
- Accounts
- Addresses
- Alerts (Incremental)
- Applications
- Available Phone Number Countries (Incremental)
- Available Phone Numbers Local (Incremental)
- Available Phone Numbers Mobile (Incremental)
- Available Phone Numbers Toll Free (Incremental)
- Calls (Incremental)
- Conference Participants (Incremental)
- Conferences (Incremental)
- Conversations
- Conversation Messages
- Conversation Participants
- Dependent Phone Numbers (Incremental)
- Executions (Incremental)
- Incoming Phone Numbers (Incremental)
- Flows
- Keys
- Message Media (Incremental)
- Messages (Incremental)
- Outgoing Caller Ids
- Queues
- Recordings (Incremental)
- Services
- Step
- Roles
- Transcriptions
- Trunks
- Usage Records (Incremental)
- Usage Triggers
- Users
- UserConversations
- VerifyServices
Performance considerations & troubleshooting
The Twilio integration will gracefully handle rate limits. For more information, see the Twilio docs for rate limitations.
Max number of tables that can be synced at a time is 6,000. We advise you to adjust your settings if it fails to fetch schema due to max number of tables reached.