What a custom connector can do inside Claude.
Most people think a connector means Claude can read your data and answer in text. It can also hand back a working panel: a table you can sort and filter, a policy answer with its source, an approval queue, a form it filled in for you. Pick a seat below, pick a question, click around. One connector, five jobs.
Claude called a tool. The connector answered with a panel.
You asked in plain English. Claude picked the right tool and the connector did the work: a read-only SQL query, a search of the policy handbook, a list of refund requests, or a ticket draft. Instead of pasting the answer as text, it handed back a panel built for that job.
Four panels in this demo: a table with a chart and drill-in, a policy answer with the source highlighted, an approval queue with the rule on each row, and a form Claude fills in that you confirm.
Your people stay in the tool they already use.
No new dashboard to learn, no export to Excel. Support asks what's stuck and gets the list, clickable. A new agent asks about policy and gets the actual section, not a guess. Billing approves refunds with the rule right there. Same connector, same permissions, in the chat window they already have open.
Claude handles the words. The panel handles the clicks. The important actions, like creating a ticket or approving money, wait for a human to press the button.