Everyone's talking about connecting AI to their tools. Claude Code, MCPs, "just chat with your data." If you're not technical, it can sound like a wall you're not allowed past.
It isn't.
We connected Claude Code to our own LinkedIn signal data, with no coding, and had it build a live GTM dashboard in about 20 minutes. The person doing it is a marketer who didn't know what an API key was a couple of months ago. We recorded the whole thing, mistakes and all.
Below is the written version so you can follow along at your own pace. The exact prompts and the finished dashboard are free in our community, linked at the bottom.
What you'll need
- A Teamfluence API key. Create a new one under Signal Processing - API Keys. Treat it like a password.
- Claude Code, the desktop app or the terminal version. Either works.
That's the whole setup. No environment to configure, no code editor.
Step 1: Point Claude Code at your workspace
Open Claude Code and tell it, in plain English, that you want to connect to your Teamfluence workspace. Paste your workspace URL and the link to Teamfluence's API documentation. This makes Claude look for the API instead of clicking around a screen like a human would.
It'll go read our API docs on its own and come back knowing how to connect without a browser.
Step 2: Give it your API key
Claude will ask for your API key. You can either paste the API key directly in the chat (with precaution) or add your API key as an environment variable if you are using the terminal.
Once it's in, Claude connects.
Step 3: Ask what you can do
You don't need to know the API to use it. Once connected, just ask: "give me a list of everything I can do here, as if I were a GTM engineer."
Claude will read our documentation and hand you a menu: pull leads, see who engaged with a post, track signal types, push data to a CRM. You pick.
Step 4: Build something in one sentence
We asked for a GTM performance dashboard for the last 30 days just with one sentence. Claude pulled the real data from the leads endpoint and built the whole thing: signals captured over time, where they came from, how many qualified, capture by team member, top geographies, and the highest-intent leads ranked by engagement.
It also read the numbers back and told us what they meant. An actual read on our GTM.
What Claude figured out on its own
You never touch this, but for the curious, here's what it discovered by reading the docs:
- API base: https://api.teamfluence.app
- Auth: a Bearer token (your API key)
- The endpoint it used: GET /external/{your-profile}/leads
The takeaway
The barrier to this used to be "can you code." It isn't anymore. It's "can you describe what you want." If a marketer who didn't know what an API key was can build a live pipeline dashboard in 20 minutes, you can too.
Grab the exact prompts we used and the dashboard file, free → Join our Community