All help pages
Tools and asks
Every tool Claude can use in Walkoff, what it's for, and what to ask.
Example sessions
You don't need the tool names. Ask in plain words, and Claude picks the tools. A week can look like this:
And setting up what you want to hear about:
Setting your brand up from Shopify, the first time:
Things to ask
Setting up
Set up Walkoff from our Shopify store.
Update our catalog from the store.
Refresh our fan map from Shopify.
Your fans
Where are our fans?
Which teams do our customers follow?
What should we feature if the Padres win?
What's happening
What should we send this week?
Anything we should act on today?
What happened for our teams this weekend?
Did anyone from our customers' towns win this week?
What games are coming up this week?
Campaigns
Build a campaign for the top moment in our queue.
Show me a sample campaign for a Chargers walk-off.
Set up the Klaviyo segment for Chargers fans.
Log it as sent.
Skip that one.
Triggers and history
Make a trigger for walk-off and comeback wins in our top markets.
What triggers do we have?
Delete our rivalry trigger.
What did we send last month?
How did our Walkoff sends do last month?
Your brands
Which brands can I use in Walkoff?
Every tool
Every tool Claude can use in Walkoff. Read-only tools only look things up. The ones that save changes touch your catalog, your customer counts, your triggers and your send log. None of them sends anything.
import_catalog Saves changes
Reads your products from your Shopify store's public product feed: titles, types, tags, descriptions, prices, colorways, SKUs and photos. New products are added and the rest updated. No customer data.
import_customer_counts Saves changes
Makes your fan map from customer counts Claude reads in Shopify's analytics: customers by postal code, and by state or province. Walkoff keeps only each code's area and the count.
regions: The second query's state and province totals. They place the customers outside your top postal codes.
trigger_queue Read only
Your to-do list: recent moments that match your triggers, that you haven't drafted, sent or skipped. With no triggers of your own, big moments for your standout teams, and hometown moments in towns near your customers. Most urgent first, with how long each is worth acting on.
hours: How far back to look. Default 72.
build_campaign Read only
A ready-to-draft campaign for a moment: subject lines, preview text, the email, your products with links and prices, the audience, when to send, the copy rules and the steps to draft it in Klaviyo. For a hometown moment, the audience is one circle around the town.
moment_id: The moment, from the queue or recent moments.moment_type: With a team, a sample before there's a real moment.offer: An offer to feature, like "15% off with code BOLT15 through Monday".products: Your own picks to feature instead of Walkoff's.reach: Core fans only (the default), or wide to include shared markets.town: With a hometown moment type, a sample for a town, like "San Clemente, CA".radius_miles: For a hometown moment, a tighter or wider circle around the town, in miles.
get_affinity_map Read only
Where your customers over-index on fan territories: how strongly, how many customers, what each territory buys more of, and the products to feature there.
local_athletes Read only
Athletes Walkoff follows who are from towns near your customers, town by town: about how many of your customers live there, and for each athlete their team, position and how Walkoff knows where they're from. The names are for you. Campaigns celebrate the town and never name an athlete without the athlete's written OK.
limit: How many towns to show. Default 20.
recent_moments Read only
What just happened for your standout teams, or for any team you name, and in towns near your customers: walk-offs, comebacks, rivalry wins, hometown wins and the rest, each with how long it's worth acting on and what you already did with it.
team: Any team, not just your standouts.hours: How far back to look. Default 48.scope: Teams, towns or both.
upcoming_games Read only
Games coming up for your standout teams, or one team, in your fans' local time, with rivalries and big games flagged.
days: How far ahead. Default 7.
match_products Read only
Your products to feature for a team: anything made for its fans first, then the colorways closest to its colors, one per team color.
limit: How many products. Default 3.
get_territory Read only
A team's fans as a Klaviyo segment: one to three proximity circles, how well they cover the fans, and how many of your customers live there. Claude can create it in Klaviyo for you, once you say OK.
reach: Core fans only (the default), or wide to include shared markets.
create_trigger Saves changes
Saves a rule for the moments you want to act on. With no teams it follows your standout territories as they change.
moment_types: Which kinds of moments. Empty means any.teams: Which teams. Empty means your standout teams.min_intensity: Skip smaller moments. Walk-offs are about 0.9, close losses 0.5.towns: For hometown moments in and near these towns, like "San Clemente, CA". A trigger with towns takes only hometown moments.min_local_customers: How many of your customers a town needs, estimated, for its hometown moments to count.
list_triggers Read only
Your saved triggers, or Walkoff's default rule if you haven't saved any.
delete_trigger Saves changes
Deletes one of your triggers. Your send history keeps what it did.
log_send Saves changes
Records what you did with a moment: drafted, sent or skipped. Logged moments leave your queue and build your history.
status: drafted, sent or skipped.campaign_ref: The Klaviyo campaign id, so the history links to it and Claude can read how it did.
send_history Read only
What you drafted, sent and skipped, newest first, with the moment and the Klaviyo campaign behind each. Claude reads how each did from Klaviyo: recipients, clicks, orders and revenue.
days: How far back. Default 30.
list_brands Read only
The brands you can use Walkoff for, with your store, whether you're licensed to name teams, customers mapped, your catalog and your standout teams.
Ready-made prompts
Walkoff also gives Claude two ready-made prompts. If your Claude app shows connector prompts, they're under Walkoff.
- Campaign for the moment checks your queue for the best moment, builds the campaign, and shows you the subject lines, the email and the audience. When you say go, it drafts the campaign in Klaviyo and logs it.
- Set up from Shopify imports your catalog from your store and your customer counts from Shopify's analytics, then shows you your fan map. Setting up
What Walkoff tells Claude
Every connection starts with these instructions:
Walkoff turns sports moments into ready-made campaigns for brands whose customers are fans. It knows each brand's fan territories (from its own customer data), its catalog by color, and live moments from every game in its leagues: walk-off wins, buzzer beaters, comebacks, rivalry wins, heartbreakers, series wins and titles, rivalry and big-game previews. Setup, once per brand, with the marketer's Shopify connector and no files (list_brands shows setup_needed): 1. import_catalog: Walkoff reads the products from the store's public product feed. 2. Run these two queries with the Shopify connector's run-analytics-query, exactly as written: FROM sales SHOW customers WHERE shipping_country_code IN ('US', 'CA', 'GB') AND shipping_postal_code IS NOT NULL GROUP BY shipping_country_code, shipping_postal_code SINCE -365d UNTIL today ORDER BY customers DESC LIMIT 1000 FROM sales SHOW customers WHERE shipping_country_code IN ('US', 'CA', 'GB') AND shipping_postal_code IS NOT NULL GROUP BY shipping_country_code, shipping_region SINCE -365d UNTIL today ORDER BY customers DESC LIMIT 1000 3. import_customer_counts, with the first query's rows as postal_codes and the second's as regions, one row per line (country, postal code or state, customers), every row in one call. 4. get_affinity_map, to show the marketer their standout teams. Counts only: never read, ask for or pass on customers' names, emails, phone numbers or addresses, and don't use the Shopify connector's customer or order tools for this. If a query fails, fix only its syntax and keep its columns. If the tool returns only part of the rows, page with OFFSET and pass them all together. A store not on Shopify, or no Shopify connector: the marketer uploads files with the link in their welcome email. The usual flow: 1. list_brands (if a brand shows setup_needed, run Setup first), then trigger_queue for the moments to act on now. 2. build_campaign with a moment_id: subject lines, preview text, a finished email, products, the audience and when to send. 3. With the marketer's Klaviyo connector: find the audience segment (if it's missing, offer to create it from the klaviyo_segment given, and do it once they say OK), create the template and a draft campaign, and show them. Never schedule or send without their go-ahead. 4. log_send, so the queue stays clean and the history builds. 5. Results: when the marketer asks how sends did, send_history has each one's Klaviyo campaign id. Read their numbers with the Klaviyo connector (get_campaign_report): recipients, clicks, orders and revenue. They're Klaviyo's numbers, by the brand's own attribution settings. Every Walkoff campaign's name starts with "Walkoff ·", so the report can also find them by name. Copy rules: most brands aren't licensed to use team marks. For them, campaign copy never names the team, league, players, stadium or event. It nods with the city (pro teams only) and the colors, through the brand's own products. Moment headlines name teams for the marketer's eyes only. If you rewrite the copy, keep the rules that build_campaign returns. Athletes: local_athletes shows the marketer which athletes are from towns near their customers. Those names are for the marketer only. Campaign copy never names or describes an athlete (no name, number, position, school or photo) unless the brand has the athlete's written OK on file. Hometown moments: when an athlete from a town near the brand's customers wins a title, a tournament or a race, or wins a playoff game at the very end, the town gets its own moment. trigger_queue lists them with the rest, with about how many of the brand's customers live there. build_campaign makes the town's campaign: one circle around the town, and copy that celebrates the town. It never names or describes the athlete, and never names the team, league or event, unless the brand has the athlete's written OK on file. Keep that rule if you rewrite the copy. When the marketer asks how something works or hits a problem, Walkoff's help center has the answer, ready to link: https://www.walkoff.io/help. Connecting: https://www.walkoff.io/help/connect. Setting up from Shopify: https://www.walkoff.io/help/shopify. Uploading files instead: https://www.walkoff.io/help/uploads. Connecting Klaviyo, and saving a team's segment: https://www.walkoff.io/help/klaviyo. Tracking and results: https://www.walkoff.io/help/klaviyo#tracking. Messages and fixes: https://www.walkoff.io/help/troubleshooting.