0-CodeKit icon

0-CodeKit

A toolbox of no-code utilities

Actions40

Overview

The Operator - Scheduler operation in the 0-CodeKit n8n node allows you to schedule HTTP POST requests to a specified webhook with custom JSON data. You can configure the scheduling as a one-time event, multiple specific times, a cronjob, or a timed posthook. This is useful for automating tasks such as sending notifications, triggering workflows, or integrating with external systems at scheduled intervals.

Practical examples:

  • Send a daily summary report to a Slack webhook every morning.
  • Trigger a workflow at several specific dates/times (e.g., reminders).
  • Use a cron expression to automate periodic data pushes to an API.
  • Set up a timed posthook for advanced scheduling scenarios.

Properties

Name Meaning
Webhook to Send To The URL of the webhook where the data will be sent. Required.
Stringified JSON Data The JSON data (as a string) that will be sent to the webhook. Required.
intervalType Type of scheduling. Options:
- One-Time
- Multiple Times
- Cronjob
- Timed Posthook
One-Time Execution Date and time for a single execution. Used when intervalType is "One-Time".
Multiple Times Collection of date/time values for multiple executions. Used when intervalType is "Multiple Times".
Cronjob Cron expression defining the schedule. Used when intervalType is "Cronjob". For more info: crontab-generator.com
Times Posthook Configuration string for a timed posthook. Used when intervalType is "Timed Posthook". For more info: 1saas.co docs
End Date Optional date/time after which the scheduler should be deactivated.

Output

The output is a JSON object containing the response from the scheduling request. The structure depends on the response from the underlying service, but typically includes confirmation of the scheduled task or error details if the request failed.

Example output:

[
  {
    "success": true,
    "message": "Scheduler created",
    "details": {
      "webhook": "https://example.com/webhook",
      "intervalType": 1,
      "scheduledAt": "2024-07-01T09:00:00Z"
    }
  }
]

If an error occurs and "Continue On Fail" is enabled, the output may look like:

[
  {
    "error": "Error: Invalid webhook URL"
  }
]

Dependencies

  • External Service: Requires access to the CodeKit API (the backend service handling the scheduling).
  • API Key: The node requires codeKitApi credentials configured in n8n.
  • Network Access: The n8n instance must be able to reach both the CodeKit API and the target webhook URLs.

Troubleshooting

Common issues:

  • Invalid Webhook URL: If the provided webhook is malformed or unreachable, the node will return an error.
  • Malformed JSON Data: If the "Stringified JSON Data" is not valid JSON, the scheduling may fail.
  • Incorrect Cron Expression: An invalid cron string will result in a scheduling error.
  • Missing Required Fields: Omitting required fields for the selected interval type will cause errors.

Error messages:

  • "Error: Invalid webhook URL" – Check the webhook URL format and accessibility.
  • "Error: Malformed JSON" – Ensure your JSON data is properly formatted.
  • "Error: Invalid cron expression" – Validate your cron syntax using a tool like crontab-generator.com.

Links and References

Discussion