7 use cases across 4 jobs · newest added Nov 3, 2026

Hand this to your AI agent. It does the boring part.

Step-by-step use cases for Claude Code and n8n. Pick a job and hand your agent the steps.

What do you want off your plate?

Latest use cases

Every use case is available as a web page, a .md file, or a one-click copy.

All 7 use cases →

2 use cases for Reports. Clear filter

See one in action

The whole use case, step by step.

This is what your agent gets. Open any step, then copy the whole thing as Markdown.

Researchintermediateagent: n8nevidence: Documented

Monitor competitors and get a weekly digest

Watch competitors' public pricing pages, changelogs and blogs, and get a weekly email listing only what changed.

  1. List the pages to watch
    For each competitor, list their pricing page, changelog and blog (an RSS feed is better than scraping if they have one). Leave out social media accounts (see the warning). Check each site's terms and robots.txt; robots.txt tells crawlers what they are asked not to fetch.
  2. Track changes with Firecrawl
    Scrape each page with Firecrawl's changeTracking format. It compares the page with the last time you scraped it and marks it new, same, changed or removed, with an optional git-style diff. Firecrawl's Monitoring feature can run these checks on a schedule for you. Prefer self-hosting? changedetection.io is an open-source alternative.
  3. Run it weekly in n8n
    Add a Schedule Trigger for once a week, then the Firecrawl node (or an HTTP Request node) for each URL. Keep only results whose status is changed or removed.
  4. Summarize only what changed
    Pass the diffs to a Basic LLM Chain node.
  5. Email the digest and check ityou check
    Send the summary with the Send Email or Gmail node. Before acting on a change, open the page and confirm it yourself.

New to agents?

Start here. Three use cases, one weekend.

Picked for beginners: the non-advanced use cases with the shortest setup, one per job. Do them in order.

Total listed setup time: 3 h

The tools behind the use cases

Every tool shows the use cases that use it.

Hover a use case anywhere on this page to light up the tools it uses.

Browse all 14 tools →

Airbyte MCP

0 use cases

Hosted MCP server for Airbyte pipelines, job logs and optional read-only data access.

No use case uses this yet.

Free tier · MCP server

Browserbase

0 use cases

Headless browsers your agents can drive.

No use case uses this yet.

Free tier · MCP server

Claude Code

0 use cases

Coding agent for the terminal, IDE and desktop.

No use case uses this yet.

Paid · MCP client and server

CrewAI

0 use cases

Framework for teams of role-based agents.

No use case uses this yet.

Free tier · MCP client
No news items yet.

Personal AI gear

Devices that feed your agents

Hardware that captures meetings, notes, and paper so your agents have something to work with. Each card says how far we've checked it.

All 6 gear →
Front view of the gray, card-shaped Plaud Note Pro with a ridged body, PLAUD logo and a round button

Not tested by CrimsonBot · Based on sourced reviews

Plaud Note Pro

A card-style recorder for in-person meetings and phone calls, with 64 GB storage, long battery life and MCP access to ChatGPT or Claude. CrimsonBot has not tested it.

$189price checked Oct 30, 2026Details →
Round Omi pendant on a black cord with a small blue LED lit in the center

Not tested by CrimsonBot · Based on published specs

Omi AI Pendant

An open-source pendant notetaker whose memories and transcripts reach Claude, ChatGPT, Cursor and other clients through Omi's hosted MCP server. No independent hands-on review was opened. CrimsonBot has not tested it.

$169–$229price checked Oct 30, 2026Details →
Black Bee Frontier wristband device with a single round button, shown beside the words Bee Frontier on a lavender background, with three small color-variant thumbnails

Not tested by CrimsonBot · Based on published specs

Bee Frontier

A wrist- or clip-worn recorder that turns conversations into summaries in the Bee app. CrimsonBot has not tested it. Shipping in the US. Bee Pro is optional.

For agents (and the humans who build them)

Your agent can read this whole site. No scraping required.

Every use case, tool, and gear item is clean Markdown and JSON. Point your agent at llms.txt or the REST API and it gets the steps, the tools, and nothing else. No key is needed for read access while the API is in beta.

# every use case, as JSON
$ curl https://crimsonbot.com/api/v1/use-cases
# filter by job
$ curl "https://crimsonbot.com/api/v1/use-cases?category=support"
# one use case as Markdown
$ curl https://crimsonbot.com/use-cases/scanned-invoices-ocr-n8n.md
# the site map for agents
$ curl https://crimsonbot.com/llms.txt
# MCP server: planned at /mcp, not shipped yet

The newsletter

Get an email when the newsletter launches.

The newsletter has not launched. Join the list and we'll email you when it does. Free.

Questions

What is CrimsonBot?

Step-by-step use cases you can hand to an agent, a directory of the tools they use, personal AI gear that works alongside you, and news about how agents are changing. A use case is published only after an editor approves it. Drafts are not listed.

How are use cases and tools sourced?

A use case is published only after an editor approves it. Tool facts are corrected from each vendor's own pages. Published use cases carry an evidence label, and named sources are listed when they were recorded. Listings can go out of date, and they are not rechecked on a fixed schedule. Sponsors and paid links do not change sort order.

How often is CrimsonBot updated?

There is no fixed schedule. Published use cases, tools and gear show up in the RSS feed at /feed.xml. Drafts are not included.