YouGotYouGot

Call your endpoint at a scheduled time

A reminder on the webhook channel sends a reminder.fired event. It reports the scheduled reminder firing; it does not report a teammate completing it or an SMS carrier delivering it.

Register and test an endpoint

  1. Keep current Business access and prepare a public HTTPS endpoint you control. Private network endpoints and redirects are blocked.
  2. Open Webhooks, register a POST endpoint and securely save its secret.
  3. Use Test connection. Your endpoint should receive webhook.test and return a 2xx response. A successful dashboard test activates it. Changing its URL or method requires another test.

Schedule the webhook reminder

Create a reminder in your dashboard, select the webhook channel and your active endpoint, and choose a future time. For API creation, replace the timestamp and endpoint ID:

{
  "message": "Start the follow-up workflow",
  "scheduledAt": "2030-01-10T15:00:00Z",
  "channel": "webhook",
  "targetWebhookId": "YOUR_ACTIVE_ENDPOINT_ID",
  "metadata": {
    "sourceRecordId": "handoff-123"
  }
}

Verify and acknowledge delivery

For POST requests, compute HMAC-SHA256 over the exact raw request body using the endpoint secret, encode it as hexadecimal and compare in constant time with X-YouGot-Signature. Reject mismatches. Return 2xx after durably accepting the event. Don't expose the secret in client code.

{
  "event": "reminder.fired",
  "timestamp": "2030-01-10T15:00:00.000Z",
  "data": {
    "reminderId": "REMINDER_ID",
    "message": "Start the follow-up workflow",
    "scheduledAt": 1894287600000,
    "isRecurring": false,
    "recurrence": null,
    "metadata": {
      "sourceRecordId": "handoff-123"
    }
  }
}

This initial recipe is for one unchanged, one-off reminder. Deduplicate that test event by data.reminderId before repeating any downstream action. Retry payloads are rebuilt from the current reminder, and the attempt timestamp changes; editing or recurring scheduling can change scheduledAt between attempts. There is currently no stable occurrence ID or replay window in the signature, so validate your own deduplication and replay controls before using recurring or consequential workflows.

Failures, quotas and teardown

To use a tool such as Make, Zapier or n8n, configure its HTTP/webhook step and downstream action yourself. Availability and third-party plans vary; this recipe doesn't claim a native connector.