create_scout
Set up a monitoring scout to continuously track web changes based on your query and receive alerts.
Instructions
Create a monitoring scout for continuous web monitoring. Scouts track changes relevant to a query and alert you. Examples: 'news about Yutori', 'H100 pricing below $1.50'.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Natural language description of what to monitor. Examples: 'Tell me about the latest news, product updates, or announcements about Yutori', 'when H100 pricing per hour drops below $1.50', 'anytime a startup in SF announces seed funding' | |
| output_interval | No | Seconds between scout runs. Minimum 1800 (30 minutes). Default: 86400 (daily) | |
| webhook_url | No | HTTPS URL to receive webhook notifications when updates are available. Must use https://. Confirm the URL with the user before setting. | |
| webhook_format | No | Webhook payload format: 'scout' (default), 'slack', or 'zapier' | |
| output_fields | No | Optional: Extract structured data as an array of objects with these field names. Example: ['headline', 'summary', 'url']. If omitted, returns human-readable text. For complex schemas, call the Yutori REST API directly (see example at: https://docs.yutori.com/reference/scouts-create#using-scheduling-webhooks-and-a-structured-output-schema). | |
| user_timezone | No | Timezone for scheduling. Example: 'America/New_York'. Default: 'America/Los_Angeles' | |
| skip_email | No | If true, skip email notifications (useful with webhooks) | |
| start_timestamp | No | Unix timestamp for when monitoring should start (0 = immediately) | |
| user_location | No | User location for geo-relevant searches. Format: 'city, region, country' | |
| is_public | No | Whether scout results are publicly accessible |