0CodeKit icon

0CodeKit

A toolbox of no-code utilities

Actions108

Overview

The "Scheduler" operation within the "Operator" resource of this node allows users to schedule HTTP POST requests to a specified webhook URL with custom JSON data payloads. It supports various scheduling types including one-time execution, multiple specific times, cronjob-based recurring schedules, and timed posthooks. This functionality is useful for automating data delivery or triggering workflows at defined intervals or times.

Practical examples:

  • Sending a notification or data update once at a specific date/time.
  • Posting data repeatedly at multiple predefined dates/times.
  • Triggering a webhook on a recurring schedule using cron expressions.
  • Using timed posthooks for advanced scheduling scenarios as supported by an external API.

Properties

Name Meaning
Code Variables A collection of code variables where each variable has a name (or ID) and a value. These variables can be used in conjunction with code editor functions (not directly related to Scheduler but part of Operator resource).
Webhook to Send To The URL of the webhook endpoint where the JSON data will be sent via HTTP POST.
Stringified JSON Data The JSON data payload, provided as a string, that will be sent to the webhook.
Interval Type The type of scheduling interval to use. Options are:
1 - One-Time
2 - Multiple Times
3 - Cronjob
4 - Timed Posthook
One-Time Execution (Shown if Interval Type = One-Time) The exact date and time when the data should be posted once to the webhook.
Multiple Times (Shown if Interval Type = Multiple Times) A collection of multiple date/time entries specifying when to post the data repeatedly to the webhook.
Cronjob (Shown if Interval Type = Cronjob) A cron expression defining the recurring schedule for posting data to the webhook.
Times Posthook (Shown if Interval Type = Timed Posthook) A string representing a timed posthook configuration URL or identifier, used for advanced scheduling scenarios.
End Date An optional date/time after which the scheduler should be deactivated and stop sending data.

Output

The node outputs an array of JSON objects representing the responses from the scheduling API or service after attempting to set up the scheduled posts. Each item corresponds to one input item processed.

  • The json output field contains the response data from the scheduling request.
  • No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authentication with the underlying scheduling service.
  • The node makes HTTP POST requests to the scheduling API endpoints corresponding to the Operator resource.
  • The user must provide a valid webhook URL to receive the scheduled POST requests.
  • For cronjobs and timed posthooks, knowledge of cron syntax or the external posthook API is necessary.

Troubleshooting

  • Invalid webhook URL: If the webhook URL is malformed or unreachable, the scheduling request will fail. Verify the URL correctness and accessibility.
  • Incorrect JSON data format: The data property expects a stringified JSON. Invalid JSON strings will cause errors. Use proper JSON formatting.
  • Cron expression errors: Invalid cron syntax will cause scheduling failures. Validate cron expressions using online tools like https://crontab-generator.com/.
  • Missing required fields: Depending on the interval type, required properties such as one-time date, multiple times list, cronjob string, or posthook string must be provided.
  • API authentication issues: Ensure the API key credential is correctly configured and has permissions to create schedules.
  • End Date misconfiguration: Setting an end date earlier than start dates or invalid date formats may cause unexpected behavior.

Links and References

Discussion