AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node allows users to create a scheduler entry by sending a POST request to an external service. It is useful in scenarios where automated scheduling of tasks, events, or processes is required within a workflow. For example, you might use this node to programmatically set up scheduled jobs for data processing, notifications, or system maintenance based on dynamic input parameters.

Properties

Name Meaning
X USER ID The user identifier header value sent with the request. This is a required string that identifies the user making the request.
Additional Body Fields Optional additional fields to include in the request body. This is a collection allowing customization of the scheduler creation payload. It includes a JSON field named Data which can contain various properties such as:
- subvalue (array)
- thirdvalue (array)
- is_global (boolean)
- is_active (boolean)
- email (array)
- included_application (array)
- companies (array)
- agent_ids (array)
- excludecompany (array)
- include_tags (array)
- exclude_tags (array)
- uifilters (array)
- trigger_reboot (boolean)
- integrations (array)
These fields allow detailed configuration of the scheduler's behavior and scope.

Output

The node outputs JSON data representing the response from the scheduler creation API. This typically includes confirmation details about the newly created scheduler entry, such as its ID, status, and any metadata returned by the external service. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key or authentication token configured in n8n credentials to authorize requests to the external scheduler service.
  • The base URL for the API must be set in the node’s credential configuration.
  • The node depends on the external service defined by the OpenAPI specification bundled with the node.

Troubleshooting

  • Missing or invalid X USER ID: Since the user ID header is required, omitting it or providing an incorrect value will likely cause authorization errors. Ensure the correct user ID is provided.
  • Malformed JSON in Additional Body Fields: The Data field expects valid JSON. Invalid JSON syntax will cause request failures. Use proper JSON formatting.
  • API connectivity issues: Network problems or incorrect base URL settings can prevent successful communication with the scheduler service.
  • Permission errors: Insufficient permissions associated with the API key or user ID may result in access denied errors.
  • To resolve these issues, verify all inputs, credentials, and network configurations carefully.

Links and References

  • Refer to the external scheduler service API documentation for detailed information on the expected request body structure and response format.
  • Consult n8n documentation on how to configure API credentials and handle HTTP request nodes for further customization.

Discussion