Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to create a company mapping integration. It is designed to send configuration data related to company mappings, including notification settings and integration rules, to the API. This node is useful in scenarios where you need to programmatically configure or update company integration settings within the Connect Secure platform, such as enabling or disabling notifications, managing consent flags, or applying specific integration rules.

Practical examples include:

  • Automating the setup of company-specific integration parameters during onboarding.
  • Updating notification preferences for a company based on user input.
  • Managing consent and configuration flags centrally via workflow automation.

Properties

Name Meaning
X USER ID The User Id header value required for authentication or identification in the API request.
Data JSON object containing the company mapping configuration. Includes:
- no_notification (boolean): Flag to disable notifications.
- enable_notification (boolean): Flag to enable notifications.
- consent_enabled (boolean): Flag indicating if consent is enabled.
- configuration (boolean): General configuration flag.
- integration_rules (stringified JSON array): Rules that define integration behavior.

Output

The node outputs the response from the Connect Secure API call in the json field of the output data. This typically contains the result of the create company mapping operation, such as confirmation details or error messages returned by the API.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node depends on the external Connect Secure API service being available.
  • No additional environment variables are explicitly required beyond the API credential.

Troubleshooting

  • Missing or invalid X USER ID: The API requires the X USER ID header; ensure this is provided and valid to avoid authentication errors.
  • Malformed JSON in Data property: The data property must be valid JSON. Invalid JSON will cause request failures.
  • API connectivity issues: Network problems or incorrect API credentials can lead to failed requests.
  • Error responses from API: The node will pass through error messages from the API; check these messages for clues on misconfiguration or permission issues.

Links and References

  • Connect Secure API documentation (refer to your organization's internal API docs or vendor-provided resources).
  • n8n documentation on HTTP Request nodes and custom node development for further customization guidance.

Discussion