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 interacts with the TeleFlow API to perform various operations on different resources, including Accounts. Specifically, the "Get Many" operation for the Account resource retrieves multiple account records from TeleFlow based on specified query fields. This is useful when you want to fetch a list of accounts filtered by certain criteria, such as name or other custom fields.
Practical examples include:
- Retrieving all accounts that match specific field values.
- Filtering accounts by custom attributes to integrate with other systems.
- Bulk fetching account data for reporting or synchronization purposes.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs used to filter the accounts returned by the request. You can specify multiple fields to narrow down the query results. For example, filtering by "name" with a specific value. |
Output
The output is an array of JSON objects representing the accounts retrieved from the TeleFlow API. Each object contains the account data fields as returned by the API, matching the requested filters.
No binary data is output by this operation.
Example output structure (simplified):
[
{
"id": "account_id_1",
"name": "Account Name 1",
"otherField": "value"
},
{
"id": "account_id_2",
"name": "Account Name 2",
"otherField": "value"
}
]
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.
Troubleshooting
- Missing or invalid API credentials: Ensure the API key and base URL are correctly set in the node credentials.
- Empty or no results returned: Verify that the field filters are correct and that matching accounts exist in TeleFlow.
- Error messages about missing ID: Not applicable for "Get Many" but relevant for other operations like "Get" or "Update" where an ID is required.
- HTTP errors: Check network connectivity and API endpoint availability.
- If the node throws errors, enabling "Continue On Fail" allows processing subsequent items without stopping the workflow.
Links and References
- TeleFlow API Documentation (replace with actual URL)
- n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/