Configure
HTTP job settings
Configure URL, method, headers, body, and timeout for a task.
Overview
Every CronFox task is an HTTP request. These settings control what CronFox sends when the schedule fires (or when you click Run now).
Step-by-step
- Open Collections → your collection → the task (create or edit).
- Set the URL to an absolute address CronFox can reach from the internet.
- Choose the HTTP method (
GET,POST,PUT,PATCH, orDELETE). - Optionally add headers (for example
AuthorizationorContent-Type). - Optionally add a body for methods that send one (
POST,PUT,PATCH). - Optionally enable a custom timeout in advanced settings (default is 30 seconds when unset).
- Save the task and use Run now once to verify the request.
Fields
| Field | Purpose |
|---|---|
| URL | Target endpoint. Prefer HTTPS. |
| Method | HTTP verb CronFox uses |
| Headers | Key/value pairs sent with the request |
| Body | Request payload (when applicable) |
| Timeout | How long CronFox waits for a response before failing |
Tips
- Store secrets in headers (API keys, bearer tokens). Treat them like production credentials.
- Keep payloads small; oversized bodies are harder to debug in execution history.
- If the endpoint is flaky, combine a reasonable timeout with retries.
- CronFox must reach the URL from the public internet — localhost and private VPC-only hosts will not work unless you expose them.