Skip to main content
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

Scheduled automations

Discover exact options first when creating because schedule payload fields may evolve:
Use dry-run when available:

Inbound hooks

Outbound webhooks

Agent follow-ups and tasks

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.