Search approved mailboxes alongside calendars, files, tickets and chat. Linkence returns cited answers from mail and uses the same evidence to ground reply drafts, classification and follow-ups, with a person approving every sensitive send.
Gmail connects through an admin-defined boundary. Each object type below lists what Linkence reads, the scope condition that applies and the limitation you should know about before the first sync. Your Gmail account remains the system of record.
Subject, body, participants and labels
Approved mailboxesText content of supported attachments
Approved mailboxesOnly extractable content is searchableOpen loops, promised dates and pending replies
Approved mailboxesFind · Prepare · Act
Pair Gmail with Google Calendar, Google Drive, Slack and the answer stops being a search result. Evidence arrives from every connected system, and the next step waits for your approval.
A cited reply draft with the account context attached
Review and sendThe exact thread, date and owner, cited
Bring one of these to the demo on representative data. Every answer arrives with citations that open the original Gmail record.
Every answer reflects the verified connector behaviour, never generalised.
Approved mailboxes and labels chosen by an admin; Incremental sync after the initial import; Grounded drafts, classification and follow-up tracking.
Personal mailboxes outside the approved scope; Sending any email without human approval; Attachments that cannot be text-extracted.
Incremental sync with live actions on approved threads. Scope: Admin-approved mailboxes and labels.
Only verified, approval-gated writes: send a reviewed reply; apply labels and classification; schedule a follow-up reminder. Every sensitive change is prepared, policy-checked and held for a person before execution.
We will show how Linkence finds the relevant context, presents the work and keeps every sensitive change under your team's control.
Representative data is enough for the first demo. No production access required.