STEM Connect icon

STEM Connect

Manage telecommunications operations with STEM Connect API

Actions30

Contact → Get

AI-generated

Overview

This node integrates with the STEM Connect API to manage telecommunications-related data and operations. Specifically, for the Contact resource with the Get operation, it retrieves contact records from the STEM Connect system. This is useful in scenarios where you need to fetch contact information such as names, phone numbers, or email addresses associated with telecom accounts or services.

Practical examples include:

  • Synchronizing contact lists from STEM Connect into a CRM.
  • Automating notifications by retrieving contact details.
  • Reporting or auditing contacts related to telecom services.

Properties

Name Meaning
Subsystem Selects which subsystem of the STEM Connect API to use. Options: Main, Portal, API.
Offset Pagination offset to skip a number of results (only available when Subsystem is Main).
Limit Maximum number of contact results to return (only available when Subsystem is Main).

Output

The output is an array of JSON objects representing individual contact records retrieved from the STEM Connect API. Each object corresponds to one contact's data as returned by the /api/contacts/get endpoint.

No binary data is output by this operation.

Example output structure (simplified):

[
  {
    "id": "contact_id_1",
    "name": "John Doe",
    "email": "john.doe@example.com",
    "phone": "+1234567890",
    ...
  },
  {
    "id": "contact_id_2",
    "name": "Jane Smith",
    "email": "jane.smith@example.com",
    "phone": "+0987654321",
    ...
  }
]

Dependencies

  • Requires an API key credential for authenticating with the STEM Connect API.
  • The node uses HTTP requests to the STEM Connect endpoints; network connectivity to the STEM Connect service is required.
  • No additional external dependencies beyond the configured API authentication.

Troubleshooting

  • Empty results: Check that the Offset and Limit parameters are set correctly and that there are contacts 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 selection may cause errors. Verify the subsystem is set to "Main" for Contact Get operations.
  • Rate limits or timeouts: If many contacts are requested at once, consider using pagination via Offset and Limit to reduce load.

Links and References

Discussion