n8n nodes for STEM Connect API - telecommunications management system
npm install n8n-nodes-stemconnectThis package contains a unified n8n node for integrating with the STEM Connect API, a comprehensive telecommunications management system.
This package provides a single STEM Connect node that manages all telecommunications operations:
- TOCs (Take Over Certificates) - File upload/download and data submission
- ISPs (Internet Service Providers) - ISP management and configuration
- Devices - Network device management and monitoring
- End Customer Circuits - Circuit provisioning and management
- End Customers - Customer management
- VLANs - Network VLAN configuration
- Products - Service product management
- Sites - Physical site management
- Contacts - Contact management
- Billing - Billing information
1. Install the package in your n8n instance:
``bash`
npm install n8n-nodes-stemconnect
2. Restart your n8n instance to load the new nodes.
This package is compatible with:
- n8n versions: 1.88.0 and newer
- n8n-workflow: 1.88.0 (pinned for exact compatibility)
- Node.js versions: 18.17.0 and newer
The node has been specifically tested and optimized for compatibility with older n8n versions, including 1.88.0, to resolve URL handling issues that may occur in earlier versions. The n8n-workflow dependency is pinned to version 1.88.0 to ensure exact compatibility and prevent issues with newer workflow APIs.
Before using any of the nodes, you need to configure your STEM Connect API credentials:
1. Go to your n8n credentials settings
2. Create a new credential of type "STEM Connect API"
3. Enter your API key and base URL (default: https://om.stemconnect.net)
The STEM Connect node provides operations for all major telecommunications entities:
This package covers the following STEM Connect API endpoints:
- List TOCs
- POST /api/tocs/upload - Upload TOC files
- POST /api/tocs/submit - Submit TOC data
- GET /api/tocs/download/{uniqueId} - Download TOC files$3
- GET /api/isps/get - Get all ISPs
- POST /api/isps/add - Add new ISP
- POST /api/isps/update/{isp_id} - Update ISP$3
- GET /api/devices/get - Get devices
- GET /api/devices/get/{serial_no} - Get device by serial
- POST /api/devices/add - Add device
- POST /api/devices/create - Create device
- POST /api/devices/update/{serial_no} - Update device
- GET /api/devices/get/promo - Get promo products$3
- GET /api/endcustomercircuits/get - Get all circuits
- GET /api/endcustomercircuits/get/{circuit_no} - Get circuit
- POST /api/endcustomercircuits/add - Add circuit
- PATCH /api/endcustomercircuits/update/{circuit_no} - Update circuit
- DELETE /api/endcustomercircuits/delete/{circuit_no} - Delete circuit
- POST /api/endcustomercircuits/generate-toc - Generate TOC PDFUsage Examples
$3
1. Add a "STEM Connect" node to your workflow
2. Set resource to "Device"
3. Set operation to "Get"
4. Configure pagination parameters (offset, limit)
5. Execute to retrieve device list$3
1. Add a "STEM Connect" node
2. Set resource to "Circuit"
3. Set operation to "Add"
4. Fill in circuit details (circuit number, speeds, PPPoE credentials)
5. Execute to create the circuit$3
1. Add a "STEM Connect" node
2. Set resource to "Circuit"
3. Set operation to "Generate TOC"
4. Provide the circuit number
5. Execute to generate and download the TOC PDF$3
1. Add a "STEM Connect" node
2. Set resource to "ISP"
3. Choose operation (Get, Add, Update)
4. Configure parameters as needed
5. Execute the operationError Handling
All nodes include comprehensive error handling:
- API errors are properly caught and reported
- Continue on fail option available
- Detailed error messages for troubleshooting
Authentication
The nodes use API key authentication as required by the STEM Connect API:
- API key is passed in the
apiKey` headerFor issues and questions:
1. Check the STEM Connect API documentation: https://om.stemconnect.net/api/
2. Review the n8n documentation for node development
3. Open an issue in this repository
MIT License - see LICENSE file for details.
Contributions are welcome! Please:
1. Fork the repository
2. Create a feature branch
3. Make your changes
4. Add tests if applicable
5. Submit a pull request