DataDoe + Claude Tag in SlackConnect DataDoe, and anyone in #amazon-ops can tag @Claude with a Seller Central, Vendor Central or Amazon Ads question. The answer lands in the thread for the whole team to read, digests post on a schedule, and a change to Amazon waits for the person who owns it.
Claude Tag is in public beta on Claude Team and Enterprise. DataDoe is $97 a month after a 14-day free trial.
Claude Tag does not borrow anyone’s login by default. When you tag it in a channel, it can reach DataDoe in two ways, and most Amazon teams end up using both: a personal connector for their own asks, and a shared one for the channel.
@Claude in #amazon-opsDataDoe added on your claude.ai account, under Customize → Connectors.
DataDoe added once by a Claude Owner in the Claude Tag admin settings.
DataDoe→
Seller Central, Vendor Central, Amazon Ads| SKU | Units | Reason | Fees / mo |
|---|---|---|---|
| BRD-OAK-L | 212 | Stranded | $318 |
| KNF-SET5 | 64 | Customer damaged | $141 |
| 3 more | 39 | Mixed | $52 |
| Campaign | Terms | Spend |
|---|---|---|
| SP · Knife set broad | 11 | $1,180 |
| SP · Boards auto | 8 | $690 |
| Other | 4 | $270 |
| ASIN | Ordered | On hand | Gap |
|---|---|---|---|
| B0C7KX… | 600 | 240 | −360 |
| B0BZQ2… | 480 | 0 | −480 |
| 2 more | 500 | 200 | −300 |
| ASIN | Ours | Winner | Since |
|---|---|---|---|
| Chef knife 8in | $59.00 | $56.49 | Sat |
| Honing steel | $24.99 | $23.90 | Sun |
| Oak board M | $42.00 | $39.99 | Mon |
The PPC lead lives in #ppc, the warehouse team in #amazon-ops, finance in its own corner. With DataDoe behind Claude Tag, each of them asks in their channel and the answer stays in a thread where the rest of the team can read it, push back or follow up. Click a channel to see the kind of ask it gets.
Pick the channel where Amazon questions already pile up, add Claude there, and widen access once the team trusts the answers.
Send @Claude what can you access from this channel? and it lists the connectors that apply there, DataDoe included.
Once Claude is in a thread it reads every reply, so “now split that by marketplace” needs no new mention.
Claude Tag can take standing work: a job on a schedule, or a watch over a channel. Describe it once in the channel where it should post, and DataDoe supplies fresh Amazon numbers every time it runs. Here is a week one Amazon team set up.
@Claude every weekday at 9am Eastern, post yesterday’s Amazon sales, ad spend and any SKU under 14 days of cover in this channel. Five lines, one per marketplace.
Sales, net margin and ad spend by marketplace, and the three biggest moves with a reason each.
Terms with spend and no orders, staged as negatives for the PPC lead to approve.
New Amazon purchase orders against stock on hand, with a suggested reply per line.
ASINs that lost the offer since the last run, with who won it and at what price.
The latest settlement matched to orders, refunds and fees, gaps listed by order.
.svg)
@Claude !routines for the list. Anyone in the channel can pause or move one.A shared channel is a good place to propose a change to Amazon and a bad place for anyone to push one through. Three layers decide who can, and the strongest one sits in DataDoe, outside Slack.
Each kind of change, from prices to bids to shipments, stays off in DataDoe until you turn it on. A dry run validates a change without sending it, and every Action that does run is logged.
The shared DataDoe connector only exists in the channels its bundle names. Keep it in #amazon-ops, out of guest and Slack Connect channels. Your personal connector asks you before it is used, and can hold each result for your review.
Tell Claude who signs off, and it keeps that in the channel’s memory for every thread. It is a working rule, not a lock, which is why the two layers above it matter.
The rule lives in #ppc’s memory, and anyone in the channel can ask Claude to show or change it.
The first time a request of yours needs your own DataDoe connector, Slack shows you this prompt and no one else.