Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node is designed to create an integration credential within a system called "Connect Secure" by sending user-specific data to the API. It is useful when you need to programmatically register or update credentials for integrations, enabling automated workflows that require authenticated access to external services.

Typical use cases include:

  • Automating the setup of integration credentials for new users.
  • Managing credentials dynamically based on user input or other workflow data.
  • Centralizing credential creation as part of a larger automation pipeline.

Properties

Name Meaning
X USER ID The User ID header value sent with the request; identifies the user making the request.
Data JSON object containing the body payload for creating the integration credential.

Output

The node outputs JSON data representing the response from the Connect Secure API after attempting to create the integration credential. This typically includes details about the created credential or error information if the operation failed.

No binary data output is indicated in the source code.

Dependencies

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

Troubleshooting

  • Missing or invalid X USER ID: If the "X USER ID" header is not provided or incorrect, the API may reject the request. Ensure this property is set correctly.
  • Malformed JSON in Data: The "Data" property expects valid JSON. Invalid JSON will cause parsing errors before the request is sent.
  • Authentication errors: If the API key credential is missing or invalid, the node will fail to authenticate.
  • API connectivity issues: Network problems or incorrect API endpoint configuration can cause request failures.

To resolve these issues:

  • Verify all required properties are set and valid.
  • Confirm the API key credential is configured and has necessary permissions.
  • Check network connectivity and API endpoint URLs.
  • Validate JSON syntax in the "Data" property.

Links and References

Discussion