Foqal turns Slack and Microsoft Teams channels, plus email and web chat, into tracked helpdesk tickets, with routing, assignment, and feedback scoring. Connecting Foqal to clariBI puts that chat-native support workload next to the revenue, headcount, and customer data it touches.
Why connect Foqal
When support lives inside Slack and Teams threads, volume, resolution time, and satisfaction are hard to measure without reading the channels by hand.
With Foqal connected, you can ask "How many tickets did each team close last month?", "What are the most common request topics across our Slack channels?", or "How did CSAT trend after we changed the on-call rotation?" and the AI engine reads it live.
How the connection works
clariBI talks to Foqal through its hosted MCP server at . Authentication uses an API key you generate in your vendor account. Tokens stay encrypted server-side and never leave clariBI in clear form.
sequenceDiagram
actor U as You
participant C as clariBI
participant V as Foqal
U->>V: Generate an API key in Foqal dashboard
U->>C: Paste the key into the connect wizard
C->>V: list_tools (verify the key)
V-->>C: Tools available
C->>C: Encrypt and store credentials
C-->>U: Connection ready
Available tools
clariBI exposes the read-only Foqal tools that the vendor's MCP server publishes at connection time. Write operations (create, update, delete, send, refund) are filtered out by a name-pattern blocklist before any tool reaches the analysis engine, so connecting Foqal cannot modify data on the vendor side.
The exact tool inventory depends on the Foqal features your account has access to. After connecting, try a few natural-language questions to see what Foqal data clariBI can pull.
Data flow during analysis
When you ask a question that maps to Foqal, the AI engine routes to the right tool, reads the result, and pairs the answer with a chart you can pin to a dashboard.
sequenceDiagram
actor U as You
participant C as clariBI
participant AI as AI engine
participant V as Foqal
U->>C: Ask a question about chat-based helpdesk and ticket data
C->>AI: Plan the analysis
AI->>V: Call the right tool
V-->>AI: Tool result
AI->>AI: Summarize and chart
C-->>U: Answer plus visual
Setting up the connection
- Open Data Sources in the clariBI sidebar.
- Click Add data source.
- Open the MCP Servers tab.
- Click the Foqal card.
- In Foqal, open your workspace settings and generate a token with read access.
- Paste the token into clariBI and click Connect.
- Give your data source a name and click Finish.
Permissions and data access
clariBI authenticates with the Foqal MCP token you paste and reads tickets, topics, assignments, resolution timelines, and feedback scores. The catalog exposes read tools only; clariBI never opens, assigns, reopens, or closes a ticket. Rotate the token in Foqal, or disconnect from Settings → Integrations in clariBI.
Troubleshooting
| Error | Cause | Fix |
|---|---|---|
| "Invalid token" | The key was revoked in Foqal or copied with trailing whitespace. | Generate a fresh read-access token in your Foqal workspace settings and paste it again with no extra spaces. |
| "No tickets returned" | The connected key is scoped to a workspace or spoke without tickets in the window, or the Hub and Spoke setup routes them elsewhere. | Widen the time range and confirm the token covers the workspace whose tickets you expect. |