Pull from any operation — a door, a camera, a cardholder, anything your systems hold. Tick what the incident concerns. Leave empty for everything that happened at that time.
Add an API connector
Workspace
Everything below is set up for the workspace you're in. Switch before configuring a customer.
Your connectors
Workspace actions
Capabilities usable with any connector — e.g. email a report.
Recipes
One-click flows: run a report, then email it (PDF) or post it to Slack/Teams. Needs a data-source connector and a configured action.
Site model
One entry per real thing — a door, camera, zone — and the id each system knows it by. An id only works in the system that issued it, so this is how a question can cross from an access event to the camera that saw it. Looked up on demand, never loaded into every conversation.
Incident report sources
Which reads an incident report pulls. Ticked by default from the ones that look like a feed of events — untick anything irrelevant, or tick a feed we guessed wrong about.
Alerts
Watch for something and notify — no polling the model. Poll a read tool on an interval (cursor-based, cheap), or receive a webhook. Conditions are checked in code.
Slack bot (inbound)
Two-way chat: @mention the bot in Slack to ask questions and run reports. Point your Slack app's Event & Interactivity URLs at this server.
Device / glasses access
A Bearer key for a device or app (e.g. smart glasses) to reach Cognition. The app POSTs { text } to /api/device and gets back one short line, shaped for a heads-up display.