SUPERSTORE 007

#What it is

SUPERSTORE 007 is a Tableau Next Hackathon 2026 build that takes the most-used demo dataset in analytics and pushes it past the dashboard. Orders, service cases, and social sentiment all land in Salesforce Data Cloud. Account managers see the trend, ask why, create the case, and get team confirmation — without ever leaving Slack.

The pitch is in the name. Classic Superstore tells you what happened. Bar charts, line charts, the question "why is the West region down again?" SUPERSTORE 007 is licensed to act on it. The dashboard raises the question, the agent and the flow take it the rest of the way.

What it demonstrates: agentic analytics on a dataset every Tableau person already knows by heart. Same data, different outcome. The "now what" gets answered.

#How it works

Five layers, each doing one job:

• Tableau Next — the surface where trends become questions. Same Superstore visuals you've seen a thousand times, wired to a Data Cloud source instead of a flat extract.
• Salesforce Data Cloud — the unification layer. Orders + service cases + social sentiment live in one place so the agent has actual context, not just a single fact.
• Agentforce — the investigator. Asks follow-up questions, pulls supporting records, drafts the next action.
• Salesforce Flows — the case creator. Turns the conversation into an actual record with the right owner, the right priority, the right links.
• Slack — where it all lives. The team sees the case, confirms the action, moves on. No tab-switching, no "did anyone follow up on that?"

The move here: stop building dashboards that end in questions. Build for the action on the other side. The dataset doesn't have to be exotic — the question handoff does. You can use this pattern on any operational dataset where "what should we do about it" has a real answer.

#Try this

If you've got a Salesforce dev org and some time, the recipe is short:

1. Pick the boring dataset on purpose. Superstore. Or whatever your org's equivalent is — the one everyone already understands. The point isn't novelty; it's that the action layer becomes the whole story.
2. Land it in Data Cloud, not in a flat extract. Even one source is enough to start. The unification matters more once a second source shows up — service cases, support tickets, anything that gives the agent context the dashboard alone can't carry.
3. Wire one Tableau Next view to it. Doesn't need to be pretty. Needs to be the surface where a real question gets asked.
4. Build one Agentforce action that picks up that question. Start narrow — one trend, one follow-up, one case template. Resist the urge to make the agent omniscient on day one.
5. Hand the case to a Flow that creates the record and posts to Slack. This is where it stops being a demo and starts being a thing a team would actually use.

The whole loop is the bit. You can extend any layer afterwards — richer sentiment, smarter routing, multi-step agent reasoning — but the loop has to close first. Question on the dashboard, action in Slack, no tabs in between.

What I learned building it: the dashboard doesn't have to be impressive. The handoff does.