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 multiple resources, including Mobile SIMs. Specifically, the "Get" operation for the Mobile SIM resource retrieves detailed information about a single Mobile SIM by its unique identifier. This is useful in scenarios where you need to fetch current data or status of a specific SIM card managed within TeleFlow, such as checking its configuration, usage, or associated metadata.
Practical examples include:
- Retrieving details of a Mobile SIM before performing updates or audits.
- Fetching SIM information to display in dashboards or reports.
- Validating SIM existence and properties during automated workflows.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Mobile SIM resource to retrieve. This is required. |
| Fields | Optional key-value pairs specifying additional fields to include in the request query. You can add multiple field name and value pairs to filter or customize the returned data. |
Output
The output is a JSON object representing the Mobile SIM resource retrieved from the TeleFlow API. It contains all the properties and metadata of the specified Mobile SIM as returned by the API. The exact structure depends on the API response but typically includes identifiers, status, configuration details, and related attributes.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the TeleFlow API via an API key credential configured in n8n.
- The base URL for the API is taken from the credential configuration.
- The node sends HTTP requests with JSON content type and expects JSON responses.
Troubleshooting
- Missing ID error: If the "ID" property is not provided, the node will throw an error stating that the ID is required for the get operation. Ensure the ID is correctly set.
- API connectivity issues: Network errors or invalid credentials will cause HTTP request failures. Verify API keys and network access.
- Invalid field names: Providing incorrect or unsupported field names in the "Fields" collection may result in incomplete or empty responses.
- Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output JSON.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n HTTP Request Node documentation for understanding request options: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/