> ## Documentation Index
> Fetch the complete documentation index at: https://docs.thinkplatform.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Choose User guide for browser tasks, Developers for CLI, SDK and external agents, and Administration for organization management.
> Confirm identity and organization/project context before operations. Documentation access does not grant ThinkPlatform permissions.
> Review side effects, verify changes with a read, and do not blindly retry an operation with an uncertain outcome.
> Use documented UI steps for the web app and documented public CLI or SDK interfaces for automation. Follow each page’s prerequisites and authentication requirements.

# Schedules and webhooks

> Configure scheduled work and outbound event notifications.

Scheduled automations run configured work on a timetable. Webhook subscriptions send selected events to a target URL. Availability depends on your deployment and permissions.

## Before you begin

Select the intended organization and project. You need permission to configure the automation and access to its target. Ensure the target action and recipient are appropriate: a schedule can repeatedly perform work, and a webhook sends event data outside the platform.

## Create a scheduled automation

For this example, use the summary agent from [Create and configure an agent](https://docs.thinkplatform.ai/guides/agents/create-and-configure.md), with its three-bullet instruction and no tools or knowledge attached. The schedule repeats the same fixed-input test each day; it does not collect live project status.

1. Open **Automation → Schedules** and choose **New scheduled automation**. Enter `Daily summary test` as **Name**, choose **Agent**, and select the summary agent. Enter `Summarize this: The team shipped the search page Monday. On Tuesday, users reported slow results. The team plans to add caching on Friday.` as the prompt.
2. Under **Execution mode**, choose **Schedule** and a daily schedule. Set **Hour** to `9`, **Minute** to `0`, **Second** to `0`, and **Timezone** to `Asia/Tokyo`. Leave **Start after** empty and turn off **Catch up missed runs** so missed runs are not requested for catch-up. Review the enabled setting and choose **Create**.
3. Open the schedule and check **Next run**: it should be the next future 09:00 in Tokyo, subject to the displayed schedule and service state. After that time, inspect **Last run** and open the resulting agent task. Check for three bullets covering Monday's release, Tuesday's slow results, and Friday's planned caching. A scheduled time or created record does not prove the task succeeded.

A schedule can be stopped or edited through its available controls. Check its status after changing it. Some target and device combinations may be unavailable; follow any warning shown in the form.

For requests arriving from an external sender to start an agent or flow, use an authenticated [inbound webhook endpoint](https://docs.thinkplatform.ai/guides/automation/webhook-endpoints.md).

## Create a webhook subscription

1. Open **Automation → Webhooks → Subscriptions** and choose **New subscription**.
2. Enter the **Target URL** and select the **Event types** to send. Configure authentication, signing, retry, and enabled settings as appropriate for the receiving service.
3. Choose **Create**, then inspect the subscription and its delivery information as events occur. Confirm receipt at the destination.

## Troubleshoot

Check the selected project, permissions, target configuration, and displayed errors. For schedules, verify the timezone, enabled state, next run, and target status. For webhooks, check the URL, selected events, authentication, and delivery details. Before retrying or re-enabling an automation, check whether the operation already occurred.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.