API integrations on the roadmap: what's possible
Agentric Team ·
v1 answers calls and chats and books into Google Calendar — deliberately. The architecture underneath is designed for more, and here's the honest map of where it goes.
Already integrated
- Google Calendar — availability + bookings, OAuth-connected.
- Stripe — subscriptions, affiliate payouts.
- Email — transactional (confirmations, notifications).
- Telephony — Twilio-compatible SIP/webhook providers (Twilio, Plivo, Telnyx-class).
Natural next integrations
- Booking platforms. Fresha, Treatwell, Calendly-style flows — "send booking link" tools already exist as a fallback; native integration is the clean extension point.
- Calendars beyond Google. Microsoft 365/Outlook is the obvious next — same OAuth pattern, different provider adapter.
- SMS/WhatsApp. Post-call confirmations, reminders, the "we've received your enquiry" touch — inbound-safe messaging.
- CRMs. HubSpot/Pipedrive-style: contact + enquiry sync so your CRM sees what the assistant captured.
- Trade-specific software. Job management tools (ServiceM8-class), salon systems, practice managers — the vertical integration layer.
The extension seams (for the curious)
The runtime is channel-agnostic: chat and voice are adapters onto the same agent loop. New channels follow the same pattern — a new adapter, same brain. Same for tools: create_booking is a function signature, and new tools (payments, order status, ticket creation) slot into the registry the same way.
What we won't build
- Outbound marketing calls or cold SMS — intentionally out of scope (the legal exposure and spam-shaped incentives aren't worth it).
- A full multi-page website builder in v1 — the landing page + widget covers the practical case; a fuller builder is the flagged extension point.
How requests shape it
Integration priorities come from what customers actually need — the message inbox and the feature-flag system are how real demand becomes the roadmap.