01
Messages, threads, drafts, sending, search, labels, attachments, and repairable incremental sync.
Inbox and send
Platform
A product surface for every communication primitive.
Horato is the product-facing layer for the communication resources your customers already depend on: messages, calendars, meetings, transcripts, contacts, tasks, bookings, webhooks, and agent actions.
The communication features your customers already expect.
Horato gives your product stable APIs for the work around every customer conversation: messages, calendars, meetings, contacts, tasks, bookings, webhooks, and approvals.
02
Calendar
Events, availability, free/busy, recurrence, conference links, watch renewal, and sync token recovery.
Push plus delta
03
AI Meeting Notetaker
Start notetakers for customer meetings, retrieve post-call transcripts and recordings, and send meeting lifecycle events to your app.
Post-call transcripts
04
Contacts
People, organizations, address books, groups, multi-value fields, and dedupe support.
Customer context
05
Tasks
Task lists, completion, linked resources, external status mapping, and follow-up work from meetings or messages.
Follow-up model
06
Scheduling
Booking links, event types, slot generation, buffers, questions, reminders, and branded booking flows.
Booking API
07
Webhooks
Signed events, retries, dead-letter handling, delivery inspection, and replay for customer workflows.
Replayable delivery
08
SDKs and MCP
Typed SDKs for product teams, plus MCP tools for agents that need context and approval-gated actions.
Developer surfaces
Architecture
One model for communication data.
Horato gives your product stable resources for messages, meetings, transcripts, contacts, tasks, bookings, webhooks, and agent actions. You keep the sync, audit, and repair details your product needs without owning every integration path.
01
Account connections
Connections, permissions, sync jobs, and capability checks live behind one product API.
02
Product resources
Email, calendar, meeting notes, contacts, tasks, scheduling, and webhooks share tenant-aware models your app can depend on.
03
Reliable delivery
Changes flow through an event log before signed webhooks are delivered, retried, and repaired.
04
Approved actions
REST, SDKs, and MCP tools use the same action model, with approvals for sends, bookings, event changes, and destructive operations.
Use cases
From first message to follow-up, keep the workflow connected.
Start with one communication workflow. Horato keeps email, calendars, meeting notes, tasks, bookings, and approvals tied to the same customer context.
Active customer path
Vertical SaaS
Add email, scheduling, contacts, tasks, and meeting notes without rebuilding the same integration work for every product line.
- 01Connect accounts
- 02Sync conversations
- 03Attach meeting notes
- 04Create follow-ups
Shared account context