Overview
The Webbing node for n8n allows you to interact with the Webbing API, specifically targeting device management operations. For the "Devices" resource and the "Suspend" operation, this node enables you to suspend a service device by providing various identifiers (such as Service Device ID, IMEI, SSID, ICCID, or EID). This is useful in scenarios where you need to remotely disable or pause connectivity for a device, such as when a device is lost, stolen, or no longer in use.
Practical examples:
- Suspending a SIM card or eSIM in case of theft.
- Temporarily disabling a device's network access during maintenance.
- Automating device suspension workflows based on business rules.
Properties
| Name | Type | Meaning |
|---|---|---|
| Service Device Identifier | Collection | A group of possible identifiers to specify the target device. Includes: |
| - Service Device ID (string): Unique identifier for the service device. | ||
| - IMEI (string): International Mobile Equipment Identity. | ||
| - SSID (string): Subscriber Service Identifier. | ||
| - ICCID (string): Integrated Circuit Card Identifier. | ||
| - EID (string): Embedded Universal Integrated Circuit Card Identifier. | ||
| Simplify Output | Boolean | Whether to simplify the output data structure for easier downstream processing. |
Output
- The node outputs a
jsonfield containing the response from the Webbing API after attempting to suspend the specified device. - If "Simplify Output" is enabled, the output will be a simplified version of the API response, making it easier to use in subsequent nodes.
- The exact structure of the output depends on the Webbing API's response for the suspend operation, but typically includes status information and possibly details about the suspended device.
Dependencies
- External Service: Requires access to the Webbing API.
- API Credentials: You must configure valid Webbing API credentials in n8n under the name
webbingApi. - n8n Configuration: No additional environment variables are required beyond standard credential setup.
Troubleshooting
Common Issues:
- Invalid or Missing Identifiers: If none of the device identifiers are provided or if they are incorrect, the API may return an error indicating that the device could not be found.
- Authentication Errors: If the
webbingApicredentials are missing or invalid, you may receive authentication or authorization errors. - API Connectivity Issues: Network problems or incorrect API endpoint configuration can result in connection errors.
Common Error Messages:
"Device not found": Ensure at least one correct identifier (Service Device ID, IMEI, etc.) is provided."Unauthorized"or"Invalid credentials": Check your Webbing API credentials in n8n."Network error": Verify network connectivity and API endpoint accessibility.
Links and References
- Webbing Official Website
- n8n Documentation: Custom Nodes
- Contact your Webbing account representative for API documentation and support.