VICIdial icon

VICIdial

Interact with VICIdial Non-Agent API

Actions58

Overview

This node provides an interface to perform the "Blind Monitor" operation within a broader set of "Other Operations" for the VICIdial Non-Agent API. The Blind Monitor function allows users to silently listen in on a call session without alerting the parties involved. This is useful in call center environments for quality assurance, training, or supervisory purposes.

Typical use cases include:

  • Supervisors monitoring live calls to ensure compliance and service quality.
  • Trainers listening to agent calls to provide real-time feedback.
  • Managers auditing calls for performance evaluation.

Properties

Name Meaning
Function API function name; fixed to "Blind Monitor" for this operation.
User API user credential username used for authentication.
Pass API password credential used for authentication.
Source Description of what originated the API call; default is "n8n".
Phone Login The phone login identifier related to the call session to monitor.
Session Id The unique session ID of the call to be monitored.
Server Ip IP address of the server handling the call session.
Stage Output format of the response; options are Csv, Tab, Pipe, or Json (default: Pipe).

Output

The node outputs the API response in the json field of the output data. The structure depends on the selected output format (stage property):

  • Csv, Tab, Pipe: The response is returned as plain text formatted accordingly (comma-separated, tab-separated, pipe-separated).
  • Json: The response is parsed and returned as JSON.

No binary data output is indicated by the code or properties.

Dependencies

  • Requires an API key credential with username and password for authenticating against the VICIdial Non-Agent API.
  • Needs the base URL of the VICIdial server configured in credentials.
  • The node sends HTTP requests to the /vicidial endpoint of the configured host.
  • No additional external dependencies beyond standard HTTP request capabilities.

Troubleshooting

  • Authentication errors: Ensure that the provided user and password credentials are correct and have sufficient permissions.
  • Invalid session or phone login: Verify that the phone_login and session_id correspond to an active call session.
  • Server connectivity issues: Confirm the server_ip and base URL are reachable from n8n.
  • Unexpected output format: If parsing JSON fails, try changing the stage property to a plain text format like Pipe or Csv.
  • API errors: Check the API documentation for error codes returned in the response body.

Links and References

Discussion