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 set the monitor status of a user entity within 3CX. It is useful in scenarios where you want to programmatically update or control the monitoring state of users in your telephony environment, such as enabling or disabling call monitoring for specific agents or users based on workflow conditions.

For example, you might use this node to automatically disable monitoring for a user during their break time or enable it when they start a shift, helping manage call center operations dynamically.

Properties

Name Meaning
Id The unique identifier of the user entity whose monitor status you want to set. You can provide this as a number or use an expression like {{$json.Id}} to dynamically reference it from previous node data.
Days Number of days related to the monitor status setting. This numeric value is sent in the request body and likely controls how long the monitor status should be applied or retained.

Output

The node outputs JSON data representing the response from the 3CX API after attempting to set the monitor status. This typically includes confirmation of the operation's success or failure and any relevant details returned by the API.

No binary data output is indicated.

Dependencies

  • Requires an active connection to a 3CX telephony system.
  • Needs an OAuth2 API credential configured in n8n to authenticate requests against the 3CX API.
  • The base URL for the 3CX server must be provided in the credentials configuration.

Troubleshooting

  • Invalid or missing user Id: Ensure that the Id property is correctly set and corresponds to a valid user in the 3CX system.
  • Authentication errors: Verify that the OAuth2 credentials are correctly configured and have not expired.
  • API endpoint issues: Confirm that the 3CX server URL is correct and accessible from the n8n instance.
  • Incorrect 'Days' value: Make sure the Days property is a non-negative integer; invalid values may cause the API to reject the request.

Common error messages will generally relate to authentication failures, invalid parameters, or connectivity issues. Checking the node's execution logs and the 3CX API documentation can help resolve these.

Links and References

(Note: The above links are general references; consult your 3CX version-specific API docs for precise details.)

Discussion