Schedule an HTTP job

Prerequisites

• Confirm the absolute HTTP or HTTPS endpoint, method, cadence, and IANA timezone.
• Ask whether the endpoint needs headers, a JSON body, or an idempotency key.
• Keep credentials out of URLs and logs. Refer to values from a secure store.

Workflow

1. Preview plain-English cadence and resolve every clarification.
2. Show the resolved cron, timezone, and next runs to the user.
3. Create the schedule with exactly one of text or cron.
4. For changes, identify the existing schedule and send only changed fields.
5. After execution, inspect retained history and verify the endpoint outcome.

MCP examples