Calls an assigned user, announces the contact, then connects the contact after confirmation. Identifier: call_connect.

Call Connect

Identifier and availability

Type: action
Stable identifier: call_connect
Status: Selectable — available in the new-node selector and importable.

Purpose

Calls an assigned user, announces the contact, then connects the contact after confirmation.

Prerequisites and context

Required configuration: settings. Runtime requires a Contact, an active Twilio voice channel, valid E.164 Contact and caller-ID numbers, and either an active assigned user with a valid phone or Company Phone when the Contact is unassigned.

Parameters

JSON path	Type	Required	Default	Allowed values	Description
`settings`	object	Yes	—	—	Node-specific settings. Unknown keys are rejected.
`settings.whisper_message`	string	No	—	—	Optional text spoken privately to the internal recipient before the Contact is dialed. Automation variables are supported.
`settings.timeout_seconds`	integer	Yes	30	5 to 600	Maximum time, in seconds, to ring each call leg.
`settings.disable_voicemail_detect`	boolean	No	false	—	When true, do not use answering-machine detection on the Contact call leg.
`settings.connect_after_keypress`	boolean	No	true	—	When true, require the internal recipient to press a numeric key before dialing the Contact.

Unknown parameter and settings keys are rejected. Resource references use names, emails, document keys, or endpoints rather than database IDs.

Inputs and available variables

This node declares no additional variable groups. The always-available date group and context inherited from its path still apply.

Templated strings use double braces, for example {{contact.first_name}}. Availability in the editor does not create runtime context; the trigger and preceding branch still need to provide it.

Connections and branches

This is a sequential action with no branch ports. A root placement uses from set to null and branch set to actions; a branch placement uses the branching action key and branch token. Use a 1-based order within that path.

Connection fragment:

{
    "from": null,
    "to": "action_call_connect",
    "branch": "actions",
    "order": 1
}

Valid JSON node example

{
    "key": "action_call_connect",
    "type": "action",
    "name": "call_connect",
    "display_name": null,
    "parameters": {
        "settings": {
            "whisper_message": "You have a call with {{contact.full_name}}.",
            "timeout_seconds": 30,
            "disable_voicemail_detect": false,
            "connect_after_keypress": true
        }
    }
}

Validation and runtime caveats

The call starts asynchronously. The internal recipient is called first; an internal answer is not a successful Contact outcome. With keypress confirmation enabled, any numeric key confirms and three unanswered prompts end the call. Voicemail detection applies to the Contact leg unless disabled. Company Phone is used only when the Contact has no assigned users.

See the Automation JSON import format for the envelope, dependency resolution, graph rules, complete examples, and AI author checklist.

Call Connect Automation Action