Actions145
- User Actions
- Voice Actions
- File Actions
- Flow Actions
- Reseller Actions
- SIP Trunk Actions
- Transcription Actions
- Voice Mail Message Actions
- Account Actions
- Account Audit Actions
- Billing Entry Actions
- Call Detail Record Actions
- Carrier Actions
- Device Actions
- Device Template Actions
- Email Template Actions
- Feature Code Actions
- Flow Template Actions
- LCR Actions
- Mobile SIM Actions
- Number Port Actions
- Phone Number Actions
- Provision Actions
- Report Actions
- Tariff Actions
- Tariff Code Actions
- Tariff Profile Actions
- Tenant Actions
- Tenant Audit Actions
Overview
This node interacts with the TeleFlow API to manage SIP Trunks, specifically allowing users to create new SIP Trunk entries. It is useful in telephony and VoIP management scenarios where automated provisioning or configuration of SIP trunks is required. For example, a telecom administrator can use this node to programmatically add new SIP trunks to their system without manual entry, streamlining deployment and integration workflows.
Properties
| Name | Meaning |
|---|---|
| Name | The unique name assigned to the SIP trunk being created. |
| Host | The hostname or IP address of the SIP trunk. |
| Fields | Additional field-value pairs to include in the request for more specific queries (not used in create operation but available generally). |
Output
The output is a JSON object representing the response from the TeleFlow API after creating the SIP trunk. This typically includes details of the newly created SIP trunk such as its ID, name, host, and any other metadata returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the TeleFlow API.
- Needs an API authentication token configured in the node credentials.
- The base URL for the TeleFlow API must be set in the node's credential configuration.
Troubleshooting
- Missing Required Fields: If "Name" or "Host" is not provided, the node will fail because these are mandatory for creating a SIP trunk.
- API Request Failures: Network issues or invalid API credentials will cause HTTP request errors. Ensure the API key/token and base URL are correctly configured.
- Error Messages: Errors thrown by the node will include messages from the TeleFlow API or internal validation errors. Common messages might indicate missing parameters or unauthorized access.
- To resolve errors, verify all required fields are filled, check API credentials, and ensure network connectivity to the TeleFlow service.
Links and References
- TeleFlow API Documentation (Replace with actual URL if available)
- n8n Documentation on HTTP Request Node for understanding underlying HTTP calls.