Day.ai integration
Day.ai keeps the context around a deal — calls, threads, what was actually said. Swoop watches the numbers it reports and asks the people behind them why.
Day.ai metrics Swoop can read
Read-only, and only what you point it at.
- One tool call per source
- Whatever metric that tool returns
- Read-only; nothing is written back
History arrives on connect. Day.ai hands over past values, so signals can appear on the first sync.
Connecting it
A couple of minutes. Day.ai's MCP endpoint and an access token, both from their MCP page. We'll list the server's tools so you can pick one.
- 01MCP endpoint
The MCP server address Day.ai gives you at day.ai/mcp.
- 02Access tokenoptional
If Day.ai issues one for the endpoint. Leave blank if the URL already carries your authorisation.
- 03Tool to call
We'll list the server's tools when you connect, so you can copy the exact name.
- 04Name this metric
What to call it in Signals.
- 05Where the rows areoptional
Dotted path to the array of points in the tool's result. Blank if it returns the array directly.
- 06Choose what it may watch
Every source states what it is allowed to look at. Ingesting everything available is how this becomes another dashboard nobody opens.
Credentials are encrypted and used read-only — nothing is ever written back to Day.ai. Answers are synthesized by an open-weights model on Amazon Bedrock, so no foundation-model vendor sees your data; Enterprise runs that model in your own AWS account.
Include Day.ai metrics in Swoop panels
Free to start, and you only pay for panels that answer.
Start free