Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve mappings between agents and their credentials. Specifically, the "Retrieve Agent Credential Mapping" operation fetches credential mapping details for a given agent identified by an ID. This is useful in scenarios where you need to programmatically access or audit which credentials are assigned to specific agents within the Connect Secure system.

Practical examples include:

  • Automating audits of agent credential assignments.
  • Integrating credential mapping data into broader workflows for security compliance.
  • Fetching credential mappings dynamically to drive conditional logic in automation processes.

Properties

Name Meaning
X USER ID User Id header value required for authentication or identification in the API request.
Id Numeric identifier of the agent whose credential mapping is to be retrieved.

Output

The node outputs JSON data representing the agent credential mapping retrieved from the Connect Secure API. The structure typically includes details about the agent and associated credentials, such as credential IDs, types, and possibly metadata describing the mapping.

No binary data output is indicated.

Dependencies

  • Requires an API key or token credential to authenticate with the Connect Secure API.
  • The node depends on the Connect Secure API being accessible and properly configured.
  • No additional external services beyond the Connect Secure API are required.

Troubleshooting

  • Missing or invalid "X USER ID" header: Ensure that the "X USER ID" property is set correctly; it is mandatory for the API call.
  • Invalid or missing agent Id: The "Id" property must be a valid number corresponding to an existing agent.
  • Authentication errors: Verify that the API key or authentication token credential is correctly configured and has sufficient permissions.
  • API connectivity issues: Check network connectivity and API endpoint availability.
  • Unexpected response structure: Confirm that the Connect Secure API version matches the expected schema used by the node.

Links and References

Discussion