Actions14
- Call Actions
- Dial Plan Actions
- Domain Actions
- Phone Number Actions
- Queue Actions
- User Actions
Overview
This node integrates with the Level365 API to retrieve information related to telephony resources. Specifically, the "Get Queue Info" operation under the "Queue" resource fetches details about a particular call queue identified by its extension number within a specified domain.
Use cases include:
- Monitoring or managing call queues in a Level365 telephony system.
- Retrieving queue configuration or status for reporting or automation workflows.
- Integrating queue data into CRM or helpdesk systems to enhance customer support operations.
For example, a user might use this node to get real-time information about a support queue to dynamically adjust routing or notify agents.
Properties
| Name | Meaning |
|---|---|
| Domain | The domain of your Level365 account. You can enter your domain name directly; using ~ will auto-replace it with your default domain. This identifies the account context for the API request. |
| Queue Number | The extension number of the queue you want to retrieve information about. This is required to specify which queue's info to fetch. |
Note: There is also a notice property informing that this node is for Level365 clients only and requires an active subscription.
Output
The node outputs JSON data containing detailed information about the specified queue. This typically includes properties such as queue settings, status, members, and other metadata returned by the Level365 API for that queue.
No binary data output is indicated for this operation.
Dependencies
- Requires an active Level365 subscription and valid API credentials (an API key or token) configured in n8n.
- The node makes HTTP requests to the Level365 API endpoint at
https://api.365sip.com/ns-api/v2. - Proper domain and queue extension inputs are necessary for successful API calls.
Troubleshooting
- Invalid Domain or Queue Number: If the domain or queue extension is incorrect or does not exist, the API may return errors or empty results. Verify these inputs carefully.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key/token is correctly set up in n8n credentials.
- Subscription Required: Since this node requires an active Level365 subscription, users without one will not be able to retrieve data.
- Network Issues: Connectivity problems to the Level365 API endpoint can cause timeouts or request failures.
Common error messages likely relate to authorization failures, resource not found, or malformed requests. Checking input values and credential validity usually resolves these issues.
Links and References
- Level365 Official Website
- Level365 API documentation (not provided here but recommended to consult for detailed API response structures and additional capabilities).