Actions34
- Customer Actions
- Customer Xdrs Actions
- Customer Extensions Actions
- Account Actions
- Invoice Actions
- DID Numbers Actions
- Billing sessions Actions
- Rate Management Actions
Overview
The PortaOne node for n8n allows you to interact with the PortaOne API, specifically to manage DID (Direct Inward Dialing) numbers. The Assign To Customer operation under the DID Numbers resource assigns a specific DID number to a customer in your PortaOne system.
Common scenarios:
- Automating the assignment of phone numbers to new or existing customers.
- Integrating customer onboarding workflows where each customer is provisioned with a unique DID number.
- Managing telephony resources programmatically as part of larger business processes.
Practical example:
When a new customer signs up on your platform, this node can be used to automatically assign them a DID number from your inventory, ensuring seamless telephony integration.
Properties
| Name | Meaning |
|---|---|
| Authentication | The authentication method to use. Options: Token Authentication, Basic Authentication. |
| Customer ID | The unique ID of the customer record. |
| DID Number ID | The unique ID of the DID number record. |
| Simplify | Whether to simplify the output data. |
| SimplifyPath | Path to the property that should be returned (used when simplifying output). |
Output
- The node outputs a
jsonfield containing the result of the assignment operation. - If Simplify is enabled, only the specified property (via SimplifyPath) or a simplified structure will be returned.
- Otherwise, the full response from the PortaOne API regarding the assignment will be included.
- Binary data: This node does not output binary data; all output is in JSON format.
Dependencies
- External Services: Requires access to the PortaOne API.
- API Credentials: You must provide either a PortaOne Token or Basic Authentication credentials via n8n's credential system.
- n8n Configuration: Ensure the appropriate credentials are set up and selected in the node configuration.
Troubleshooting
Common issues:
- Invalid credentials: If the provided API token or basic auth details are incorrect, authentication will fail.
- Missing required fields: Both Customer ID and DID Number ID are mandatory. Omitting these will result in errors.
- Incorrect SimplifyPath: If you specify a path that doesn't exist in the response, the output may be empty or throw an error.
Error messages and resolutions:
"Authentication failed": Check your API credentials and ensure they have sufficient permissions."Required parameter missing": Make sure both Customer ID and DID Number ID are filled in."Resource not found": Verify that the IDs correspond to existing records in your PortaOne system.