Twilio (SMS history) connector
Connect Twilio (SMS history) to Silux Chat with a read-only connection for account activity. It is tested with a real call when you connect it and re-checked every day.
Good to know: Returns the messages a phone number (E.164, e.g. +447700900123) has sent to your Twilio numbers.
What your bot can do with Twilio (SMS history)
Account activity
Reads account activity held in Twilio (SMS history) for the verified customer and adds it to their account summary.
Customers ask: “Did my message get through?”
Connected and tested when you connect Twilio (SMS history), but the bot does not answer customers from it: Twilio (SMS history) can’t prove who is asking, and these records are personal. Email support@siluxcall.co.uk to discuss using it.
Set it up
Most businesses finish in under ten minutes. You need to be able to sign in to Twilio (SMS history) as an administrator to create the key.
Step 1 — in Twilio (SMS history)
- 1Twilio Console
- 2Account Info
- 3copy the Account SID and Auth Token.
Least access: grant only the read permissions named above (customers, orders, invoices, bookings or tickets — whichever this connector uses). Never use an owner or full-admin key where Twilio (SMS history) lets you create a restricted one.
Step 2 — in Silux Chat
- 1Open Dashboard → Integrations → Connectors and search for “Twilio (SMS history)”.
- 2Fill in:
Field Example Stored Account SID (AC…) •••••••• Encrypted Auth token •••••••• Encrypted - 3Press Connect & test. The platform makes a real, read-only call to Twilio (SMS history) with a made-up customer and shows a tick or a cross for each capability, with Twilio (SMS history)’s exact error if something is refused.
Twilio (SMS history) identifies API users with a key-and-secret (or username-and-key) pair, sent with HTTP Basic authentication over HTTPS.
How customer verification works
Twilio (SMS history) holds no customer records that the platform can match by name and email, so this connector cannot verify customers by itself. It is tested when you connect it and re-checked every day. To plan how its data should reach your customers alongside your verification route — a connector that can look customers up, or your own Account Connect endpoints — email support@siluxcall.co.uk.
What the bot can and cannot see
Can see (after verification)
Nothing — see the verification section above.
Only these standard fields are mapped from Twilio (SMS history)’s responses. Everything else in the response is discarded before the bot sees it.
Never sees
- passwords, security answers or login details
- records belonging to anyone other than the verified customer
- anything outside the fields listed alongside
Security
Keys encrypted at rest
Credentials are stored encrypted, shown only masked after saving, and destroyed — not just hidden — when you disconnect.
Read-only look-ups
Every capability is a look-up. The connector cannot create, change or delete anything in Twilio (SMS history).
HTTPS only
Calls go to the vendor’s HTTPS address, redirects are not followed, and private network addresses are refused.
Injection-safe
Values a customer types are cleaned before they are placed in Twilio (SMS history)’s search, and URL-encoded in addresses.
Other customers filtered out
A row that names a different customer’s email is dropped, whatever the vendor’s search returned.
Checked daily
Connections are re-tested every day, and the owner is emailed if a working connection starts failing.
More: Security & data protection.
Technical details
For developers and IT teams: the Twilio (SMS history) endpoints this connector reads. Values in braces come from the settings you enter.
| Capability | Request | Standard fields returned |
|---|---|---|
| Account activity | GET/Messages.json | id, from, to, body, status, direction, sent |
Test level: Documented-API tested. Each capability is run automatically against Twilio (SMS history)’s documented example responses and must produce the standard fields; your own connection is then tested with a real call when you connect. The bot receives these through the standard Account Connect endpoints, exactly as if you had built them yourself.
Troubleshooting
| What you see | Likely cause and fix |
|---|---|
| “the vendor refused the credentials (401)” or (403) | The key was revoked, has expired or was copied incompletely, or it lacks a read permission this connector needs. Create a fresh read-only key in Twilio (SMS history) and reconnect. |
| Customers are “not matched” although they exist | Customers are looked up by email or mobile, not postcode. Check the customer’s email or mobile is saved on their Twilio (SMS history) record, and that the surname matches. |
| A capability shows a cross but others work | That permission wasn’t granted in Twilio (SMS history), or your Twilio (SMS history) plan doesn’t include that part of the API. Grant it and press Test. |
| “the vendor kept rate-limiting the request” | Twilio (SMS history) returned “too many requests” three times in a row. The platform already waits and retries automatically (up to 10 seconds, as Twilio (SMS history) asks); if it persists, ask Twilio (SMS history) about your API quota. |
| Results are empty for a verified customer | The records exist under a different email or customer record in Twilio (SMS history), or none are recent. Check the customer’s record in Twilio (SMS history) directly. |
Full error reference: Troubleshooting & error reference.
Frequently asked questions
Is the Twilio (SMS history) connection read-only?
Yes. Every request Silux Chat makes to Twilio (SMS history) is a look-up; none creates, changes or deletes anything in Twilio (SMS history). Give the key or sign-in read-only permissions wherever Twilio (SMS history) offers them.
Do I need a developer to connect Twilio (SMS history)?
No. You paste the details listed in the set-up steps in Dashboard → Integrations → Connectors and press “Connect & test”. The platform makes a real call to Twilio (SMS history) straight away and shows exactly which features work.
How does the bot know it is really my customer?
Twilio (SMS history) holds no customer records the platform can search, so it cannot verify customers by itself. See the verification section on this page, or email support@siluxcall.co.uk to plan the right set-up.
What happens if my Twilio (SMS history) key is revoked or expires?
The bot tells customers it can’t check their account right now — it never pretends there are “no orders”. Connections are re-tested daily and the account owner is emailed when a working connection starts failing. Reconnect it in Dashboard → Integrations → Connectors.
How has the Twilio (SMS history) connector been tested?
It is Documented-API tested: every capability is run automatically against Twilio (SMS history)’s documented example responses and must produce the standard fields. When you connect, it is tested again with a real call to your own Twilio (SMS history) account before your bot uses it.
Need help with your integration?
Our integration team can review your endpoints, help you choose the right connector and check a test run with you. Tell us which system you use and what you would like the bot to answer.