Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Update Company Mapping under the Integration resource, is designed to update configuration settings related to company integration mappings in an external system via an API. It allows users to modify notification preferences, consent settings, integration rules, and other configuration flags for a specific company identified by an ID.

Typical use cases include:

  • Automating updates to company integration settings as part of a workflow.
  • Synchronizing company preferences or rules from one system to another.
  • Enabling or disabling notifications and consents programmatically based on business logic.

For example, a user might update a company's mapping to disable notifications and enable consent tracking after receiving updated compliance requirements.

Properties

Name Meaning
X USER ID The User Id header value used for authentication or identification in the API request headers.
Data JSON object containing the update details:
- no_notification (boolean)
- enable_notification (boolean)
- consent_enabled (boolean)
- configuration (boolean)
- integration_rules (stringified JSON array)
Id Numeric identifier of the company mapping record to update.

Output

The node outputs the JSON response returned by the API after attempting to update the company mapping. This typically includes confirmation of the update status or the updated company mapping data.

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 endpoint that handles company mapping updates.
  • Proper configuration of the API credentials within n8n is necessary for successful execution.

Troubleshooting

  • Missing or invalid X USER ID: The API may reject requests without a valid user ID header. Ensure this property is correctly set.
  • Invalid JSON in Data property: The data field must be valid JSON. Malformed JSON will cause errors.
  • Incorrect company Id: Providing an invalid or non-existent company Id may result in "not found" or similar errors.
  • API authentication errors: Verify that the API key credential is configured and has sufficient permissions.
  • Network or connectivity issues: Ensure that n8n can reach the external API endpoint.

Common error messages might include:

  • Unauthorized or 401 errors due to missing/invalid credentials.
  • 400 Bad Request if required fields are missing or malformed.
  • 404 Not Found if the specified company Id does not exist.

Resolving these usually involves verifying input properties, credentials, and network access.

Links and References

Discussion