Why does this connector show no named actions?

Because the action is whatever endpoint you configure — it’s a generic HTTP caller, so there’s no fixed action list. You define the request per workflow.

When should I use Custom REST?

When the system you need doesn’t have a dedicated Voicent connector yet — a homegrown backend, a niche SaaS, or a webhook you control.

What auth does it support?

You configure the auth the target API requires, so headers, tokens, or keys are set per endpoint rather than assumed.

Custom · Integration

Custom REST API + Voicent AI

Voice workflows that actually work — not just call transfers.

The Custom REST connector lets a Voicent agent call any HTTP API you configure — the escape hatch for the system you use that doesn’t have a dedicated connector yet.

Book a demo See workflows

Custom0 actionscustom auth

Overview

Not every system you run has a dedicated connector — so Voicent ships an escape hatch. The Custom REST connector calls any HTTP endpoint you configure, with the auth, headers, and body you specify, mapping call data into the request and the response back into your workflow. It exposes no fixed named actions because the action is whatever you point it at: your internal API, a niche SaaS, a webhook. When a purpose-built connector doesn’t exist yet, this is how you still reach the system during or after a call.

What your agent can do with Custom REST API

Voicent can call any REST endpoint you configure — you define the request per workflow.

How it works

You configure the endpoint, auth, headers, and request shape for the API you want to reach.
The workflow maps call data into the request and sends it during or after the call.
The response maps back into workflow variables for the agent or a later step to use.

What the agent actually says

I've sent that over to our system and it's been recorded.

Put it in a workflow

Combine Custom REST API with triggers, branches, and other connectors in a Voicent workflow.

Browse workflow templates →

In practice

Any internal or third-party API, reachable from a call.

A company with a homegrown backend wires it into Voicent through the Custom REST connector, mapping a call outcome to their own API endpoint without waiting for a purpose-built integration.

Custom REST API + Voicent AI

See Custom REST API + Voicent on a real call.