What Lumela connects to
Lumela measures the return on AI from the systems your teams already work in. It only ever reads from them.
Gmail
What it shows. Whether your teams reply to people faster since they started using AI.
What we need. A Google Cloud OAuth client ID, then one click to connect each mailbox. The access Lumela asks for can read message metadata, such as who sent what and when, and cannot read message content.
HubSpot
What it shows. Whether AI is helping your sales team win more, and which reps are using it.
What we need. One read-only HubSpot key, and a yes/no property on deals and contacts to mark AI use.
Jira
What it shows. Whether AI-assisted tickets get resolved faster than the rest, and which agents use it.
What we need. Your Jira site, an API token, and a label on AI-assisted tickets.
GitHub
What it shows. How much of your delivered work is AI-assisted, and whether it ships faster.
What we need. A read-only token and the list of repositories to include.
Where your data goes
Records are fetched when you open a report, turned into figures, and discarded. Nothing from these systems is written to Lumela’s database.
The history matters as much as the present. Each of these systems kept timestamps from long before AI arrived, which is where the before-and-after comparison comes from. Our guide to measuring AI ROI explains the method.
Running agents somewhere else?
If your agents live in Copilot Studio, Power Automate, AWS or a tool of your own, tell us on a walkthrough. We’ll be straight about what we can read from it today.