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 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 by specifying the number and its type.
Common scenarios where this node is beneficial include:
- Automating the provisioning of phone numbers in bulk.
- Integrating phone number management into larger workflows, such as setting up new user accounts or devices.
- Dynamically creating phone numbers based on external triggers or data sources.
For example, a telecom company could use this node to automatically register newly purchased phone numbers into their system, specifying whether each number is local or toll-free.
Properties
| Name | Meaning |
|---|---|
| Fields | Additional field-value pairs to include in the request for more specific queries. Users can add multiple custom fields here. |
| Number | The phone number to create, required. Must be entered in E.164 format (e.g., +12125551234). |
| Type | The type of phone number. Options are: Local or Toll Free. |
Output
The output is a JSON object 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 unique identifier, number, type, and any other metadata returned by the API.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the TeleFlow API.
- Needs an API authentication token configured in the node credentials to authorize requests.
- The base URL for the TeleFlow API must be set in the credentials configuration.
Troubleshooting
- Missing Required Fields: If the "Number" property is not provided or is incorrectly formatted, the API will likely reject the request. Ensure the phone number is in E.164 format.
- Authentication Errors: If the API key or credentials are invalid or missing, the node will fail to authenticate. Verify that the API credentials are correctly configured.
- API Request Failures: Network issues or incorrect base URL settings can cause request failures. Confirm the base URL and network connectivity.
- Error Messages: The node throws errors if required parameters like "Number" are missing or if the API returns an error. Enabling "Continue On Fail" allows the workflow to proceed while capturing error messages in the output JSON.
Links and References
- E.164 Phone Number Format
- TeleFlow API documentation (refer to your TeleFlow API provider's official docs for detailed endpoints and request formats)