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. Specifically, for the "Mobile SIM" resource with the "Get Many" operation, it retrieves multiple Mobile SIM records from the TeleFlow system. This is useful when you want to fetch a list of SIM cards managed in your TeleFlow account, optionally filtering the results by specific fields.
Practical examples include:
- Retrieving all Mobile SIMs currently active in your system.
- Filtering Mobile SIMs by certain attributes such as status or assigned user.
- Integrating SIM inventory data into workflows for reporting or automation.
Properties
| Name | Meaning |
|---|---|
| Fields | Field-value pairs to filter the query results. You can add multiple fields to narrow down the returned Mobile SIMs. For example, you might specify a field "status" with value "active" to get only active SIMs. |
The "Fields" property is a fixed collection allowing multiple entries, each consisting of:
- Name: The name of the field to filter by (string).
- Value: The value to match for that field (string).
Output
The output is an array of JSON objects representing the Mobile SIM records retrieved from the TeleFlow API. Each object contains the properties of a Mobile SIM as returned by the API, filtered according to any specified fields.
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 TeleFlow API must be configured in the node credentials.
- The node uses HTTP requests to communicate with the TeleFlow REST API endpoints.
Troubleshooting
- Missing or invalid API credentials: Ensure that the API key and base URL are correctly set in the node 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.
- Network issues: Connectivity problems can cause request failures; verify network access to the TeleFlow API endpoint.
- Error messages about missing IDs: Not applicable for "Get Many" but relevant for other operations like "Get" or "Update" which require an ID parameter.
If the node throws an error related to the HTTP request, check the API response message for details and verify that the query parameters are correct.
Links and References
- TeleFlow API Documentation (Replace with actual URL if available)
- n8n Documentation on HTTP Request Node for understanding how API calls are made within n8n.