Actions30
- Billing Actions
- Circuit Actions
- Contact Actions
- Device Actions
- End Customer Actions
- ISP Actions
- Product Actions
- Site Actions
- TOC Actions
- VLAN Actions
End Customer → Get
AI-generatedOverview
This node integrates with the STEM Connect API to manage telecommunications operations. Specifically, for the End Customer - Get operation, it retrieves a paginated list of end customers from the STEM Connect system. This is useful in scenarios where you need to fetch customer data for reporting, synchronization, or further processing within an automation workflow.
Practical examples include:
- Automatically retrieving updated lists of end customers to sync with a CRM.
- Fetching customer data to trigger notifications or billing processes.
- Integrating customer information into dashboards or analytics tools.
Properties
| Name | Meaning |
|---|---|
| Subsystem | Selects which subsystem of the STEM Connect API to use. Options: Main, Portal, API. |
| Offset | Pagination offset to start returning results from (default 0). Used only in Main subsystem and for certain resources including End Customer. |
| Limit | Maximum number of results to return (minimum 1, default 50). Used only in Main subsystem and for certain resources including End Customer. |
Output
The output is an array of JSON objects representing individual end customers retrieved from the STEM Connect API. Each item corresponds to one end customer record as returned by the /api/endcustomers/get endpoint.
The exact structure of each end customer object depends on the STEM Connect API response but typically includes customer details such as identifiers, names, contact info, and related metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests against the STEM Connect API.
- The node uses the
stemConnectApiRequesthelper function to perform HTTP requests. - The "Main" subsystem must be selected to access the End Customer resource.
- Network connectivity to the STEM Connect API endpoints is required.
Troubleshooting
- Empty or no results: Check that the Offset and Limit parameters are set correctly and that there are end customers available in the system.
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions.
- API request failures: Network issues or incorrect subsystem/resource/operation selections can cause errors. Verify all parameters.
- Unhandled operation messages: The node currently returns placeholder messages for add/update operations on End Customer, indicating these require additional implementation.
Links and References
- STEM Connect API Documentation (replace with actual URL if available)
- n8n documentation on Creating Custom Nodes
- General REST API usage in n8n workflows
Note: This summary focuses exclusively on the "End Customer" resource with the "Get" operation under the "Main" subsystem as requested.