Task Types
On-Demand Tasks
Execute immediately when triggered manually or via API
Scheduled Tasks
Run automatically based on cron schedules
Event-Driven Tasks
Triggered by webhooks or system events
Recurring Tasks
Execute on a regular interval (daily, weekly, monthly)
Creating Tasks
From the Console
- Navigate to Tasks in your workspace
- Click Create Task
- Configure task details:
- Name and description
- Agent to execute
- Prompt/command to run
- Schedule (optional)
- Save and optionally enable
From Conversation
Create tasks directly from agent conversations:Task Templates
Save common operations as reusable templates:Built-in Templates
CloudThinker includes templates for common operations:| Template | Agent | Description |
|---|---|---|
| Daily Cost Report | Alex | Summarize daily spending and anomalies |
| Weekly Security Audit | Oliver | Comprehensive security scan |
| Database Health Check | Tony | Performance and health metrics |
| K8s Cluster Review | Kai | Cluster utilization and issues |
| Infrastructure Summary | Anna | Cross-agent infrastructure overview |
Custom Templates
Create custom templates for your organization:- Navigate to Tasks > Templates
- Click Create Template
- Define the template:
- Name and category
- Agent assignment
- Prompt text (supports variables)
- Default schedule
- Share with your workspace
Template Variables
Use variables in templates for dynamic content:Scheduling with Cron
Define precise schedules using cron expressions:Cron Expression Builder
CloudThinker includes a visual cron builder to help create schedules:| Field | Values | Example |
|---|---|---|
| Minute | 0-59 | 0 (on the hour) |
| Hour | 0-23 | 8 (8 AM) |
| Day of Month | 1-31 | 1 (first of month) |
| Month | 1-12 | * (every month) |
| Day of Week | 0-6 | 1 (Monday) |
Common Schedules
| Schedule | Cron Expression |
|---|---|
| Every day at 8 AM | 0 8 * * * |
| Every Monday at 9 AM | 0 9 * * 1 |
| First of each month | 0 0 1 * * |
| Every 6 hours | 0 */6 * * * |
| Weekdays at 6 PM | 0 18 * * 1-5 |
Timezone Support
All schedules run in your workspace timezone (configurable in settings).Task Execution
Execution Flow
Execution Options
Configure how tasks execute:- Timeout: Maximum execution time (default: 30 minutes)
- Retries: Number of retry attempts on failure
- Notification: Alert on completion/failure
- Output: Where to store results (conversation, report, etc.)
Managing Tasks
Task Status
| Status | Description |
|---|---|
| Active | Task is enabled and will run on schedule |
| Paused | Task is disabled but retains configuration |
| Running | Task is currently executing |
| Completed | Last run completed successfully |
| Failed | Last run encountered an error |
Task History
View execution history for each task:- Execution timestamp
- Duration
- Status and outcome
- Output/results
- Error details (if failed)
Bulk Operations
Manage multiple tasks at once:- Enable/disable selected tasks
- Update schedules in bulk
- Delete obsolete tasks
- Export task configurations
Task Notifications
Configure notifications for task events:Notification Triggers
- On Start: Notify when task begins
- On Complete: Notify when task finishes successfully
- On Failure: Alert when task encounters an error
- On Output: Notify when specific conditions are met in results
Notification Channels
- Email notifications
- Slack messages
- Webhook calls
- In-app notifications
Task Workflows
Chain multiple tasks together:Sequential Workflows
Execute tasks in order:Parallel Execution
Run independent tasks simultaneously:Conditional Tasks
Execute tasks based on conditions:Integration with External Systems
API Triggers
Trigger tasks via the CloudThinker API:Webhook Triggers
Configure tasks to run on external events:- Create a webhook endpoint in CloudThinker
- Configure external system to call the webhook
- Map webhook payload to task parameters
CI/CD Integration
Run tasks as part of deployment pipelines:- Post-deployment cost analysis
- Pre-release security scan
- Infrastructure validation
Best Practices
Use Descriptive Names
Use Descriptive Names
Name tasks clearly to indicate their purpose, schedule, and scope. Example: “Daily-EC2-CostAnalysis-Production”
Set Appropriate Timeouts
Set Appropriate Timeouts
Configure timeouts based on expected task duration. Too short causes failures; too long delays feedback.
Configure Failure Alerts
Configure Failure Alerts
Always set up notifications for task failures to catch issues early.
Review History Regularly
Review History Regularly
Periodically review task execution history to identify patterns and optimize schedules.
Use Templates
Use Templates
Create templates for common patterns to ensure consistency and reduce configuration errors.
View Operations Hub
Browse 325+ pre-built operations that can be scheduled as tasks