Connect what you have. Same customer, one record.

Read-only. What is open today is marked; the rest says Coming soon.

Six systems, one vocabulary

Sources / identity / vocabulary

A natural key: a phone first, then an email, then the system's own id. Two systems that share one become one record. Two that do not stay apart, rather than being guessed together.

When two arrivals are one record

Two arrivals. One record, or two.

Pick a case

Local and international: kept apart, no country guessedSame email in Gmail and HubSpot: one recordSame name, different phones: kept apartRebuilt twice: nothing changesA phone in WhatsApp, the same person's email in Gmail: two records todayThe same number in WhatsApp and Salesforce: one record

Gmail
M.Rivas@example.com
email:m.rivas@example.com
HubSpot
m.rivas@example.com · +57 300 ··· 2233
email:m.rivas@example.com

1 record

1 record · same key

Checked against backend/tests/fixtures/identity_cases.jsonRuns in your browser on the illustration's data. Nothing is sent and no engine is called.

A phone, then an email, then the system's id. Never a guess.

What connects today

Each one read-only. Anything OnDuty does back is an action, and an action goes through the gate.

CRM

Available
HubSpot
Available
contacts, companies, deals
Details
People and companies reconciled; deals sit under their company. No email, left out.
Keyed on
Customeremail:<address>
Companydomain:<domain> · company:<name>
Opportunityhubspot.deal:<id>
Scopes it asks for
crm.objects.contacts.read
crm.objects.companies.read
crm.objects.deals.read
Signs in through hubspot
Coming soon
Salesforce
Coming soon
accounts, contacts, leads, opportunities
Details
The same reconciliation as HubSpot, against another system of record.
Keyed on
Customerresolve: phone:… · email:… · salesforce.record:<id>
Companydomain:<domain> · salesforce.account:<id>
Opportunitysalesforce.opportunity:<id>
Scopes it asks for
api
refresh_token
Signs in through salesforce
Coming soon
Outlook Contacts
Coming soon
the contacts folder, read as customers
Details
A contact with a phone or an email becomes a customer; the rest are counted.
Keyed on
Customerresolve: phone:… · email:… · outlook_contacts.record:<id>
Companycompany:<name>
Scopes it asks for
Contacts.Read
Signs in through microsoft

Needs setup
Gmail
Needs setup
threads, people, message text
Details
Conversations as entities, with message and attachment text to quote from.
Keyed on
Personemail:<address>
Conversationgmail.thread:<id>
Scopes it asks for
gmail.readonly
Signs in through google
Coming soon
Outlook Mail
Coming soon
conversations, people, message text
Details
Gmail's treatment on Microsoft 365. Attachments are listed, not read.
Keyed on
Personemail:<address>
Conversationoutlook_mail.conversation:<id>
Scopes it asks for
Mail.Read
Signs in through microsoft

Calendar

Needs setup
Google Calendar
Needs setup
events and attendees
Details
Who met whom and when. A CRM almost never has it.
Keyed on
Personemail:<address>
Meetinggoogle_calendar.event:<id>
Scopes it asks for
calendar.readonly
Signs in through google
Coming soon
Outlook Calendar
Coming soon
events and attendees
Details
Who met whom and when, from Outlook. Rooms and equipment left out.
Keyed on
Personemail:<address>
Meetingoutlook_calendar.event:<id>
Scopes it asks for
Calendars.Read
Signs in through microsoft

Files

Needs setup
Google Drive
Needs setup
files, text, owners
Details
Files linked to their owners, with the text of Docs, Sheets, PDFs and Word. Images, video and files over 10 MB are left out.
Keyed on
Personemail:<address>
Filegoogle_drive.file:<id>
Scopes it asks for
drive.readonly
Signs in through google
Coming soon
OneDrive and SharePoint
Coming soon
files, text, who may open them
Details
OneDrive and SharePoint files, readable by whoever Microsoft says can open them.
Keyed on
Personemail:<address>
Fileonedrive.file:<id>
Scopes it asks for
Files.Read.All
Signs in through microsoft

Team chat

Needs setup
Telegram groups
Needs setup
the groups your bot is in
Details
From the moment your bot joined. A bot cannot read history.
Keyed on
Conversationtelegram.conversation:<bot>:<chat>
Scopes it asks for
None: no provider is asked for a grant
Still owed
Built, not yet exercised against Telegram groups.
Coming soon
Slack
Coming soon
the channels and messages you choose
Details
Readable in OnDuty by exactly the people who can read it in Slack.
Keyed on
Personemail:<address>
Conversationslack.conversation:<team>:<channel>
Scopes it asks for
channels:read
groups:read
im:read
mpim:read
channels:history
groups:history
im:history
mpim:history
users:read
users:read.email
files:read
team:read
Signs in through slack
Coming soon
Microsoft Teams
Coming soon
teams, channels, chats, channel files
Details
Delegated permissions only: OnDuty reads what the connecting person can read.
Keyed on
Personemail:<address>
Conversationteams.conversation:<tenant>:<id>
Scopes it asks for
Team.ReadBasic.All
Channel.ReadBasic.All
ChannelMessage.Read.All
TeamMember.Read.All
ChannelMember.Read.All
Chat.Read
ChatMember.Read
Files.Read.All
Signs in through microsoft

