Actions14
- Call Actions
- Dial Plan Actions
- Domain Actions
- Phone Number Actions
- Queue Actions
- User Actions
Overview
The node integrates with the Level365 API to retrieve data related to various telephony resources. Specifically, for the "Queue" resource and the "Get All Queues" operation, it fetches a list of all call queues configured in a Level365 account domain. This is useful for users who want to automate or monitor their call queue configurations, such as retrieving queue details for reporting, analytics, or further processing within an n8n workflow.
Practical examples include:
- Automatically fetching all call queues to synchronize with a CRM or helpdesk system.
- Generating reports on queue statuses or configurations.
- Triggering workflows based on queue data changes.
Properties
| Name | Meaning |
|---|---|
| Domain | The domain of your Level365 account. You can enter your domain name directly or use ~ as a placeholder that will be replaced with your actual domain. This property is required to specify which account's queues to retrieve. |
Note: There is also a notice property informing users that this node is for Level365 clients only and requires an active subscription.
Output
The node outputs JSON data representing the list of all queues retrieved from the specified Level365 domain. Each item in the output corresponds to a queue object containing its properties as returned by the Level365 API.
If the node supports binary data output (not indicated here), it would typically represent attachments or media related to queues, but this node primarily outputs JSON data about queues.
Dependencies
- Requires an active Level365 subscription.
- Needs an API key credential for authenticating requests to the Level365 API.
- The node makes HTTP requests to the Level365 API endpoint at
https://api.365sip.com/ns-api/v2. - The user must provide the correct domain associated with their Level365 account.
Troubleshooting
Common issues:
- Invalid or missing domain value: Ensure the domain property is correctly set; using
~will automatically replace it with the user's domain. - Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network or API downtime: Check connectivity and Level365 service status.
- Invalid or missing domain value: Ensure the domain property is correctly set; using
Error messages:
- Unauthorized or 401 errors indicate invalid credentials.
- 404 errors may occur if the domain does not exist or is incorrect.
- Rate limiting or quota exceeded errors require checking subscription limits.
Resolving these usually involves verifying credentials, domain correctness, and subscription status.
Links and References
- Level365 Official Website
- Level365 API documentation (not provided in source, but typically available via Level365 support or developer portal)