CLAUDE LABJP
FORK — Claude Code 2.1.212 changes what /fork does: it copies your conversation into a new background session with its own row in claude agents, so you can keep working. The old in-session subagent is now /subtaskLIMITS — WebSearch calls are now capped at 200 per session by default, and subagent spawns get the same 200 ceiling, so a runaway search or delegation loop stops on its ownMCPBG — MCP tool calls running past two minutes now move to the background automatically, keeping the session usable. Tune the threshold with CLAUDE_CODE_MCP_AUTO_BACKGROUND_MSPLANFIX — Fixed plan mode auto-running file-modifying Bash commands such as touch and rm without a permission prompt or an SDK canUseTool callbackSONNET5 — Claude Sonnet 5 is running on introductory pricing of $2 per million input tokens and $10 per million output. After August 31 it moves to $3 and $15IPO — Bankers are reportedly lining up investor meetings for Anthropic ahead of a possible public listing as soon as OctoberFORK — Claude Code 2.1.212 changes what /fork does: it copies your conversation into a new background session with its own row in claude agents, so you can keep working. The old in-session subagent is now /subtaskLIMITS — WebSearch calls are now capped at 200 per session by default, and subagent spawns get the same 200 ceiling, so a runaway search or delegation loop stops on its ownMCPBG — MCP tool calls running past two minutes now move to the background automatically, keeping the session usable. Tune the threshold with CLAUDE_CODE_MCP_AUTO_BACKGROUND_MSPLANFIX — Fixed plan mode auto-running file-modifying Bash commands such as touch and rm without a permission prompt or an SDK canUseTool callbackSONNET5 — Claude Sonnet 5 is running on introductory pricing of $2 per million input tokens and $10 per million output. After August 31 it moves to $3 and $15IPO — Bankers are reportedly lining up investor meetings for Anthropic ahead of a possible public listing as soon as October
Articles/Cowork
Cowork/2026-03-27Beginner

Automate Cross-App Workflows with Cowork — HubSpot, Slack, Google Drive Integration Guide

Non-technical guide to using Claude Cowork for cross-app business automation. Connect HubSpot, Slack, Google Drive, and automate sales reports, follow-ups, and data consolidation.

cowork13automation95hubspotslackgoogle-drivebusiness-report

Claude Cowork bridges your business apps—HubSpot, Slack, Google Drive—and orchestrates workflows between them. Most business tasks are variations on one pattern: "fetch data from app A, process it, write results to app B, notify app C." Cowork automates that pattern. Here's how, step by step, for non-technical users.

What is Cowork? — The Bridge Between Apps

Old way:

Check HubSpot for sales numbers
  ↓
DM sales team on Slack for their numbers
  ↓
Manually type into Google Sheets
  ↓
Send report to Slack

Cowork way:

Auto-fetch HubSpot data
  ↓ (Processed by Claude)
  ↓
Auto-message sales team on Slack
  ↓
Auto-save to Google Drive
  ↓
