STEM Connect icon

STEM Connect

Manage telecommunications operations with STEM Connect API

Actions30

Device → Add

AI-generated

Overview

This node integrates with the STEM Connect API to manage telecommunications operations. Specifically, for the Device resource and the Add operation, it allows users to add a new network device by providing details such as MAC address and various status flags (configured, available, billed, notified). This is useful in scenarios where telecom operators or network administrators need to programmatically register new devices into their management system.

Practical examples include:

  • Automatically adding newly provisioned network devices into the STEM Connect system.
  • Integrating device onboarding workflows with other automation processes.
  • Setting initial device statuses during creation to reflect current operational states.

Properties

Name Meaning
Subsystem Selects the subsystem of the STEM Connect API to use. Options: Main, Portal, API
MAC Address The MAC address of the device to add
Configured Boolean flag indicating if the device is configured
Available Boolean flag indicating if the device is currently available
Billed Boolean flag indicating if the device has been billed
Notified Boolean flag indicating if notifications related to the device have been sent

Output

The node outputs JSON data representing the response from the STEM Connect API after attempting to add the device. The structure depends on the API's response but typically includes details about the newly added device or an error message if the operation failed.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the STEM Connect API.
  • The node uses HTTP requests to communicate with the STEM Connect endpoints.
  • No additional external services are required beyond the STEM Connect API itself.

Troubleshooting

  • Common issues:

    • Missing or invalid API credentials will cause authentication failures.
    • Providing incomplete or incorrectly formatted device data (e.g., invalid MAC address) may result in API errors.
    • Network connectivity issues can prevent successful API calls.

  • Error messages:

    • Errors returned from the API will be included in the node output under an error field if "Continue On Fail" is enabled.
    • Typical error messages might relate to validation failures or unauthorized access.

  • Resolution tips:

    • Verify that the API key credential is correctly configured and has necessary permissions.
    • Ensure all required fields are provided and correctly formatted.
    • Check network connectivity and endpoint URLs.

Links and References

Discussion