Actions82
- 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
Overview
The node interacts with the TeleFlow API to perform various operations on different resources. Specifically, for the Feature Code resource with the Get Many operation, it retrieves multiple feature code records from the TeleFlow system. This is useful when you want to fetch a list of feature codes, optionally filtered by specific fields.
Common scenarios include:
- Retrieving all feature codes available in the system.
- Filtering feature codes based on certain attributes (e.g., name or other custom fields).
- Integrating TeleFlow feature codes data into workflows for reporting or further processing.
Example: You might use this node to get all feature codes that match certain criteria and then process them in subsequent workflow steps.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs used to filter the request. You can specify multiple fields to narrow down the query results. For example, you could filter by "name" or any other supported field. |
The "Fields" property allows adding multiple entries, each with:
- Name: The field name to filter by.
- Value: The value to match for that field.
Output
The output is an array of JSON objects representing the feature codes retrieved from the TeleFlow API. Each object corresponds to a feature code record with its properties as returned by the API.
- The
jsonoutput contains the full response data from the API call. - No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the TeleFlow API.
- The base URL for the API must be configured in the node credentials.
- The node uses HTTP requests to communicate with the TeleFlow REST API.
Troubleshooting
- Missing or invalid API credentials: Ensure the API key and base URL are correctly set in the node credentials.
- Invalid field names in filters: Using unsupported or misspelled field names in the "Fields" property may result in empty responses or errors.
- API errors: If the API returns an error, the node will throw an error unless "Continue On Fail" is enabled, in which case the error message will be included in the output JSON.
- Empty results: If no feature codes match the specified filters, the output will be an empty array.
Links and References
- TeleFlow API Documentation (Replace with actual URL if available)
- n8n HTTP Request Node documentation for understanding how HTTP calls are made within n8n workflows.