STEM Connect icon

STEM Connect

Manage telecommunications operations with STEM Connect API

Actions30

ISP → Update

AI-generated

Overview

The node integrates with the STEM Connect API to manage telecommunications-related data and operations. Specifically, for the ISP resource with the Update operation, it updates existing Internet Service Provider (ISP) records in the STEM Connect system. This is useful when you need to modify ISP details such as the name or alias after they have been created.

Practical examples include:

  • Correcting or changing the name of an ISP.
  • Updating the alias used internally or externally to refer to an ISP.
  • Automating ISP record maintenance as part of a larger workflow managing network resources.

Properties

Name Meaning
Subsystem Selects which subsystem's API endpoints to use: Main, Portal, or API
ISP ID The unique numeric identifier of the ISP to update
ISP Name The new or updated name of the ISP
ISP Alias The new or updated alias for the ISP

Output

The output is an array of JSON objects representing the response from the STEM Connect API after updating the ISP. Each object corresponds to an updated ISP record or contains messages/errors related to the update operation.

The json field typically includes the updated ISP data returned by the API. There is no binary data output for this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the STEM Connect API.
  • The node uses HTTP methods (GET, POST, PATCH, DELETE) to interact with various STEM Connect API endpoints.
  • No additional external dependencies beyond the configured STEM Connect API credentials.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent ISP ID will likely result in an error from the API indicating the ISP was not found.
    • Omitting required fields like ISP ID may cause the request to fail.
    • Network or authentication errors if the API key is missing, expired, or incorrect.

  • Error messages:

    • Errors returned from the API are passed through; typical messages might include "ISP not found" or "Invalid parameters".
    • If the node is set to continue on failure, errors will be included in the output JSON under an error property.

  • Resolution tips:

    • Verify that the ISP ID exists before attempting an update.
    • Ensure the API key credential is correctly configured and has sufficient permissions.
    • Validate input parameters to avoid sending empty or malformed data.

Links and References

Discussion