Getting Started

Getting Started with Overclock #

Welcome to Overclock! This guide will walk you through creating your first AI agent using natural language. No coding required—just describe what you want to automate.

The Overclock Workflow #

Creating an AI agent with Overclock follows a simple pattern:

  1. Conversation: Chat with Overclock to describe your goal
  2. Generation: Overclock creates a structured playbook
  3. Refinement: Collaborate with Overclock AI to improve the playbook
  4. Testing: Run your playbook manually
  5. Deployment: Schedule your agent to run automatically

Let’s walk through each step.

Step 1: Start a Conversation #

Go to https://overclock.work and you’ll see a chat interface where you can describe what you want to automate. Simply type your automation goal in the text area and click the arrow button to get started.

Example Conversation #

You: “I want to get a daily summary of new customer support tickets from Linear and have it sent to our team Slack channel.”

Overclock: “I can help you create a playbook for daily Linear ticket summaries! Let me generate a playbook that will:

  • Connect to your Linear workspace
  • Fetch new customer support tickets from the last 24 hours
  • Summarize the key issues and priorities
  • Post the summary to your specified Slack channel

Would you like me to create this playbook?”

You: “Yes, that sounds perfect. Can you make sure it runs every weekday at 9 AM?”

Step 2: Overclock Generates Your Playbook #

Overclock will create a structured playbook based on your conversation:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12

# Daily Customer Support Summary
This playbook fetches new customer support tickets from Linear and
sends a daily summary to the team Slack channel.

- Connect to Linear workspace
- Query tickets created in the last 24 hours with label "customer-support"
- Analyze ticket priorities and common themes
- Format a concise summary with key metrics
- Post summary to #customer-support Slack channel

## Trigger
- Run Monday through Friday at 9:00 AM EST

Step 3: Refine Through Conversation #

Continue chatting to refine your playbook:

You: “Can you also include the number of urgent tickets and highlight any that haven’t been assigned yet?”

Overclock: “Absolutely! I’ll update the playbook to include urgent ticket counts and flag unassigned tickets.”

Overclock will update your playbook with these improvements.

Step 4: Connect Your Integrations #

Before testing, you’ll need to connect the integrations your playbook uses:

  1. Click “Integrations” in the right panel
  2. Connect to Linear by clicking “Connect” and following the OAuth flow
  3. Connect to Slack the same way
  4. Grant the necessary permissions

The system will automatically detect which integrations your playbook needs based on its content.

Step 5: Test Your Playbook #

Once your integrations are connected:

  1. Click “Run” to execute your playbook manually
  2. Watch the real-time execution log
  3. Review the output to ensure it meets your expectations
  4. Make adjustments by continuing the conversation if needed

Example Test Output #

✓ Connected to Linear workspace
✓ Found 12 new tickets in the last 24 hours
✓ Identified 3 urgent tickets, 2 unassigned
✓ Generated summary report
✓ Posted to #customer-support Slack channel

Final Output:
📊 Daily Support Summary - January 24, 2024
• Total new tickets: 12
• Urgent tickets: 3 (2 unassigned ⚠️)
• Common themes: Login issues (4), Billing questions (3)
• Avg response time: 2.3 hours

Step 6: Deploy Your Agent #

When you’re satisfied with your playbook:

  1. Click “Deploy” in the top-right corner
  2. Configure your schedule using the intuitive scheduler
  3. Choose whether to receive notifications
  4. Set any Slack channels for delivery

Your agent is now live and will run automatically according to your schedule!

Best Practices for Playbook Conversations #

Be Specific About Your Goals #

Instead of: “Help with tickets” Try: “Send me a daily summary of urgent customer support tickets that haven’t been responded to in 4+ hours”

Mention Your Tools #

Include the specific tools you use: “from Linear”, “post to Slack”, “save to Google Drive”

Describe Your Timing #

Be clear about when things should happen: “every weekday at 9 AM”, “once a week on Mondays”, “whenever a high-priority ticket is created”

Ask for Clarification #

Overclock can explain any part of your playbook: “Can you explain how the ticket priority detection works?”

Common First Playbooks #

Here are some popular automation ideas for your first playbook:

  • Daily standups: Collect updates from team tools and post to Slack
  • Issue monitoring: Alert when critical tickets or bugs are created
  • Report generation: Summarize weekly metrics from your project management tools
  • Content curation: Find and share relevant articles or updates
  • Data syncing: Keep information updated between different tools

Next Steps #

Now that you’ve created your first playbook:

  1. Explore Integrations: Check out all the tools you can connect
  2. See More Examples: Browse real playbook examples for inspiration
  3. Create More Agents: Try automating other workflows
  4. Share with Your Team: Playbooks can be shared and collaboratively improved

Getting Help #

Having trouble? Overclock is always available to help:

  • Ask questions about your playbook: “Why did this step fail?”
  • Request improvements: “Can you make this faster?”
  • Get explanations: “How does the Linear integration work?”

Welcome to the future of automation with Overclock!