Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node updates a company record via the Connect Secure API. It is useful in scenarios where you need to modify existing company data programmatically, such as updating tags, status flags, or other metadata fields. For example, you might use this node to mark a company as deleted, add assessment flags, or update custom tags based on workflow conditions.

Properties

Name Meaning
X USER ID The user identifier required for authentication or tracking purposes in the API request.
Data JSON object containing the fields and values to update on the company record. Typical fields include is_assessment, is_migrated, is_deleted, tags, and manual_tags.
Id Numeric identifier of the company to update.

Output

The node outputs the response from the Connect Secure API after attempting to update the company. The output is structured as JSON representing the updated company data or the API's confirmation message. There is no indication that binary data is returned by this node.

Dependencies

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

Troubleshooting

  • Missing or invalid X USER ID: The API requires a valid user ID header; ensure this is provided and correct.
  • Invalid company Id: If the company ID does not exist or is incorrect, the API will likely return an error indicating the resource was not found.
  • Malformed JSON in Data: The Data property must be valid JSON. Errors parsing this field will cause the request to fail.
  • API authentication errors: Ensure the API key credential is correctly configured and has sufficient permissions.
  • Network or connectivity issues: Verify network access to the Connect Secure API endpoint.

Links and References

  • Connect Secure API documentation (not provided here, but should be consulted for detailed field definitions and error codes).

Discussion