Actions82
- 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
Overview
The node interacts with the TeleFlow API to perform various operations on different resources, including Mobile SIMs. Specifically, for the Mobile SIM - Update operation, it updates an existing Mobile SIM resource by its unique ID with specified fields.
This node is beneficial when you need to programmatically manage and update telecommunication-related resources such as SIM cards within automated workflows. For example, you might update a Mobile SIM's attributes like its name or other custom fields dynamically based on external triggers or data changes.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Mobile SIM resource to update. This is required. |
| Fields | A collection of field-value pairs specifying which fields of the Mobile SIM to update. You can add multiple fields, each with a name and corresponding value. |
Output
- The output is a JSON object representing the updated Mobile SIM resource as returned by the TeleFlow API.
- The structure of this JSON depends on the API response but typically includes the Mobile SIM's properties after the update.
- No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the TeleFlow API.
- The base URL for the API must be configured in the node credentials.
- The node uses HTTP requests (GET, POST, PUT, DELETE) to interact with the TeleFlow REST API endpoints.
Troubleshooting
- Missing ID Error: If the "ID" property is not provided for the update operation, the node will throw an error stating that the ID is required. Ensure the ID is correctly set.
- API Request Failures: Network issues, invalid credentials, or incorrect field names may cause HTTP request failures. Check API credentials and field names carefully.
- Field Validation: Providing invalid or unsupported field names/values in the "Fields" collection may result in API errors. Verify field names against 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/
- n8n Custom Node Development Guide: https://docs.n8n.io/integrations/creating-nodes/