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 manage various resources, including Tenants. Specifically, the "Get Many" operation for the Tenant resource retrieves multiple tenant records from the TeleFlow system. This is useful when you want to list tenants or filter tenants based on specific criteria.
Common scenarios include:
- Fetching a list of all tenants in your TeleFlow account.
- Querying tenants that match certain field values (e.g., name or other attributes).
- Integrating tenant data into workflows for reporting, auditing, or synchronization purposes.
Example: You might use this node to get all tenants whose name contains a particular string or meet other custom field criteria, then process or export that data downstream.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs used to filter or specify which tenant fields to include in the request. You can add multiple fields to refine the query. For example, filtering tenants by name or other attributes. |
The "Fields" property allows adding multiple entries, each specifying:
- Field: The name of the tenant attribute to filter by.
- Value: The value to match for that field.
Output
The output is an array of JSON objects representing tenant records retrieved from the TeleFlow API. Each object corresponds to a tenant and includes the fields returned by the API according to the specified filters.
No binary data is output by this node.
Example output structure (simplified):
[
{
"id": "tenant-id-1",
"name": "Tenant One",
"otherField": "value"
},
{
"id": "tenant-id-2",
"name": "Tenant Two",
"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 ID error: Although not applicable for "Get Many", other operations require an ID parameter. Ensure IDs are provided where necessary.
- API authentication errors: Verify that the API key and base URL are correctly set in the credentials.
- Empty results: If no tenants are returned, check the filter fields for correctness; incorrect field names or values may yield no matches.
- Network issues: Ensure the TeleFlow API endpoint is reachable from your n8n instance.
Links and References
- TeleFlow API Documentation (replace with actual URL)
- n8n HTTP Request Node documentation for understanding underlying HTTP calls: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/