STEM Connect icon

STEM Connect

Manage telecommunications operations with STEM Connect API

Actions30

Device → Create

AI-generated

Overview

This node integrates with the STEM Connect API to manage telecommunications operations. Specifically, for the Device resource and Create operation, it allows users to create new network device records in the STEM Connect system. This is useful for telecom operators or IT administrators who need to automate device provisioning and management workflows.

Typical use cases include:

  • Automatically registering newly deployed network devices by providing their MAC address and status flags.
  • Integrating device creation into larger automation flows that manage network infrastructure.
  • Ensuring consistent device metadata (configured, available, billed, notified) is set upon creation.

Properties

Name Meaning
Subsystem Selects which subsystem API endpoints to use: Main, Portal, or API.
MAC Address The MAC address of the device to be created.
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 creating the device. This typically includes details about the newly created device record such as its identifiers and status fields.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "mac_address": "00:11:22:33:44:55",
  "configured": true,
  "available": false,
  "billed": false,
  "notified": false,
  "id": "device-id-generated-by-api"
}

Dependencies

  • Requires an API key credential for authenticating with the STEM Connect API.
  • The node uses HTTP requests to the STEM Connect REST API endpoints.
  • Proper configuration of the subsystem parameter is necessary to target the correct API endpoint group.

Troubleshooting

  • Common issues:

    • Missing or invalid API credentials will cause authentication failures.
    • Providing incomplete or invalid device data (e.g., malformed MAC address) may result in API errors.
    • Selecting the wrong subsystem may lead to unexpected endpoint errors.

  • Error messages:

    • Authentication errors usually indicate problems with the API key or permissions.
    • Validation errors from the API will specify missing or incorrect fields; ensure all required properties are correctly set.
    • Network or connectivity errors suggest checking the n8n server's internet access and API availability.

Links and References

Discussion