Provider Connectors are configuration items that define the connection and authentication of Nimbus with external communication providers. The goal is to leverage external APIs, allowing communication between external customers and internal Nimbus services.
✅PRECONDITIONS
💡The current implementation is limited to https://www.twilio.com/ as vendor. To set up this configuration entity correctly, you need:
- A working Twilio API set up.
- The
API Key SIDfrom your Twilio service, which is needed for later mapping to a Nimbus service.
| Field | Description |
|---|---|
| Name | Name of the Provider Connector. |
| Organization Unit | Organization Unit placement of the Provider Connector. |
| Type | 💡Currently locked to Twilio as selection. → Visit: https://www.twilio.com for more information. |
| API Key SID |
💡Example for a valid SID Ensure you only paste the (limited scope) API Key SID, not your entire Twilio account SID in Nimbus. The latter would grant access to your entire Twilio account. 🔎 From the Twilio Documentation: What is a Twilio Account SID and where can I find it?
|
| API Key Secret |
💡A field for the API secret, created when you create a new API Key resource in Twilio. This unique key can be up to 256 characters in length. ☝Store the secret in a secure location, because you won't be able to retrieve it again. Twilio uses the Key resource's |
| Region |
The list of regions that Twilio supports:
1☝Note: Data ResidencyFrom the Twilio Documentation: Twilio Regions
|