Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node allows you to create a scheduler by sending structured scheduling data to an external service. It is useful for automating tasks or workflows that need to be triggered based on specific schedules or conditions defined in the input data. For example, you could use it to set up automated report generation, periodic notifications, or system maintenance tasks.

Properties

Name Meaning
X USER ID The user identifier required for authentication or tracking purposes. This value is sent as a header named X-USER-ID in the request.
Data A JSON object containing the scheduler configuration details. It includes fields such as: subvalue, thirdvalue, is_global, is_active, email, included_application, companies, agent_ids, excludecompany, include_tags, exclude_tags, uifilters, trigger_reboot, and integrations. These fields define the scope, activation status, recipients, filters, and other parameters of the scheduler.

Output

The node outputs JSON data representing the response from the scheduler creation API. This typically includes confirmation of the scheduler creation, any identifiers assigned, and possibly status or error messages. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key or token credential for authenticating with the external scheduler service.
  • The node sends HTTP requests with custom headers (including X-USER-ID) and JSON body payloads.
  • No additional environment variables are explicitly required beyond standard API authentication setup.

Troubleshooting

  • Missing or invalid X USER ID header: Ensure the user ID is provided and correctly mapped to the header; otherwise, the API may reject the request.
  • Malformed JSON in Data property: The Data field must be valid JSON. Invalid JSON will cause request failures.
  • API authentication errors: Verify that the API key or token credential is configured properly in n8n.
  • Network or connectivity issues: Confirm that the external scheduler service endpoint is reachable from the n8n instance.
  • Unexpected API responses: Check the structure of the Data JSON matches the expected schema required by the external service.

Links and References

  • Refer to the external scheduler service API documentation for detailed information on the JSON schema and available options within the Data property.
  • Consult n8n documentation on how to configure API credentials and handle HTTP headers in nodes.

Discussion