Native connector
A direct, authorised connection. You grant scoped access once; Kaer reads and writes through the service's own API or protocol, and you can revoke it at any time.
7 services
Via Kaer Computer
No API needed. Kaer signs in and uses the web app in its own browser session, the same way your team does — with the same approval gates before anything is sent, paid or published.
22 services
Planned
On the roadmap and not connectable yet. Until it ships, Kaer can still operate the service through Kaer Computer.
4 services
Mail & calendar
GmailReads messages and sends mail through your Google account, so the agent can act on a thread.Native connector
IMAP mailboxesConnects a mailbox you already have to Kaer Mail — triage, drafts and approvals on your own domain.Native connector
Google CalendarReads availability, offers times, books and reschedules appointments.Native connector
CalendlySends booking links and confirms the slots that stick.Via Kaer Computer
Files & docs
Google DriveOpens and files the documents it creates — quotes, reports, onboarding packs.Native connector
Google SheetsReads and updates spreadsheets — trackers, price lists, recurring reports.Native connector
NotionReads your internal knowledge base before it answers a customer.Planned
Google DocsDrafts and edits documents in the browser.Via Kaer Computer
DropboxFiles and retrieves documents where your business already keeps them.Via Kaer Computer
Communication
SlackPosts updates, asks for approvals, and picks up work from a channel.Native connector
Google MeetCreates meeting links when booking an appointment.Via Kaer Computer
ZoomBooks meetings and pulls attendance for follow-ups.Via Kaer Computer
Money & billing
StripeInvoice status, payment chasing and revenue reporting.Planned
PayPalChecks what's been paid so the chasing list stays accurate.Via Kaer Computer
SquarePulls takings and payment status into recurring reports.Via Kaer Computer
QuickBooksRaises invoices, checks what's outstanding, prepares the month-end pack.Via Kaer Computer
XeroReconciles, chases overdue invoices, builds the numbers for a report.Via Kaer Computer
Customers & sales
HubSpotLogs enquiries, updates deals, keeps the follow-up sequence moving.Via Kaer Computer
SalesforceReads the account before replying; records what happened after.Via Kaer Computer
MailchimpPrepares a campaign and holds it for your approval before sending.Via Kaer Computer
IntercomDrafts answers to inbound conversations using your own policies.Via Kaer Computer
ZendeskTriages tickets and drafts the reply an agent approves.Via Kaer Computer
Work tracking
LinearCreates and updates issues from enquiries and incidents.Planned
TrelloMoves work through the board as each step completes.Via Kaer Computer
AsanaCreates tasks from enquiries and closes them when the work is done.Via Kaer Computer
AirtableReads and updates the base your operations already run on.Via Kaer Computer
ZapierTriggers the automations you have already built.Via Kaer Computer
Websites & storefronts
ShopifyOrder status, stock checks and customer enquiries about a purchase.Via Kaer Computer
CanvaProduces the recurring graphics a campaign needs.Via Kaer Computer
WordPressPublishes and updates pages — held for approval before anything goes live.Via Kaer Computer
SquarespaceEdits site content and product listings.Via Kaer Computer
Software
GitHubReads the repository, opens pull requests, runs against your existing CI.Native connector
FigmaReads designs when building the interface for an internal tool.Planned
Why two kinds
An API is faster. A browser is universal.
Where a service offers an API and we have built the connector, Kaer uses it — it is quicker, more reliable and easier to scope. Where it does not, Kaer signs in and uses the web app in a Kaer Computer session, which means the long tail of business software works without waiting for anyone to build anything.
- Native connections are scoped per tool and revocable individually
- Browser sessions are isolated per run and destroyed after
- Both paths pass through the same approval gates before anything consequential
Integrations, answered.
What does “planned” actually mean?
It is named in the product's own connector catalogue and not connectable yet. Until it ships, Kaer can still operate the service through Kaer Computer — so a planned label is about how it connects, not whether the work can be done.
Is a browser session less secure than an API connection?
It is scoped differently. A native connection carries explicit, revocable API scopes. A browser session runs in an isolated machine that is destroyed when the run ends, using credentials you granted for that purpose. Both are recorded, and both stop at the same approval gates.
Can Kaer work with our internal system?
If a person can use it in a browser, usually yes — that is the point of the browser path. Systems behind a VPN or with unusual sign-in need a conversation first.
How do I revoke access?
Per tool, at any time, from the connectors screen. Revoking one connection does not affect the others.
Connect one tool.
Hand over one job.
A mailbox and a calendar is enough to start. Everything else can wait until you have seen it work.
