- Démarrage
- UiPath Conversational Agents
- Agents UiPath dans Studio Web
- À propos des agents UiPath
- Licences
- Exécuter des agents
- Agents et workflows
- Meilleures pratiques pour créer des agents
- Choix du meilleur modèle pour votre agent
- Meilleures pratiques pour la publication et le déploiement d’agents
- Meilleures pratiques en matière d’ingénierie contextuelle
- Meilleures pratiques pour DeepRAG et la transformation par lots : JIT vs. stratégies basées sur l’index
- Utiliser des fichiers
- Contextes
- Escalades
- Évaluations
- Traçages d’agent
- Score de l’agent
- Gérer les agents UiPath
- Agents codés UiPath
- Créer avec des agents codés
Connect a number hosted on your own Twilio account to a UiPath voice agent.
If your number lives on Twilio, connect your Twilio account directly. UiPath sets the number's voice webhook for you, so there is no Session Initiation Protocol (SIP) trunk to build and no inbound access to authorize.
Do not point a Twilio Elastic SIP Trunk at your UiPath SIP domain. UiPath's own SIP endpoint is hosted on Twilio, and Twilio does not route SIP between two of its own domains. Connect the Twilio account instead.
How a call reaches your agent
Twilio Programmable Voice holds the number and streams the call's audio to UiPath. The Conversational Service runs the agent — chat history, agent loop, and call control — and reaches the models through the LLM Gateway, which applies AI Trust Layer governance, monitoring, and audit. The Flow you publish supplies the design, and tool calls execute in the Unified Runtime.
There is no carrier ahead of Twilio on this path, and no trunk between Twilio and UiPath.
Avant de commencer
- The prerequisites — see Deployment.
- A number bought or ported into your own Twilio account.
- Your Twilio Account SID and Auth token, from your Twilio console.
- For incoming calls — a Flow with an Incoming call trigger, published to Orchestrator.
Connect the number
- In the Agents page, go to Phone numbers.
- Select Connect number, then select Twilio in the left rail.
- Enter a Label and the Phone number in E.164 format.
- Select a Direction — Incoming, Outgoing, or Both.
- Under Twilio account, enter your Account SID and Auth token.
- For an incoming flow, select the published Flow Process and its Incoming call trigger (entry point) under Inbound binding.
- Select Connect.
There is no Outgoing configuration on this path, and no SIP domain to copy. Once the number is connected, Twilio account shows the connected SID with a Disconnect action, and later Twilio numbers reuse that account without asking again.
One Twilio account is stored per tenant, shared by every Twilio number on it, so you enter the credentials only once.
Check the webhook in Twilio
Nothing needs configuring on the Twilio side. For verification purposes only, open the number in your Twilio console under Phone Numbers > Manage > Active numbers, then look at Voice Configuration:
| Champ | Expected value |
|---|---|
| Configure with | Webhook, TwiML Bin, Function, Studio Flow, Proxy Service |
| A call comes in | Webhook, with a uipath.com URL and HTTP POST |
If Configure with is set to SIP Trunk, the number routes to a trunk and UiPath's webhook never fires. Set it back to the webhook option.
Connecting a number overwrites its Voice Configuration, including any existing webhook URL or TwiML application. Note the current settings first.
How your Twilio credentials are stored
Your auth token is encrypted at rest and is never shown again after you save it — the dialog only lets you replace it.
Encryption follows your tenant's own key configuration. If your organization uses customer-managed keys, the token is encrypted under your key rather than a UiPath-managed one, which is the default. See customer-managed keys for enabling them on your tenant.
Associé
- Voice — overview, limitations, and which providers work.
- Deployment — prerequisites and the inbound app registration.
- Any SIP provider — the SIP Trunk option, for a number held anywhere else.