AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

The node provides functionality to update scheduler configurations via a PATCH HTTP request. It is designed to modify existing scheduler entries by sending partial updates, which is useful when you want to change specific fields without replacing the entire scheduler object.

Common scenarios include:

  • Updating activation status or global flags of a scheduler.
  • Modifying associated user IDs, tags, or company filters.
  • Adjusting integration settings or reboot triggers for scheduled tasks.

For example, you might use this node to activate or deactivate a scheduler, add or remove companies or tags it applies to, or update email notification settings dynamically.

Properties

Name Meaning
X USER ID The user identifier required for authentication or authorization purposes. This value is sent as an HTTP header named X-USER-ID.
Additional Body Fields Optional additional fields to include in the PATCH request body. These include:
- Data: A JSON object containing various scheduler attributes such as subvalue, thirdvalue, is_global, is_active, email, included_application, companies, agent_ids, excludecompany, include_tags, exclude_tags, uifilters, trigger_reboot, and integrations.
- Id: Numeric identifier of the scheduler entry to update.

Output

The node outputs JSON data representing the response from the PATCH update operation on the scheduler. This typically includes the updated scheduler object or confirmation of the successful update.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authentication (referred generically).
  • The base URL for the API must be configured in the node credentials.
  • The node depends on an external service that exposes a REST API supporting PATCH operations on scheduler resources.

Troubleshooting

  • Missing or invalid X USER ID header: The API may reject requests if the user ID header is missing or incorrect. Ensure the property is set correctly.
  • Invalid JSON in Data field: The data field expects valid JSON. Malformed JSON will cause errors. Use proper JSON formatting.
  • Scheduler ID not provided or invalid: The id field is necessary to identify which scheduler to update. Omitting or providing an invalid ID will result in failure.
  • API connectivity issues: Verify network access and correct base URL configuration.
  • Permission errors: Ensure the API key has sufficient permissions to perform PATCH updates on schedulers.

Links and References

  • Refer to the API documentation of the scheduler service for detailed schema and supported fields in the PATCH request body.
  • JSON formatting guides to ensure valid input for the data field.

Discussion