Actions145
- 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
- File Actions
- Flow Actions
- Flow Template Actions
- LCR Actions
- Mobile SIM Actions
- Number Port Actions
- Phone Number Actions
- Provision Actions
- Report Actions
- Reseller Actions
- SIP Trunk Actions
- Tariff Actions
- Tariff Code Actions
- Tariff Profile Actions
- Tenant Actions
- Tenant Audit Actions
- Transcription Actions
- User Actions
- Voice Actions
- Voice Mail Message Actions
Overview
This node integrates with the TeleFlow API to manage phone numbers programmatically. Specifically, the "Phone Number - Create" operation allows users to add new phone numbers to their TeleFlow account. This is useful in scenarios such as provisioning new local or toll-free numbers for a business, automating number management workflows, or integrating TeleFlow phone number creation into larger automation pipelines.
For example, a telecom administrator could use this node to automatically register new phone numbers in bulk, specifying whether each number is local or toll-free, and optionally adding custom metadata fields.
Properties
| Name | Meaning |
|---|---|
| Number | The phone number to create, entered in E.164 format (e.g., +12125551234). |
| Type | The type of phone number to create. Options: Local, Toll Free. |
| Fields | Optional additional field-value pairs to include in the request for more specific data. |
- Number is required and must be provided in international E.164 format.
- Type is required and determines if the number is local or toll-free.
- Fields allow adding arbitrary extra information as key-value pairs, enhancing the request with custom parameters supported by the API.
Output
The node outputs JSON data representing the response from the TeleFlow API after creating the phone number. This typically includes details about the newly created phone number resource, such as its ID, number, type, status, and any other metadata returned by the API.
No binary data output is produced by this operation.
Example output structure (simplified):
{
"id": "string",
"number": "+12125551234",
"type": "local",
"status": "active",
"additionalProperties": { ... }
}
Dependencies
- Requires an API key credential for authenticating with the TeleFlow API.
- The base URL for the TeleFlow API must be configured in the node credentials.
- The node uses HTTP requests to communicate with the TeleFlow REST API endpoints.
Troubleshooting
- Missing Required Parameters: If the "Number" or "Type" properties are not provided, the node will fail. Ensure these are set correctly.
- Invalid Phone Number Format: The phone number must be in E.164 format; otherwise, the API may reject the request.
- API Authentication Errors: Verify that the API key credential is valid and has sufficient permissions.
- Network Issues: Connectivity problems to the TeleFlow API endpoint can cause failures.
- Error Messages: The node throws errors with messages from the API or internal validation. Common errors include missing IDs for operations other than create, invalid parameter values, or permission denied.
To resolve errors:
- Double-check all required inputs.
- Confirm API credentials and endpoint configuration.
- Review error messages logged by the node for specific API response details.
Links and References
- E.164 Phone Number Formatting
- TeleFlow API Documentation (refer to your TeleFlow provider's official API docs for detailed endpoint info)