3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

The node interacts with the 3CX telephony system, specifically allowing retrieval of a single Fxs Template entity by its unique identifier. This operation is useful when you need to fetch detailed configuration or metadata about a specific Fxs Template within the 3CX system, such as for automation workflows that manage telephony device templates or configurations.

A practical example would be an automation that, given an ID from a previous step (e.g., a list of templates), fetches the full details of that template to use in further processing or decision-making.

Properties

Name Meaning
Id The unique identifier of the Fxs Template entity to retrieve. Supports expressions like {{$json.Id}}. This property is required.
Options Additional query options to customize the data returned:
- Select ($select) Comma-separated list of properties to return for the Fxs Template (e.g., Id,Name).
- Expand ($expand) Comma-separated list of related entities to expand and include in the response.

Output

The node outputs JSON data representing the requested Fxs Template entity. The structure corresponds to the properties of the Fxs Template as defined in the 3CX API, potentially including expanded related entities if specified.

If binary data were involved (not indicated here), it would typically represent files or media associated with the template, but this node focuses on JSON entity data only.

Dependencies

  • Requires an active connection to a 3CX telephony system.
  • Needs an API authentication token credential configured in n8n to authorize requests.
  • The base URL for the 3CX API must be set in the credentials, ensuring correct endpoint targeting.

Troubleshooting

  • Missing or invalid Id: If the Id property is empty or incorrect, the node will fail to find the template. Ensure the Id is correctly provided and matches an existing Fxs Template.
  • Authentication errors: If the API key or OAuth2 token is missing or expired, the node will return authorization errors. Verify credentials are valid and properly configured.
  • Network or URL issues: Incorrect server URL or network problems can cause request failures. Confirm the base URL is correct and accessible from the n8n environment.
  • Invalid $select or $expand values: Providing invalid property names in these options may result in API errors or incomplete data. Use valid property names as per 3CX API documentation.

Links and References

Discussion