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 update entries in a blocklist. The "Update Blocklist Addr" operation modifies details of an existing blocklist entry identified by its ID. This is useful for managing IP addresses or entities that should be blocked or allowed within the telephony environment, such as preventing spam calls or allowing trusted sources.

Practical examples include:

  • Updating the reason or description for blocking a specific IP address.
  • Changing the block type from "Block" to "Allow" for a previously blocked address.
  • Setting or updating expiration dates for temporary blocks.
  • Specifying who added the block (e.g., manually, automatically, or via other systems).

Properties

Name Meaning
Id The unique identifier of the blocklist entry to update. Can be set dynamically via expressions.
Added By Specifies who added the blocklist entry. Options: Manual, Mcu, Webmeeting, Auto Blacklist, Whitelist.
Block Type Defines whether the entry is to block or allow traffic. Options: Block, Allow.
Description A textual description or note about the blocklist entry.
Expires At Expiration date/time for the blocklist entry, after which it may no longer apply.
IP Addr Mask The IP address or mask associated with the blocklist entry.

Output

The node outputs JSON data representing the updated blocklist entry as returned by the 3CX API. This typically includes confirmation of the updated fields and the current state of the blocklist entry. No binary data output is indicated.

Dependencies

  • Requires an active connection to a 3CX telephony system.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The base URL for the 3CX API must be provided in the credentials configuration.
  • The node sends HTTP requests to the 3CX API endpoint /xapi/v1.

Troubleshooting

  • Invalid ID: If the provided blocklist entry ID does not exist, the API will likely return an error. Ensure the ID is correct and exists in the system.
  • Authentication errors: Missing or invalid API credentials will cause authorization failures. Verify that the API key/token is correctly configured.
  • Invalid property values: Providing unsupported values for properties like "Added By" or "Block Type" may result in request rejection. Use only the specified options.
  • Expired or malformed date: The "Expires At" field should be in a valid date-time format; otherwise, the API might reject the update.
  • Network issues: Connectivity problems between n8n and the 3CX server can cause timeouts or failed requests.

Links and References

Discussion