3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

This node integrates with the 3CX telephony system, specifically allowing users to initiate phone calls programmatically. It is useful in scenarios where automated call initiation is needed, such as customer support callbacks, sales outreach, or alert notifications. For example, a workflow could trigger a call to a customer when a new support ticket is created, or automatically dial a list of contacts for a marketing campaign.

Properties

Name Meaning
Contact The identifier or phone number of the contact to be called.
Destination The target phone number or endpoint where the call should be directed.
Dn The direct number (DN) from which the call will be made, representing the caller ID.
Test Call A boolean flag indicating whether this is a test call (true) or a real call (false).

Output

The node outputs JSON data representing the result of the call initiation request to the 3CX system. This typically includes details such as call status, identifiers, and any error messages if the call could not be placed. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating with the 3CX telephony system.
  • Needs the base URL of the 3CX server configured in the credentials.
  • The node sends requests to the 3CX API endpoint /xapi/v1.

Troubleshooting

  • Common issues:

    • Incorrect or missing API credentials can cause authentication failures.
    • Invalid phone numbers or destination endpoints may result in call initiation errors.
    • Network connectivity problems between n8n and the 3CX server can prevent successful calls.

  • Error messages:

    • Authentication errors usually indicate invalid or expired API tokens; reconfigure credentials.
    • Validation errors on input properties suggest incorrect phone number formats or missing required fields.
    • Server errors might require checking the 3CX server status or logs.

Links and References

(Note: URLs are provided as general references; verify with your specific 3CX version.)

Discussion