STEM Connect icon

STEM Connect

Manage telecommunications operations with STEM Connect API

Actions30

Billing → Get

AI-generated

Overview

This node integrates with the STEM Connect API to manage telecommunications operations across multiple subsystems. Specifically, for the Billing - Get operation, it retrieves billing information from the STEM Connect system. This is useful in scenarios where you need to automate fetching billing data for telecom services, such as generating reports, syncing billing info with other systems, or triggering workflows based on billing status.

Practical example:

  • Automatically retrieve the latest billing information for a customer or account to update your CRM or accounting software.
  • Use billing data to trigger alerts or notifications when invoices are generated or payments are due.

Properties

Name Meaning
Subsystem Selects which subsystem's API endpoints to use. Options: Main, Portal, API.

For this specific Billing - Get operation, only the "Subsystem" property is relevant and defaults to "Main".

Output

The output JSON contains the billing information retrieved from the STEM Connect API endpoint /api/billing/get. The structure depends on the API response but generally includes detailed billing data related to telecommunications services managed by STEM Connect.

  • The node outputs an array of JSON objects representing billing records.
  • No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating with the STEM Connect API.
  • The node uses the stemConnectApiRequest helper function to make HTTP requests to the STEM Connect API.
  • Proper configuration of the API credentials in n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Authentication failures if the API key credential is missing or invalid.
    • Network connectivity problems preventing access to the STEM Connect API.
    • Unexpected API response formats if the API version changes.

  • Error messages:

    • Errors thrown by the API (e.g., 401 Unauthorized) will be surfaced unless "Continue On Fail" is enabled.
    • If the node fails, check that the subsystem is correctly set and that the API credentials are valid.

  • Resolution tips:

    • Verify API credentials and permissions.
    • Confirm network access to the STEM Connect API endpoints.
    • Enable "Continue On Fail" to handle errors gracefully within workflows.

Links and References

Discussion