Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node integrates with the Connect Secure API to update agent credential mappings. It allows users to modify the credentials associated with an agent by specifying the user ID, the mapping data, and the identifier of the credential mapping to update. This is useful in scenarios where credential assignments need to be programmatically maintained or updated, such as automating user access management or synchronizing credential information across systems.

Practical examples include:

  • Updating an agent's credential details after a role change.
  • Automating credential mapping updates during onboarding or offboarding processes.
  • Synchronizing credential mappings from an external system into Connect Secure.

Properties

Name Meaning
X USER ID The User ID header value used for authentication or identification in the API request.
Data JSON object containing the new credential mapping data to update for the agent.
Id Numeric identifier of the specific agent credential mapping to update.

Output

The node outputs JSON data representing the response from the Connect Secure API after attempting to update the agent credential mapping. This typically includes confirmation of the update, any updated fields, or error messages if the update failed.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • Depends on the Connect Secure API being accessible and properly configured.
  • The node uses the @devlikeapro/n8n-openapi-node package and OpenAPI specification (openapi.json) bundled within the node for request construction.

Troubleshooting

  • Common issues:

    • Missing or invalid "X USER ID" header can cause authentication failures.
    • Incorrect or malformed JSON in the "Data" property may result in API errors.
    • Providing an invalid or non-existent "Id" will likely cause the update to fail.
  • Error messages:

    • Authentication errors related to missing or invalid user ID header.
    • Validation errors if the JSON body does not conform to expected schema.
    • Not found errors if the specified credential mapping ID does not exist.

To resolve these:

  • Ensure the "X USER ID" is correctly set and valid.
  • Validate the JSON structure before sending.
  • Confirm the "Id" corresponds to an existing credential mapping.

Links and References

Discussion