STEM Connect icon

STEM Connect

Manage telecommunications operations with STEM Connect API

Actions30

Product → Get

AI-generated

Overview

This node integrates with the STEM Connect API to manage telecommunications-related data and operations. Specifically, for the Product resource with the Get operation, it retrieves a list of products from the STEM Connect system. This is useful in scenarios where you want to fetch product information such as available telecom products or services for further processing, reporting, or automation workflows.

Practical examples include:

  • Automatically syncing product lists from STEM Connect into your CRM or inventory system.
  • Triggering workflows based on product availability or updates.
  • Generating reports or dashboards that include current product offerings.

Properties

Name Meaning
Subsystem Selects which subsystem's API endpoints to use. Options: Main, Portal, API.
Offset Pagination offset to start returning results from (default 0).
Limit Maximum number of product results to return (minimum 1, default 50).

For this specific resource-operation (Product - Get), only the properties shown above are relevant.

Output

The output is an array of JSON objects representing individual products retrieved from the STEM Connect API. Each item corresponds to one product record returned by the /api/products/get endpoint.

The structure of each product object depends on the STEM Connect API response but typically includes product details such as IDs, names, descriptions, pricing, or other metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests to the STEM Connect API.
  • The node uses the internal helper function stemConnectApiRequest to perform HTTP requests.
  • Network access to the STEM Connect API endpoints must be available.

Troubleshooting

  • Empty or no results: Check that the Offset and Limit parameters are set correctly and that products exist in the STEM Connect system.
  • Authentication errors: Ensure the API key credential is valid and has sufficient permissions.
  • API request failures: Network issues or incorrect subsystem selection may cause errors; verify subsystem choice matches your API access.
  • Unexpected response format: If the API changes, the node might not parse results correctly; check STEM Connect API documentation for updates.

Links and References

Discussion