Autocloz + SignalWire
SignalWire is a Twilio-compatible carrier that Autocloz lists for voice and SMS. The Settings → Integrations card takes a Project ID, an API token, your Space URL and a from-number. Right now the adapter cannot read those fields: it expects the project ID and token under Twilio-style names, so SignalWire calls fail before reaching SignalWire, with an error that names the missing values. For calls today use Telnyx, or Twilio for SMS.
Status: limited today. Measured on 2026-09-28: with the SignalWire card filled in, call and SMS touches fail with "SignalWire account_sid + auth_token + extras.space_url required". Nothing is sent.
What you can do with SignalWire
SignalWire plugs into the Call stack — bring your own carrier account, scoped to your workspace.
Project, token and space saved
The three values SignalWire needs are stored encrypted on your workspace's SignalWire card.
LaML-compatible adapter
The adapter posts to your space's LaML Calls endpoint and falls back to a simple Say response built from the step's script when no TwiML URL is given.
Clear error on failure
A send that cannot run is logged as failed with the missing field names, so reports never show a call that did not happen.
How to connect SignalWire
Bring your own carrier account — you keep control of the account, the spend and the data boundary.
- 1
Copy your Project ID and API token
In the SignalWire dashboard open API and copy the Project ID and a token with calling and messaging scopes.
- 2
Note your Space URL
It looks like example.signalwire.com. Paste it without https:// into Space URL on the card.
- 3
Save and try one send
Save the card in Settings → Integrations, then send one test. Expect the field-mapping error described above.
- 4
Route live traffic elsewhere
Keep the SignalWire settings, and point call and SMS steps at a working provider until the mapping is fixed.
What to check before switching carriers
Numbers belong to the carrier that issued them, so moving from SignalWire to Telnyx or Twilio means using numbers on that carrier or porting yours. If you rely on SignalWire's own call flows, keep them in SignalWire and use Autocloz for the CRM and sequences on other channels until calls work here. Campaign analytics will show SignalWire touches as failed with the mapping message, which is the quickest way to confirm nothing is leaving through SignalWire.
- Card fields: Project ID, API token, Space URL, from-number.
- Adapter expects: account SID, auth token and space URL.
- Status on 2026-09-28: fails before the request.
Where the SignalWire mapping breaks
SignalWire accepts Twilio's REST shape with the project ID as the account SID and the API token as the auth token. The Autocloz adapter follows that shape and asks for account_sid and auth_token. The settings resolver, however, treats project_id as an extra field and files api_token as an API key, so the adapter receives neither and stops.
The adapter and the Space URL handling are otherwise in place. When the resolver maps project_id and api_token correctly, calls would go to your space's /api/laml/2010-04-01 endpoint with basic auth.
How call content would be delivered
If a TwiML URL is configured, SignalWire fetches call instructions from it. Otherwise the adapter sends inline TwiML that reads the step's script with a Say verb, capped at 1,500 characters. That is text-to-speech playback, not a live agent. For conversational AI calls, Autocloz supports Sarvam agents over Telnyx only; see AI agents.
What SignalWire does not do in Autocloz
- Calls and SMS fail today when configured only through the card.
- No in-browser softphone, inbound call webhook or recording import for SignalWire.
- Delivery and call-status callbacks need a relay that translates them for Autocloz's outcomes endpoint.
Troubleshooting SignalWire
- Touches fail with "account_sid + auth_token + extras.space_url required".
- Known mapping gap. Your values are fine; switch the step to another provider for now.
- Space URL rejected.
- Enter the bare host, for example acme.signalwire.com, without a path.
Part of the Call stack
SignalWire is one of several carriers you can run behind the Call channel. They share the same dialer, CDR logging, recordings UI and compliance gates.
Explore the Call featureRelated integrations
Call Control v2 + WebRTC softphone, signed-URL recordings, Ed25519 webhook verification.
View integrationIn-browser Voice SDK calling + low international SIP rates; CDR poll for retroactive ingest.
View integrationIndia-native voice with per-agent OAuth, presence sync + recording import.
View integrationFrequently asked
Is SignalWire really Twilio-compatible in Autocloz?
The adapter uses the Twilio-compatible endpoints. What is missing is the mapping from the card's field names to that shape.
Can I use SignalWire numbers with Telnyx?
No. A number is tied to the carrier that owns it. Add Telnyx numbers to a Telnyx sender instead.
Run SignalWire inside Autocloz
Bring your own account, plug it into the Call channel, and keep a free-forever CRM for 3 users.