Actions30
- Billing Actions
- Circuit Actions
- Contact Actions
- Device Actions
- End Customer Actions
- ISP Actions
- Product Actions
- Site Actions
- TOC Actions
- VLAN Actions
TOC → Get
AI-generatedOverview
This node integrates with the STEM Connect API to manage telecommunications operations, specifically focusing on Take Over Certificates (TOCs) when using the "TOC" resource with the "Get" operation. It retrieves TOC records from the database, supporting filtering and pagination.
Common scenarios where this node is beneficial include:
- Fetching a list of TOCs for auditing or reporting purposes.
- Filtering TOCs by their status or associated device serial number.
- Integrating TOC data retrieval into automated workflows for telecom service management.
Practical example:
- Retrieve the first 50 TOCs with a specific status to monitor pending certificates.
- Query TOCs related to a particular device by its serial number to track device handovers.
Properties
| Name | Meaning |
|---|---|
| Subsystem | Selects the subsystem endpoint to use: "Main", "Portal", or "API". |
| Offset | Pagination offset to skip a number of results (default 0). |
| Limit | Maximum number of TOC results to return (minimum 1, default 50). |
| TOC Status | Filter TOCs by their status (string filter). |
| Serial Number | Filter TOCs by the device's serial number (string filter). |
Output
The output is an array of JSON objects representing TOC records retrieved from the STEM Connect API. Each item corresponds to a TOC entry with its associated data fields as returned by the API.
If the "download" operation is used (not covered here), the node returns the raw content of a TOC file, which may be binary data representing the downloaded file.
Dependencies
- Requires an API key credential for authenticating with the STEM Connect API.
- The node uses HTTP requests to the STEM Connect endpoints under
/api/tocs/getfor fetching TOCs. - Proper configuration of the API credential in n8n is necessary for successful communication.
Troubleshooting
- Empty results: Ensure that the filters such as TOC Status or Serial Number are correct and that the offset/limit parameters are set appropriately.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- API request failures: Network issues or incorrect subsystem selection can cause failures; confirm the subsystem matches your API environment.
- Unsupported operations: Some TOC operations like upload or submit require additional implementation for file handling or form data, which are not supported out-of-the-box.
Links and References
- STEM Connect API documentation (refer to your organization's API docs for detailed endpoint info)
- n8n documentation on creating and configuring API credentials
- General REST API usage guidelines within n8n