Overview
This node, named "Scheduler," interacts with an external Scheduler API to manage webhook scheduling. It allows users to either schedule a webhook to be triggered at a specific time or cancel a previously scheduled webhook by its unique identifier.
Common scenarios include:
- Automating tasks that need to be executed at a future date/time via webhooks.
- Managing delayed or timed notifications or data processing by scheduling HTTP requests.
- Canceling scheduled webhooks if the conditions change or the task is no longer needed.
For example, you could use this node to schedule a webhook that triggers a workflow execution exactly 24 hours later, or cancel a webhook if the user cancels their subscription before the scheduled action occurs.
Properties
| Name | Meaning |
|---|---|
| Action | Choose between "Schedule Webhook" (to create a new scheduled webhook) or "Cancel Webhook" (to cancel an existing one). |
| Unique ID | A required string that uniquely identifies the webhook to schedule or cancel. |
| Run At | The date and time when the webhook should be fired (required for scheduling only). |
| Treat Date/Time As UTC | Boolean flag indicating whether the "Run At" time should be treated as UTC (true) or local time (false). Only applies when scheduling. |
| URL | The target URL to which the webhook request will be sent (required for scheduling only). |
| Method | HTTP method to use for the webhook request; options are "GET" or "POST" (required for scheduling only). |
| Body | JSON object representing the body of the webhook request (required for scheduling only). |
Output
The node outputs the response from the Scheduler API in the json output field. This typically includes confirmation details about the scheduled or canceled webhook. The exact structure depends on the API's response but generally confirms success or failure of the requested action.
The node does not output binary data.
Dependencies
- Requires access to an external Scheduler API endpoint.
- Needs an API authentication token or key configured in the node credentials to authorize requests.
- The base URL for the Scheduler API must be set in the credentials configuration.
- The node sends HTTP POST requests to
/api/schedule_webhookor/api/cancel_webhookendpoints.
Troubleshooting
- Invalid or missing Unique ID: The API requires a unique identifier for each webhook. Ensure this is provided and unique per webhook.
- Incorrect date/time format: The "Run At" property must be a valid date-time string. If "Treat Date/Time As UTC" is false, ensure the local time is correctly interpreted.
- API authentication errors: Verify that the API key or token is correctly configured and has sufficient permissions.
- Malformed JSON body: When scheduling a webhook, the "Body" must be valid JSON. Invalid JSON will cause request failures.
- Network or connectivity issues: Ensure the base URL is reachable and the network allows outbound connections to the Scheduler API.
- Unsupported HTTP method: Only GET and POST methods are supported for the webhook request.
Links and References
- Refer to your Scheduler API documentation for detailed information on the
/api/schedule_webhookand/api/cancel_webhookendpoints. - n8n documentation on HTTP Request Node may provide additional context on how HTTP routing works within nodes.