Auto-notify on Slack
  (all while you're at coffee)

Step 1: Connect Your Apps via Connectors

HubSpot

  1. In Cowork, click "+ Add Connector"
  2. Search "HubSpot"
  3. Click "Authenticate"
  4. Log in → Click "Approve"

Done in 30 seconds. No API keys to copy.

Slack

  1. "+ Add Connector"
  2. Search "Slack"
  3. Click "Authenticate"
  4. Select workspace → "Approve"

Google Drive

  1. "+ Add Connector"
  2. Search "Google Drive"
  3. Google login → "Approve"

All three apps: 3 minutes total.

Step 2: Describe What You Want (In Plain English)

Now tell Cowork what to do. Natural language, no code.

Example: Weekly Sales Report

In Cowork's "New Task" field, write:

【Task】
Automated Weekly Sales Report

【What I want】
1. Get last week's total sales from HubSpot
2. Ask sales team on Slack: "What were your numbers?"
3. Collect responses, save as Excel to Google Drive
4. Notify me on Slack when done

Cowork (Claude internally) reads this, understands it, and proposes an execution plan.

Interactive Confirmation

Cowork: "Ready to go with this?"

✓ HubSpot: Fetch 7-day sales total
✓ Slack: Message #sales-team
✓ Google Drive: Save as "Sales_Report_YYYY-MM-DD.xlsx"
✓ Slack: Final notification to #announcements

Click "Confirm" → Done.

Step 3: Save as Skill + Schedule

Want the same report weekly? Save it as a skill and schedule it.

Save as Skill

  1. Click "Save" button
  2. Name it (e.g., "Weekly Sales Report")
  3. Save

Schedule It

  1. Click the clock icon next to your saved skill
  2. Select "Every Monday at 9:00 AM"
  3. Save

From now on, your report auto-generates every Monday morning and gets delivered to the team.

Step 4: Customize Output Format

Tweak how reports look without breaking a sweat.

Use a Template

【Report Format】

# Weekly Sales Report (YYYY-MM-DD)

## Total Sales
[amount]

## By Person
- Reps A: [amount]
- Rep B: [amount]

## Next Week's Target
[target]

Tell Cowork "Use this template" → Every report follows it perfectly.

Change Output Type

  • Excel → PDF
  • Google Sheet (auto-append)
  • CSV format
  • Slack message formatting

Just ask. Cowork handles it.

Real-World Example: Automated Customer Follow-Ups

Automate your follow-up workflow:

【Process】
HubSpot: Auto-extract customers not contacted in 7 days
  ↓
Slack: Notify sales team: "Follow up with these customers"
  ↓
Google Drive: Save list as "Follow-Up Targets"

Schedule daily at 10:00 AM → Team arrives to a ready follow-up list.

Why Non-Technical People Can Do This

Cowork works for non-engineers because:

  1. Simple authentication — No API keys. Just click "Approve"
  2. Natural language — Plain English (or Japanese), not code
  3. Interactive validation — Cowork asks "Did you mean...?" so you can correct misunderstandings

If you can use Excel or Google Sheets, you can use Cowork.

Common Questions

Q1: What if Slack messages aren't answered? Cowork waits (timeout configurable, e.g., 2 hours), then marks as "no response" in the report. You can override manually anytime.

Q2: What if something breaks? Cowork auto-detects errors, sends Slack notification with the reason and fix suggestions. Easy recovery.

Q3: Can multiple reports run simultaneously? Yes. Schedule multiple skills at different times—they run in parallel.

Wrapping Up

Claude Cowork automates the "data aggregation across apps" pattern that powers most business workflows. Sales reports, expense reports, customer follow-ups—all the same structure, all automatable.

Designed for non-technical users, Cowork turns complex multi-app orchestration into natural language requests and a few clicks.

For advanced patterns, role-based task distribution, and enterprise case studies, see "Cowork Skills × Scheduling: Advanced Automation Patterns and Techniques."

Share

Thank You for Reading

Claude Lab is ad-free, supported entirely by members like you. We publish practical guides daily with implementation code, benchmarks, and production-ready patterns. If you've found it useful, we'd love to have you on board.

  • Copy-paste ready implementation code
  • New advanced guides published daily
  • $5/mo or $10 for lifetime access
View Membership →

If you found this article helpful, a small tip ($1.50) would mean a lot to us. Your support helps keep this site ad-free and covers server and hosting costs.

Related Articles

Cowork2026-07-17
It Worked on My Machine, but Nobody Could Trigger It — Four Assumptions I Stripped Out of a Cowork Plugin
I bundled four working automation skills into a plugin and shared it. Only one of them ever fired. Here is how I measured skill trigger rate, and the four assumptions — vocabulary, paths, connections, and naming — I had to strip out before it was portable.
Cowork2026-07-05
When Claude Declines a Request on Safety Grounds, What Should an Unattended Pipeline Return?
A third kind of ending that is neither an error nor a normal completion — a safety decline. Here is how to fold it into a pipeline you run unattended, with a classifier and a review-queue design drawn from indie development.
Cowork2026-06-27
Logged as success, but it produced nothing — stopping silent failures in Cowork scheduled tasks with end-of-run assertions
A Cowork scheduled task exits 0, yet not a single artifact was produced. Trusting the exit code alone hides this silent failure. Here is how to turn your definition of done into end-of-run assertions that fail loudly with an evidence log.
📚RECOMMENDED BOOKS
Build a Large Language Model (From Scratch)
Sebastian Raschka
LLM Dev
Prompt Engineering for LLMs
Berryman & Ziegler
Prompting
AI Engineering
Chip Huyen
AI Eng
* Contains affiliate links
See all →