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 integrates with the TeleFlow API to perform various operations on different resources, including users. Specifically, the "User" resource with the "Get Many" operation allows you to retrieve multiple user records from TeleFlow. You can filter the results by specifying fields and their values, enabling more targeted queries.
Common scenarios include:
- Fetching a list of users matching certain criteria for reporting or synchronization.
- Retrieving user data in bulk to update another system or dashboard.
- Filtering users based on custom field-value pairs to narrow down the dataset.
For example, you might want to get all users with a specific role or status by adding those as fields in the query.
Properties
| Name | Meaning |
|---|---|
| Fields | Field-value pairs to filter the users returned by the request. You can add multiple pairs. For each pair: - Name: The field name to filter by (e.g., "role", "status"). - Value: The value that the field should match. |
Output
The output is an array of JSON objects representing the users retrieved from the TeleFlow API. Each object contains the user data fields as returned by the API, filtered according to the specified fields if any.
No binary data is output by this node.
Example output structure (simplified):
[
{
"id": "123",
"username": "jdoe",
"email": "jdoe@example.com",
"role": "admin",
...
},
{
"id": "124",
"username": "asmith",
"email": "asmith@example.com",
"role": "user",
...
}
]
Dependencies
- Requires an API key credential for authenticating with the TeleFlow API.
- The base URL for the TeleFlow API must be configured in the 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's credentials.
- Invalid field names or values: If filtering fields do not match the API's expected parameters, the request may return no results or errors.
- ID required errors: Although not applicable for "Get Many," other operations require an ID parameter; ensure it is provided when using those.
- API connectivity issues: Network problems or incorrect base URL will cause request failures.
- Error messages from the API: These are passed through; check the error message details for guidance.
If the node encounters an error and "Continue On Fail" is enabled, it will output an error object instead of stopping execution.
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/