AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node operation "Post Create Credential" under the "Credentials" resource is designed to create a new credential record by sending an HTTP POST request. It allows users to specify a user ID via a custom header and optionally include additional JSON data in the request body. This node is useful when integrating with APIs that require creating or registering credentials programmatically, such as onboarding new users or systems with specific access credentials.

Practical examples:

  • Creating API credentials for a new user in a third-party service.
  • Registering device credentials in an IoT platform.
  • Adding authentication tokens or keys to a centralized credential management system.

Properties

Name Meaning
X USER ID The User Id to be sent as a custom HTTP header X-USER-ID. Required for identifying the user context of the credential creation request.
Additional Body Fields Optional additional fields to include in the JSON body of the POST request. Currently supports a JSON field named data where you can specify arbitrary JSON content (e.g., { "is_excluded": false }).

Output

The node outputs the response from the API call in the json output field. This typically contains the details of the newly created credential as returned by the external service. The exact structure depends on the API but generally includes identifiers, status, and metadata about the created credential.

No binary data output is indicated in the provided code or properties.

Dependencies

  • Requires an API key or token credential configured in n8n to authenticate requests to the target service.
  • The base URL for the API is expected to be set in the node's credentials configuration.
  • The node uses standard HTTP headers including Accept: application/json and Content-Type: application/json.
  • The user must provide the X-USER-ID header value for the request.

Troubleshooting

  • Missing or invalid X USER ID: The API may reject requests without this header or with incorrect values. Ensure the user ID is correctly provided.
  • Malformed JSON in Additional Body Fields: If the JSON in the data field is not valid, the request will fail. Use proper JSON syntax.
  • Authentication errors: Verify that the API key or token credential is correctly configured and has sufficient permissions.
  • API endpoint issues: Confirm the base URL and endpoint paths are correct in the node’s credential settings.
  • Unexpected API responses: Check the API documentation for required fields and response formats if the output is not as expected.

Links and References

  • Refer to the target API’s official documentation for details on the credential creation endpoint, required headers, and body parameters.
  • n8n documentation on HTTP Request nodes and credential management for general guidance on configuring API calls.

Discussion