Marketing

Needs setup
Facebook Pages
Needs setup
posts, comments, reviews
Details
What the business posts and who answers in public. Commenters stay apart from customers.
Keyed on
Pagemeta.page:<id>
Commentermeta.user:<id>
Scopes it asks for
pages_show_list
pages_read_engagement
pages_read_user_content
Signs in through meta
Still owed
Meta's App Review per permission; until then, the app's own admins only.
Needs setup
Instagram
Needs setup
media, likes, comments
Details
Recent posts with counts, and the people who comment. Replying is not asked for.
Keyed on
Accountmeta.instagram:<id>
Commentermeta.instagram_user:<id>
Scopes it asks for
instagram_basic
pages_show_list
Signs in through meta
Still owed
Meta's App Review, as for Facebook Pages.
Needs setup
Google Business Profile
Needs setup
locations, reviews, replies, rating, performance
Details
One or two stars with words is a complaint. OnDuty only reads, though Google offers read-write.
Keyed on
Locationgoogle_business_profile.location:<name>
Reviewergoogle_business_profile.reviewer:<review>
Scopes it asks for
business.manage
Signs in through google
Still owed
Google must grant the project Business Profile API access; the quota is zero until then.
Needs setup
Google Analytics
Needs setup
properties, daily traffic by channel
Details
Sessions, users, key events and revenue by channel, source, campaign and page.
Keyed on
Analytics propertygoogle_analytics.property:<id>
Scopes it asks for
analytics.readonly
Signs in through google
Needs setup
Google Search Console
Needs setup
sites, clicks, impressions, position
Details
How the business shows in Google Search each day. A three-place drop is a signal.
Keyed on
Search Console sitesearch_console.site:<site>
Scopes it asks for
webmasters.readonly
Signs in through google
Needs setup
YouTube
Needs setup
channel, videos, daily views
Details
The channel, recent videos as documents, and daily views, watch time and subscribers.
Keyed on
Channelyoutube.channel:<id>
Videoyoutube.video:<id>
Scopes it asks for
youtube.readonly
yt-analytics.readonly
Signs in through google
Needs setup
Facebook and Instagram insights
Needs setup
Page and Instagram reach, engagement
Details
Daily views, reach, engagement and follows, on the same nodes as Pages and Instagram.
Keyed on
Pagemeta.page:<id>
Accountmeta.instagram:<id>
Scopes it asks for
pages_show_list
pages_read_engagement
read_insights
instagram_basic
instagram_manage_insights
Signs in through meta
Still owed
Built, switched off: Meta's App Review for the insights permissions.

Advertising

Needs setup
Meta Lead Ads
Needs setup
lead-form fills, filed under known customers
Details
A lead lands on the customer the CRM or WhatsApp already knows.
Keyed on
Leadresolve: phone:… · email:… · meta_lead.record:<id>
Scopes it asks for
leads_retrieval
pages_show_list
pages_read_engagement
pages_manage_ads
ads_management
Signs in through meta
Still owed
Built, switched off: Meta's App Review for leads_retrieval and its Page and ads permissions.
Needs setup
Meta Ads
Needs setup
campaigns, ad sets, ads, spend, results
Details
Spend, reach, clicks, leads and purchases per closed day. A 40 percent spend rise on the prior week is a signal.
Keyed on
Campaignmeta.campaign:<id>
Ad setmeta.adset:<id>
Scopes it asks for
ads_read
Signs in through meta
Still owed
Meta's App Review, and full-access Marketing API for accounts beyond the owner's.
Coming soon
Google Ads
Coming soon
campaigns, ad groups, keywords, spend
Details
Spend, clicks and conversions per closed day. Signals state only what the data states.
Keyed on
Accountgoogle_ads.customer:<id>
Campaigngoogle_ads.campaign:<id>
Ad groupgoogle_ads.ad_group:<id>
Scopes it asks for
adwords
Signs in through google

Accounting

