Actions221
- ACL Group Actions
- Alarm Clock Actions
- Application Actions
- Broadcast Actions
- Call Actions
- Call History Actions
- Call Queue Actions
- Colleague Actions
- Contact Actions
- Department Actions
- Device Actions
- Dialplan Actions
- Add DB Value
- Create Dialplan
- Create IVR
- Create Paging Group
- Create Switch
- Create Time Table
- Delete DB Family
- Delete DB Key
- Delete Dialplan
- Delete IVR
- Delete Paging Group
- Delete Switch
- Delete Time Table
- Get DB Family Keys
- Get DB Value
- Get Dialplan
- Get Dialplans
- Get General Settings
- Get IVR
- Get Paging Groups
- Get Switches
- Get Time Tables
- Import Time Tables
- Update DB Value
- Update Dialplan
- Update General Settings
- Update IVR
- Update Paging Group
- Update Switch
- Update Time Table
- Fax Actions
- Group Actions
- Notification Actions
- OAuth2 Client Actions
- PBX Actions
- PBX Setting Actions
- PBX System Actions
- PBX Upgrade Actions
- Personal Actions
- Phonebook Actions
- Recording Actions
- SIP Registration Actions
- SMS Actions
- Sound Actions
- Trunk Actions
- Create FXO Trunk
- Create PSTN Trunk
- Create SIP Trunk
- Create Trunk Group
- Create Trunk Price List
- Delete FXO Trunk
- Delete PSTN Trunk
- Delete SIP Trunk
- Delete Trunk Group
- Delete Trunk Price List
- Export Trunk Price List
- Get FXO Trunks
- Get PSTN Trunks
- Get SIP Trunks
- Get Trunk Groups
- Get Trunk Prices
- Update FXO Trunk
- Update PSTN Trunk
- Update SIP Trunk
- Update Trunk Group
- Update Trunk Price List
- Trusted IP Actions
- Video Conference Actions
- Voicemail Actions
Trunk → Create SIP Trunk
AI-generatedSummary
Creates a new SIP trunk on a Wildix PBX with a required title and optional auth login and register string.
Inputs
- Authentication — Credential type used for the request: Bearer Token (default) or OAuth2.
- Title (required) — Title of the SIP trunk.
- Additional Fields — Optional collection. Name (Auth Login) sets the trunk's auth login; Register String sets the SIP register string.
Output shape
Not verifiable from the source. The pack contains only stubs, so the response body is not visible. Expect the Wildix API's response for the created trunk, returned as n8n items.
The execute implementation and the API endpoint are not visible in the provided source. Details such as the exact request body mapping and the return shape are inferred from the declared properties only.
Examples
Example 1: Create a basic SIP trunk with just a title.
Resource: Trunk, Operation: Create SIP Trunk, Title: 'Provider A'.
Example 2: Create a trunk that registers with a provider.
Title: 'Provider B'; Additional Fields: Name (Auth Login) = 'user123', Register String = the provider's SIP register string.