AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node is designed to create an integration rule by sending a POST request to an external service. It is useful in scenarios where users need to programmatically define or update integration rules within a system, such as automating configuration of integrations or managing user-specific integration settings.

A practical example would be automating the creation of integration rules for different users in a SaaS platform, where each rule might specify how data flows between systems or what conditions trigger certain actions.

Properties

Name Meaning
X USER ID The User Id header value sent with the request; identifies the user making the request.
Additional Body Fields Optional JSON fields to include in the request body; can customize the integration rule.

The "Additional Body Fields" property supports adding a JSON object under the key data. By default, it includes { "is_default": false }, but this can be customized to add any other relevant fields required by the API.

Output

The node outputs the JSON response returned from the API after creating the integration rule. This typically contains details about the newly created integration rule, such as its ID, status, and any metadata returned by the service.

If the API returns binary data (not indicated here), it would be included accordingly, but based on the provided code and properties, the output is expected to be JSON only.

Dependencies

  • Requires an API key credential for authentication with the external service.
  • The base URL for the API must be configured in the node credentials.
  • The node uses a predefined OpenAPI specification (openapi.json) bundled with the node to build its properties and handle requests.

Troubleshooting

  • Missing or invalid X USER ID: Since the X USER ID header is required, omitting it or providing an incorrect value will likely cause authentication or authorization errors. Ensure this field is correctly set.
  • Invalid JSON in Additional Body Fields: The data field expects valid JSON. Malformed JSON will cause parsing errors before the request is sent.
  • API connectivity issues: Verify that the base URL and API credentials are correctly configured and that the external service is reachable.
  • Unexpected API errors: Check the API response message for details. Common issues may include permission errors, invalid request formats, or server-side problems.

Links and References

  • No direct links provided in the source code.
  • Refer to the external service's API documentation for detailed information on integration rule creation and supported fields.

Discussion