# CallMeLater Documentation

> CallMeLater is a developer-first API for scheduling durable HTTP calls and interactive human reminders. Authenticate with Bearer tokens (sk_live_...). Two core primitives: (1) Scheduled webhooks — fire HTTP requests at a future time with automatic retries, (2) Approval reminders — send yes/no/snooze prompts via email or SMS with escalation. Also supports multi-step chains (workflows) and reusable templates. SDKs available for Node.js, Laravel/PHP, and n8n.

This file contains links to documentation sections following the llmstxt.org standard.

## Table of Contents

- [CallMeLater](https://docs.callmelater.io/): Schedule durable HTTP calls and interactive human approvals. One API, automatic retries, full audit trail.
- [Quick Start](https://docs.callmelater.io/quick-start): Schedule your first action in 60 seconds.
- [Laravel SDK](https://docs.callmelater.io/sdks/laravel): Fluent Laravel SDK for CallMeLater with Facades, webhook events, and Artisan commands.
- [n8n Integration](https://docs.callmelater.io/sdks/n8n): Use CallMeLater in n8n visual workflows with the community node package.
- [Node.js SDK](https://docs.callmelater.io/sdks/nodejs): Official TypeScript SDK for CallMeLater. Zero dependencies, ESM + CJS.
- [Actions & Scheduling](https://docs.callmelater.io/concepts/actions): Everything in CallMeLater is an **action** -- something scheduled to happen in the future. Actions operate in one of two modes: **webhook** or **ap...
- [Approvals & Reminders](https://docs.callmelater.io/concepts/approvals): Approval actions send interactive messages to humans and collect their responses. When someone responds, CallMeLater notifies your system -- your c...
- [Retries, Errors & Callbacks](https://docs.callmelater.io/concepts/reliability): CallMeLater automatically retries failed webhook deliveries and notifies you of outcomes via callbacks. This page covers how retries work, how to c...
- [Chains & Workflows](https://docs.callmelater.io/guides/chains): Chains let you compose multi-step workflows where each step can be an HTTP webhook, a human approval gate, or a timed wait. Steps execute sequentia...
- [Common Patterns](https://docs.callmelater.io/guides/patterns): Practical, copy-paste-ready patterns for the most frequent CallMeLater use cases. Each example shows the SDK code alongside the equivalent curl req...
- [Templates](https://docs.callmelater.io/guides/templates): Templates are reusable action configurations with unique trigger URLs. Once created, anyone can trigger a template with a simple POST request -- no...
- [Account & Settings](https://docs.callmelater.io/api/account): Endpoints for managing your account quota, contacts, and domain verification.
- [Actions](https://docs.callmelater.io/api/actions): Actions are the core primitive in CallMeLater. An action is either a scheduled HTTP request (**webhook** mode) or a human approval request (**appro...
- [Authentication](https://docs.callmelater.io/api/authentication): All API requests require authentication using a Bearer token.
- [Chains](https://docs.callmelater.io/api/chains): Chains are multi-step workflows that execute actions sequentially. Each step can be an HTTP call, a human approval gate, or a timed wait. Data flow...
- [Templates](https://docs.callmelater.io/api/templates): Templates let you define reusable action or chain configurations with a unique trigger URL. Each template gets a public endpoint that can be called...
- [Limits, Plans & Changelog](https://docs.callmelater.io/reference/limits): | Endpoint | Authenticated | Unauthenticated |
- [Security & Webhooks](https://docs.callmelater.io/reference/security): When CallMeLater delivers an HTTP action, it sends a signed request to your endpoint.