Accept a short spoken response, a keypad key, or either.
Connector Studio + speech
Make the inbound call part of the workflow.
Ask a focused question, use live business data to decide what happens next and speak the answer back. The call stays inside the routing, reporting and safety controls of CallPlatform.
Available now for public HTTPS JSON APIs using no authentication, an API-key header or a bearer token. OAuth installation is not part of the current release.
Inbound journey · booking status
Designed route
Send approved inputs to a public HTTPS JSON endpoint.
Keep reviewed scalar outputs for the next step in the call.
Speak a useful message, transfer, queue or take another route.
Write-onlySaved secrets
≤ 10 secondsProvider wait
512 KBJSON response limit
3 auth modes
Encrypted secrets
Pinned revisions
Named outcomes
Timeout + error routes
From endpoint to call-flow action
Integrations that behave like building blocks.
Connector Studio keeps provider credentials, request mapping and response logic away from the call-flow canvas. Designers choose a reviewed action, bind its inputs and connect the business outcomes that matter.
- Store a connection once at account level instead of copying a secret into every flow.
- Turn provider-shaped JSON into clearly named inputs, outputs and routes.
- Publish an immutable revision so a live flow keeps the action contract it was tested against.
- Make timeout, error and provider-specific outcomes visible before the service can be published.
Connect
Name the system and environment, choose no auth, API key or bearer token, then save the credential securely.
Define
Describe the HTTPS request, approved inputs, output mappings and the business outcomes the response can select.
Test and publish
Exercise a safe action, inspect the outcome and create an immutable account-owned revision.
Route
Pin that revision in Flow Builder and connect every named outcome, Timeout and Error path.
Built for live calls
Useful power, with deliberate boundaries.
An in-call integration has seconds, not minutes, to return. Its failure cannot become a dead end. Connector Studio makes that operating reality part of the product.
Secrets stay out of the flow
Credentials are encrypted separately and become write-only after saving. They are not returned to the browser, inserted into the call flow or retained in live call state.
Public HTTPS only
Destinations must resolve to a public HTTPS address. Private, local, link-local and reserved addresses are rejected, DNS is pinned for the request and redirects are not followed.
Small, synchronous contracts
Requests and responses use JSON. Provider waits are bounded from 250 to 10,000 ms and responses are limited to 512 KB, keeping the action suited to an active caller.
Change without surprise
Edits create a new immutable revision. A published node stays pinned until somebody deliberately selects and tests a newer action contract.
Failure is a route
Every named result sits alongside Timeout and Error. If an outcome is unknown, the flow can explain, retry safely where appropriate or hand the call to a person.
Evidence without payload sprawl
Operational events retain identifiers, selected outcome, timing and output names. They do not retain credentials, input values or the provider response body.
A timeout means the final provider result may be unknown. Changing actions should not be repeated automatically unless the provider contract supports a safe state check or idempotency key.
Available Connector Studio templates
Start reviewed. Adapt deliberately.
Install only the actions you need. Each template becomes an account-owned connector revision, so a later catalogue update cannot silently change a live flow.
Taxi self-service
Reviewed actions cover current and future booking lookup, dispatch status, cancellation, company resolution, tracking, vehicle, zone and ETA use cases.
Recognise the caller
Find a contact by phone or mobile phone and optionally create one using a customer-created HubSpot private-app bearer token.
Tell the right channel
Post an inbound-call alert or concise outcome using a manually issued Slack bot token with the required channel permission.
Bring your own adapter
Start from a small public HTTPS contract for caller lookup, call decisions and event recording, then edit it to match your developer-owned API.
These are the current templates, not a promise of automatic connectivity to every system. HubSpot and Slack use manual restricted tokens today; marketplace OAuth installs and automatic token refresh are future work. Slack actions are synchronous, so use an asynchronous Web Request when delivery must never delay a caller.
TTS + STT + Connector Studio
Explore speech-enabled flows
Listen. Look up. Speak. Keep the escape route.
Focused Speech Input and dynamic Speak Text turn a connector result into practical caller self-service without forcing every journey into an open-ended AI conversation.
Ask
Invite one short answer and retain keypad input as an option where it helps.
Act
Bind the captured value and call data into a pinned Connector action.
Answer
Speak approved output values back as a useful, personalised response.
Recover
Route no match, no input, timeout and provider error to a safe next step.
Use focused speech for short, structured requests; use AI Agent Studio for a genuinely open-ended conversation; use recorded audio when the message never changes.
Practical starting points
Automate one valuable call reason first.
Choose a request with a clear data source, a bounded response and a useful human fallback. Prove it, measure it and expand from evidence.
“Where is my driver?”
Use an approved booking lookup, speak the current status or ETA and send ambiguous or unavailable results to dispatch.
Route with known context
Look up an exact telephone match, retain reviewed fields and take a different route for a known account, tier or service need.
Ask your system what comes next
Call a customer-operated adapter and map its explicit answer to named routes such as approved, refer or unavailable.
Examples depend on the provider contract, data permissions and selected CallPlatform options. We design sensitive or provider-changing actions with confirmation, least-privilege access and a safe route when the result is uncertain.
Why it belongs in CallPlatform
More than a webhook bolted to a phone call.
Connector Studio was designed around the result of the action and what the caller should experience next, not just whether a technical request succeeded.
| Capability | CallPlatform Connector Studio | Typical webhook-only node |
|---|---|---|
| Reusable credentials | Encrypted, account-owned and write-only after save | Often configured per flow or delegated to external middleware |
| Business result | Named provider outcomes with reviewed scalar outputs | Usually success/failure plus raw response handling |
| Change control | Immutable revision pinned by the published call flow | Often dependent on manual versioning |
| Caller experience | Speech, routing, queue, IVR, voicemail and human fallback in one journey | Additional voice and telephony layers normally required |
| Failure design | Named outcomes plus required Timeout and Error routes | Varies by tool and implementation |
Category-level comparison; webhook products vary. We will compare Connector Studio against the exact tools and provider contracts in your proposed design.
Connector Studio FAQ
Clear answers before you connect a live call.
Can Connector Studio connect to any system?
No. The current runtime is for synchronous public HTTPS endpoints that exchange JSON and can authenticate with no credential, an API-key header or a bearer token. A provider may need a reviewed custom action or customer-operated adapter; private endpoints, non-JSON contracts and unsupported authentication do not become compatible by entering a URL.
Does it support OAuth?
Not in the current Connector Studio release. HubSpot uses a customer-created private-app token and Slack uses a manually issued bot token. Provider OAuth needs installation callbacks, scopes, refresh, expiry, revocation and reconnect handling, and we will only market it when that lifecycle is built.
Can a flow designer see a saved API secret?
No. The portal stores connector credentials separately in encrypted form and only exposes a masked hint. A saved value cannot be read back; rotation means entering a replacement credential and publishing the intended revision.
What happens when the provider times out?
The Connector Action follows its Timeout route. That result is intentionally distinct from a provider-defined outcome and from Error. Because a timed-out change may still have completed remotely, the safe next step is normally to check its status rather than blindly repeat it.
When should I use Web Request instead?
Use Web Request for a simple one-off webhook or event delivery that does not need a reusable provider contract, retained mapped outputs and multiple named business outcomes. Use Connector Studio when a credential or action will be reused across flows and the returned result changes the caller’s route.
Bring us the call reason and the API
Turn one inbound request into a working journey.
We’ll map the question, the data contract, each named outcome and the human escape route. Then we’ll show how speech, Connector Studio and CallPlatform fit around it.