Actions462
- Active Calls Actions
- Activity Log Actions
- Anti Hacking Settings Actions
- Backups Actions
- Black List Numbers Actions
- Blocklist Actions
- Call Cost Settings Actions
- Call Flow Apps Actions
- Call Flow Scripts Actions
- Call History View Actions
- Call Parking Settings Actions
- Call Types Settings Actions
- CDR Settings Actions
- Chat History View Actions
- Chat Log Settings Actions
- Chat Messages History View Actions
- Codecs Settings Actions
- Conference Settings Actions
- Console Restrictions Actions
- Contacts Actions
- Countries Actions
- Country Codes Actions
- CRM Integration Actions
- Crm Templates Actions
- Custom Prompts Actions
- Data Connector Settings Actions
- Defs Actions
- Device Infos Actions
- Dial Code Settings Actions
- Did Numbers Actions
- DN Properties Actions
- E 164 Settings Actions
- Email Template Actions
- Emergency Geo Locations Actions
- Emergency Notifications Settings Actions
- Event Logs Actions
- Fax Actions
- Fax Server Settings Actions
- Firewall Actions
- Firmwares Actions
- Fxs Actions
- Fxs Templates Actions
- General Settings For Apps Actions
- General Settings For Pbx Actions
- Google Settings Actions
- Groups Actions
- Holidays Actions
- Hotel Services Actions
- Inbound Rules Actions
- Last Cdr And Chat Message Timestamp Actions
- License Status Actions
- Logging Settings Actions
- Microsoft 365 Integration Actions
- Microsoft 365 Teams Integration Actions
- Music On Hold Settings Actions
- My Group Actions
- My Tokens Actions
- My User Actions
- Network Interfaces Actions
- Network Settings Actions
- Notification Settings Actions
- Office Hours Actions
- Outbound Rules Actions
- Parameters Actions
- Parkings Actions
- Peers Actions
- Phone Book Settings Actions
- Phone Logos Actions
- Phones Settings Actions
- Phone Templates Actions
- Playlists Actions
- Prompt Sets Actions
- Purge Settings Actions
- Queues Actions
- Receptionists Actions
- Recordings Actions
- System Status Actions
- Remote Archiving Settings Actions
- Report Abandoned Chats Statistics Actions
- Report Abandoned Queue Calls Actions
- Report Agent Login History Actions
- Report Agents In Queue Statistics Actions
- Report Audit Log Actions
- Report Average Queue Waiting Time Actions
- Report Breaches Sla Actions
- Report Call Cost By Extension Group Actions
- Report Call Distribution Actions
- Report Call Log Data Actions
- Report Detailed Queue Statistics Actions
- Report Extensions Statistics By Ring Groups Actions
- Report Extension Statistics By Group Actions
- Report Extension Statistics Actions
- Report Inbound Rules Actions
- Report Queue Agents Chat Statistics Actions
- Report Queue Agents Chat Statistics Totals Actions
- Report Queue Answered Calls By Wait Time Actions
- Report Queue An Un Calls Actions
- Report Queue Callbacks Actions
- Report Queue Chat Performance Actions
- Report Queue Failed Callbacks Actions
- Report Queue Performance Overview Actions
- Report Queue Performance Totals Actions
- Report Ring Group Statistics Actions
- Report Statistic Sla Actions
- Report Team Queue General Statistics Actions
- Scheduled Reports Actions
- Ring Groups Actions
- Sbcs Actions
- Secure Sip Settings Actions
- Security Tokens Actions
- Service Principals Actions
- Services Actions
- Sip Devices Actions
- Directories Actions
- Tenant Properties Actions
- Trunks Actions
- Trunk Templates Actions
- Updates Actions
- Users Actions
- Has Duplicated Email
- Get Duplicated Emails
- Send Welcome Email
- List Groups
- List Forwarding Profiles
- Get Phone Secret
- Regenerate
- Regenerate Passwords
- Export Extensions
- Get Phone Registrar
- Bulk Update
- Get Phone Registrars
- Reboot Phone
- Reprovision Phone
- Upgrade Phone
- Generate Prov Link
- Get User
- Update User
- Delete User
- List Greetings
- Make Call User Record Greeting
- Download Greeting
- Batch Delete
- Get Call Log
- Make Call
- Get Monitor Status
- Set Monitor Status
- Multi User Update
- Reprovision All Phones
- Get Multi Edit Greetings
- Multi Delete Greeting
- Get User By Number
- List User
- Create User
- Voicemail Settings Actions
- Website Links Actions
- Report Inbound Calls Actions
- Report Outbound Calls Actions
- Report User Activity Actions
Peers → Retreive Peers By Numbers
AI-generatedOverview
This node interacts with the 3CX telephony system, specifically allowing users to retrieve information about peers by their numbers. It is useful in scenarios where you need to query details of specific telephony peers (extensions or devices) within a 3CX system based on their direct number identifiers. For example, a user might want to fetch status or configuration details of certain extensions programmatically.
Properties
| Name | Meaning |
|---|---|
| Peers Request | JSON object containing an array DnNumbers with the list of direct numbers to retrieve peers for. Example: { "DnNumbers": [1234, 5678] } |
Output
The node outputs JSON data representing the peers corresponding to the requested direct numbers. The exact structure depends on the 3CX API response but typically includes peer details such as extension number, status, and other relevant telephony information.
If the node supports binary data output, it would be related to any media or files associated with peers, but this is not indicated in the provided code.
Dependencies
- Requires an API key credential for authenticating with the 3CX system.
- Needs the base URL of the 3CX server configured in credentials.
- The node sends requests to the 3CX API endpoint
/xapi/v1. - The request headers specify
Accept: application/json.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect or unreachable 3CX server URL will result in connection errors.
- Malformed JSON in the
Peers Requestproperty can cause request parsing errors. - Requesting non-existent direct numbers may return empty results or errors from the API.
Error messages:
- Authentication errors usually indicate invalid or expired API tokens; re-authenticate or update credentials.
- Network errors suggest checking the server URL and network connectivity.
- JSON parsing errors require validating the input JSON format in the
Peers Requestfield.
Links and References
- 3CX API Documentation
- n8n HTTP Request Node Documentation (for understanding how API calls are made)