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 perform various operations on different resources. Specifically, for the "Provision" resource and the "Get Many" operation, it retrieves multiple provision records from the TeleFlow system. This is useful when you want to fetch a list of provisions with optional filtering based on specific fields.
Common scenarios include:
- Retrieving all provision entries to display or process them in bulk.
- Filtering provisions by certain attributes (e.g., name, status) to narrow down results.
- Integrating TeleFlow provisioning data into workflows for reporting or automation.
Example: Fetching all provisions where the "status" field equals "active" to process only active provisions downstream.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs used to filter the request. You can specify multiple fields to refine the query. For example, setting name to "example" will filter provisions with that name. |
The "Fields" property allows adding multiple filters as key-value pairs to customize which provisions are returned.
Output
The output is an array of JSON objects representing the provision records retrieved from the TeleFlow API. Each object corresponds to a provision entry with its associated properties as returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token credential configured in n8n to access the TeleFlow API.
- The base URL for the TeleFlow API must be set in the credentials.
- The node uses HTTP requests to communicate with the TeleFlow REST API endpoints.
Troubleshooting
- Missing or invalid API credentials: Ensure the API key/token and base URL are correctly configured in the node's credentials.
- Empty or unexpected results: Verify that the field filters are correct and match existing provision data.
- Error messages about missing IDs: These do not apply to the "Get Many" operation but may appear if other operations are selected incorrectly.
- Network or connectivity issues: Confirm that the TeleFlow API endpoint is reachable from the n8n environment.
If the node throws errors related to HTTP requests, check the API response for details and ensure proper permissions and valid parameters.
Links and References
- TeleFlow API Documentation (replace with actual URL)
- n8n HTTP Request Node Documentation