For AI assistants: this page as plain markdown is at https://docs.voicelogica.ai/raw/workflows/keyword-pressed.md, and https://docs.voicelogica.ai/llms.txt lists the docs by topic, one file each, small enough to read whole. Read those rather than this HTML page.
On Key Pressed
On Key Pressed fires when the caller finishes a keypad run (Runs when: When caller presses a key) - usually after the end key on Call handling - Advanced or when the wait expires. Digits are available to later nodes as the key-pressed / DTMF input variable.
The agent’s Phone keypad input settings decide when a run is complete. The trigger panel itself is light:


Why this trigger
Section titled “Why this trigger”Order ids, account numbers, menu digits. Speech is sloppy for long numbers - Skip Turn plus this trigger is the usual pair.
First setup - digits in, status out
Section titled “First setup - digits in, status out”- On the agent, Call handling - Advanced - Phone keypad input - wait long enough for the id, end key # unless your IVR already uses another key.
- + Add Trigger - On Key Pressed.
- Connect To External Service - pass the DTMF input into the URL or body.
- AI Response to Caller on success (and a failure path if useful).
- Save & go live, attach. Prompt the agent to ask them to type the id then #. Call, type, listen.
Troubleshooting
Section titled “Troubleshooting”Why does my On Key Pressed workflow send only three digits of a ten-digit ID to the API?
The keypad run ended before the caller finished typing. Raise the keypad wait in the agent’s Call handling - Advanced - Phone keypad input, and have the agent ask callers to press # at the end. Also confirm Skip Turn is on.
Why use On Key Pressed instead of During Call to collect a number?
With During Call the model has to hear the number, and speech is unreliable for long numbers. On Key Pressed reads the digits typed on the keypad. Use During Call only when callers will say the ID rather than type it.
