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, including Resellers. Specifically, the Get operation for the Reseller resource retrieves detailed information about a single reseller by its unique ID. This is useful when you need to fetch specific reseller data for reporting, auditing, or integration purposes.
Practical examples include:
- Retrieving reseller details to display in a dashboard.
- Fetching reseller information before updating or deleting it.
- Using reseller data as part of a workflow that manages billing or user assignments.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the reseller to retrieve. This is required for the Get operation. |
| Fields | Optional key-value pairs to specify additional fields or filters to include in the request. |
The Fields property allows adding multiple field-value pairs to customize the query parameters sent with the GET request. For example, you could specify certain attributes to filter or limit the returned data.
Output
The output is an array of JSON objects where each object corresponds to the retrieved reseller data from the TeleFlow API. The structure of the JSON depends on the API response but generally includes all available properties of the reseller identified by the given ID.
No binary data output is produced by this operation.
Example output snippet (conceptual):
{
"id": "12345",
"name": "Reseller Name",
"status": "active",
"createdAt": "2023-01-01T12:00:00Z",
...
}
Dependencies
- Requires an API authentication credential configured in n8n to access the TeleFlow API.
- The base URL for the API must be set in the credentials configuration.
- The node uses HTTP requests with JSON content type and expects JSON responses.
Troubleshooting
- Missing ID error: If the ID property is not provided for the Get operation, the node will throw an error stating that the ID is required. Ensure the ID input is correctly set.
- API connection issues: Errors related to network connectivity or invalid credentials may occur. Verify the API key/token and base URL are correct and that the TeleFlow API is reachable.
- Invalid fields: Providing unsupported or incorrect field names in the Fields property may result in API errors or empty responses. Double-check field names against the TeleFlow API documentation.
- Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.
Links and References
- TeleFlow API Documentation (replace with actual URL)
- n8n HTTP Request Node Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/