Coming soon
QuickBooks
Coming soon
customers, invoices, payments
Details
Who owes what since when, reconciled with the CRM and the inbox.
Keyed on
Customerresolve: phone:… · email:… · quickbooks.record:<id>
Companycompany:<name>
Invoicequickbooks.invoice:<id>
Scopes it asks for
com.intuit.quickbooks.accounting
Signs in through intuit

Databases

Available
Postgres
Available
one SELECT, read-only transaction
Details
Tables read with a timeout and a row budget. MySQL and SQL Server are not built.
Keyed on
Recordresolve: phone:… · email:… · <system>.record:<id>
Scopes it asks for
None: no provider is asked for a grant

Your own systems

Available
Push records
Available
your system posts entities and signals
Details
A token for one source opens one route. Not a developer API.
Keyed on
Recordresolve: phone:… · email:… · <system>.record:<id>
Scopes it asks for
None: no provider is asked for a grant
Available
Read an API
Available
any https JSON API, on a schedule
Details
Base URL, auth header, paging and field mapping. Private addresses are refused.
Keyed on
Recordresolve: phone:… · email:… · <system>.record:<id>
Scopes it asks for
None: no provider is asked for a grant
Available
A CSV file
Available
a CSV export, mapped to entities
Details
The export every system can produce. Mapped columns become entities and memories.
Keyed on
Recordresolve: phone:… · email:… · <system>.record:<id>
Scopes it asks for
None: no provider is asked for a grant

Where it answers

Available
Workspace chat
Available
your members, at your own address
Details
The workspace's own chat, members only, on every plan. With no agent bound, the Brain answers.
Keyed on
Customeronduty.customer:<row>
Scopes it asks for
None: no provider is asked for a grant
Available
Telegram
Available
your own bot, reads and replies
Details
A bot your workspace makes with BotFather. Every reply is evaluated before it is sent.
Keyed on
Customeronduty.customer:<row>
Scopes it asks for
None: no provider is asked for a grant
Needs setup
WhatsApp
Needs setup
your business number, reads and replies
Details
Conversations on the number you already publish. A reply is an action, evaluated first.
Keyed on
Customerphone:<number>
Scopes it asks for
whatsapp_business_management
whatsapp_business_messaging
Signs in through meta
Still owed
Built, not yet exercised against Meta; its messaging review is not submitted. We set it up with you.
Coming soon
Slack
Coming soon
mentions and direct messages, as the member
Details
Answers where you turn it on. Every reply is evaluated before it is sent.
Keyed on
Customeronduty.customer:<row>
Scopes it asks for
app_mentions:read
chat:write
Signs in through slack
Coming soon
Microsoft Teams
Coming soon
a bot in Teams, as the member
Details
Answers messages and mentions in channels you turn on. Every reply is evaluated first.
Keyed on
Customeronduty.customer:<row>
Scopes it asks for
None: no provider is asked for a grant

What it does

Available
Your own endpoint
Available
writes: only the actions you declare
Details
Your endpoint. The gate evaluates; only a clean permit calls it. Premium and up.
Keyed on
Writes nothing into the Brain
Scopes it asks for
None: no provider is asked for a grant

Available Needs setup Coming soon

Any assistant that speaks MCP reads with a key you issue and can never accept, execute or send. Signing in from Claude or ChatGPT is built, not yet exercised live. The public agent chat is not a connector either.

Missing a system? Tell us. A new connector is work, not a switch.

How a sync behaves

Situation	What happens	Why
The run reaches its record budget	Saves its position and continues.	Nothing times out at ninety percent.
A run fails	Saves its cursor too.	Recovery never rereads what worked.
A grant is revoked	Stops, and says so.	Retrying cannot fix a revoked grant.
A rate limit or a blip	Backs off and retries.	A blip is not a revocation.

Two records about every source

Record	What it holds	On disconnect
The live plumbing	Credential, cursor, schedule.	Deleted at once.
Where knowledge came from	Which source produced each memory and insight.	Survives, marked no longer connected.

A claim you cannot check is worse than no claim.

Connect one system and see what it already knows.

Start free Talk to us

Connect what you have. Same customer, one record.

Six systems, one vocabulary

When two arrivals are one record

What connects today

HubSpot

Salesforce

Outlook Contacts

Gmail

Outlook Mail

Google Calendar

Outlook Calendar

Google Drive

OneDrive and SharePoint

Telegram groups

Slack

Microsoft Teams

Facebook Pages

Instagram

Google Business Profile

Google Analytics

Google Search Console

YouTube

Facebook and Instagram insights

Meta Lead Ads

Meta Ads

Google Ads

QuickBooks

Postgres

Push records

Read an API

A CSV file

Workspace chat

Telegram

WhatsApp

Slack

Microsoft Teams

Your own endpoint

How a sync behaves

Two records about every source

Connect one system and see what it already knows.