> ## 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.

# Automation commands

> Manage schedules, hooks, webhooks, and agent follow-up tasks.

These examples assume an authenticated active saved profile with the intended organization and project. Confirm it with `tp context show` before running commands. Add root `--json` before the command when machine parsing needs JSON output; use root `--profile <name>` only to override the active profile.

Use these command patterns before falling back to `tp api` or `tp raw`.

## Check context and available resources

```bash theme={"system"}
tp auth whoami
tp context show
tp automation schedules list
tp automation hooks list
tp automation webhooks list
tp hooks list
tp webhooks list
tp tasks list
tp agents list
tp flows list
```

## Scheduled automations

Discover exact options first when creating because schedule payload fields may evolve:

```bash theme={"system"}
tp help automation schedules
tp help automation schedules create
tp automation schedules list
```

Use dry-run when available:

```bash theme={"system"}
tp automation schedules create --body @schedule.json --dry-run
tp automation schedules create --body @schedule.json
tp automation schedules update <schedule_id> --body @schedule.json --dry-run
tp automation schedules update <schedule_id> --body @schedule.json
tp automation schedules status <schedule_id> stop
tp automation schedules log <schedule_id> --device-id <device_id>
tp automation schedules agent-log <schedule_id>
```

## Inbound hooks

```bash theme={"system"}
tp automation hooks list
tp automation hooks create --body @hook.json --dry-run
tp automation hooks create --body @hook.json
tp automation hooks deliveries <hook_id>
tp automation hooks invoke <hook_id> --body @payload.json
tp automation hooks rotate-secret <hook_id> --dry-run
```

## Outbound webhooks

```bash theme={"system"}
tp automation webhooks event-types
tp automation webhooks list
tp automation webhooks create --body @webhook.json --dry-run
tp automation webhooks create --body @webhook.json
tp automation webhooks test <subscription_id> --body @event.json
tp automation webhooks deliveries <subscription_id>
tp automation webhooks retry-delivery <delivery_id>
```

## Agent follow-ups and tasks

```bash theme={"system"}
tp tasks create --title "Review project results" --agent-id <agent_id> --dry-run
tp tasks create --title "Review project results" --agent-id <agent_id>
tp tasks followups <task_id>
tp tasks followups-bulk --task-ids "<task_id_1>,<task_id_2>"
tp tasks cancel-followup <task_id> <followup_id>
tp tasks status <task_id>
tp tasks messages <task_id>
```

## Verification checklist

* Read back the created resource by ID.
* Confirm trigger, target, auth context, and output location.
* Run a dry-run, test event, or controlled manual invocation.
* Inspect delivery/run/task status after the test.
* Report the next expected execution time or event condition.


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