How do Input Nodes and Node IDs work in MyOperator IVR, and how do I set them up?

How do Input Nodes and Node IDs work in MyOperator IVR, and how do I set them up?

⚡ Quick answer -

• An Input Node is the IVR block that captures caller input (DTMF tones or speech), posts that input to your webhook in real time, and then executes the next IVR action based on your webhook’s JSON response.

• A Node ID is the unique identifier for each step (node) inside Advanced Call Flow. Use it to reference a specific step in automations, APIs, or analytics.

When should I use this guide?

Follow these steps if you need callers to enter a PIN, account number, language choice, etc., during the call—and have MyOperator forward that data to your server—or if you plan to route callers programmatically, trigger actions at a step, or log step-level analytics using Node IDs.

1. What is an Input Node?

An Input Node is the IVR block that captures caller input (DTMF tones or speech), posts that input to your webhook in real time, and then executes the next IVR action based on your webhook’s JSON response.

2. Why use an Input Node?

  • Caller verification – collect account IDs, OTPs, or dates of birth.
  • Dynamic routing – send callers to agents/queues based on language or location.
  • Surveys & NPS – capture 0–9 ratings before the call ends.
  • Anonymous, time-bound bridges – create one-off conference rooms for >200 guests.

3. Prerequisites & permissions

Item

Required?

Where to configure

Notes

Pro or Enterprise plan

Yes

Billing → Upgrade

Feature add-on

Public HTTPS webhook

Yes

Your infrastructure

Must answer in ≤ 3 s

API token (ivr.write)

Yes

Settings → API Tokens

Paste in the header

Speech-to-text add-on

Optional

Add-ons → Speech

Needed for voice input

Anonymous user access

Optional

IVR → Advanced

For callers not pre-registered

Watch the video walkthrough

Alt text: video demo

4. How the Input Node works

image.png

Alt-text: Sequence diagram showing the round-trip between the caller, MyOperator, the Input Node, and your webhook.

5. Step-by-step setup (Input Node) and finding the Node ID

  1. Log in to the MyOperator Panel.
  2. Go to Call → Design call flow → call flow design → IVR → Edit Flow and drag the Input Node into your call flow.

image.png

image.png

  1. Node ID can be found by:
    1. Click a node (e.g., “IVR Menu” or “Route to Agent”).
    2. In the right-side Settings/Info panel, locate Node ID.
    3. Copy the ID 

image.png

Alt text: Node ID can be found in Design Callflow section in MyOperator panel.

  1. In the right-hand pane, configure: 
    1. Prompt text or TTS URL 
    2. Expected input type: Numeric | Alphanumeric | Speech 
    3. Timeout (sec) and max retries 
    4. Webhook URL (HTTPS POST)
  2. Click Save.

image.png

Alt text: Parameters will be sent according to the format configured on MyOperator panel in section MyOperator/Integration/Webhook

  1. Open Settings → API Integrations → Allowlist Domains and add your webhook host.
  2. Click Publish IVR.
  3. Place a test call to verify the round-trip.

6. Testing & expected results

  1. Dial the virtual number.
  2. When prompted, enter 1234 (or speak, if speech input is enabled).
  3. Your webhook should log the incoming payload and return a JSON action.
  4. MyOperator should immediately execute that action (e.g., dial an agent).

Success criteria:

✔️ Caller hears the correct prompt.

✔️ Webhook receives input_value.

✔️ Call is routed per your JSON response.

✔️ No “timeout” or “invalid input” message is played.

7. Edge cases & when NOT to use

  1. High latency webhooks – if your server can’t answer in < 3s, callers will hear silence or a retry prompt.
  2. No internet failover – Input Nodes require an external call; during network outages, IVR will fail.
  3. Sensitive PCI data – Collecting full credit-card numbers may violate compliance rules; use a dedicated PCI-compliant capture service instead.
  4. Very short calls (<5 s) – some carriers cut the call before the prompt finishes; add a 2-second wait node first.
  5. Permissions: If you can’t see Node ID, you may lack Edit Call Flow access. Ask an admin.
  6. Deleted nodes: If a node is removed, any automation using its Node ID must be updated.
  7. Flow copies: Duplicating a flow can produce different Node IDs for the new nodes.
  8. Environment drift: Ensure sandbox/test flows use the same node names, but confirm IDs before deploying.

8. Troubleshooting & escalation

Problem → Likely cause → Fix

  • “Invalid input” replay loops → Input type mismatch → Set “Numeric” if expecting digits only.
  • Webhook 401 errors → Wrong token → Re-generate API token with ivr.write.
  • “Node ID not visible” → Ensure you’re in Advanced Call Flow (not legacy/simple flow) and have edit rights.
  • “API error: invalid target_node_id” → Confirm the ID exists in the chosen flow_id and isn’t a deleted node.
  • “Call routed to the wrong place” → Double-check you passed the correct flow_id and target_node_id pair.

Still stuck?

• Review live logs in Analytics → Live Calls.

• Email support@myoperator.com with account ID, flow name, node name, Node ID, time of test, sample caller number, and any request IDs.

Keywords: Input Node, MyOperator, IVR, webhook, DTMF, speech input, dynamic call routing, caller verification, real-time IVR API