Authentication

An Auth Directory lets an Advanced project keep a list of people who are allowed past a sensitive point in a call — a per-project directory of identities, each checked by phone number and a PIN entered on the caller’s keypad.

Managing a directory

Advanced projects have an Authentication tab in the project sidebar. From it you can:

• Create one or more directories for the project.
• Add entries to a directory — each entry is an identity (a display name or external id), a phone number in international format, a PIN, and an optional email address.
• A phone number can only appear once per directory; adding a duplicate is rejected.

The PIN is never stored or shown in plain text — it is hashed the moment you set it, and the original value doesn’t leave the form. Nobody, including your team, can look up a stored PIN later; an entry’s PIN can only be replaced, not revealed.

External (webhook-based) authentication is listed as coming soon and cannot be enabled yet.

Using a directory in a flow

An Authentication node connects a directory to a specific step of a flow, so a caller has to clear the PIN check — by keypad, by voice, or either — before the conversation continues, and any later step can be marked as reachable only after that check passes. See Authentication node for what it does, the input options, what it saves for later steps, and how guarded steps work. It’s in preview: the directories and entries above are fully manageable today, and the node itself is documented ahead of being offered on every plan.