Skip to main content

Native Integration (AI Agent)

Let the Qontak AI Agent take real-world actions in third-party apps outside the Mekari ecosystem — Google (Calendar, Sheets), Calendly, Salesforce, Zoho, Midtrans — so the agent can close the loop inside a conversation (book the appointment, write the lead to a CRM, take the payment) instead of handing off to a human. Delivered as connect-once, use-always native integrations rather than the generic API Integration menu, so non-technical Admin/SPV users can configure them. Authentication is per-provider: OAuth for the SaaS providers, a provider token flow for Midtrans.

QA Lane

Lane B — keeps a human QA gate. Money-critical: Midtrans payment processing; and out-of-reach: third-party OAuth integrations (Google, Calendly, Salesforce, Zoho) automation can't fully drive. No E2E test specs exist for this initiative yet, so the Lane-A entry bar (100% E2E, spec-mapped coverage) is unmet regardless. Classified 2026-06-29.

One of three sibling "action" initiatives. They share one Action drawer (IA) but differ in what they target and how they authenticate:

InitiativeTargetsAuthDrawer groups
Native Integration (this)Third-party apps outside MekariOAuth / per-providerOther integration
Mekari ActionOther Mekari productsHMAC + SSO Super Admin approvalMekari Talenta / Jurnal / Desty
Qontak ActionQontak's own featuresCompany tokenMekari Qontak

Master index (ANCHOR)

  • native-integration-anchor.md — the ANCHOR PRD: the initiative master index (identity, Provider Index, decisions, Development Status). It carries no acceptance criteria of its own (those live in the provider PRDs), so it sits at the initiative root rather than under prds/. Synced with the Confluence Native Integrations ANCHOR and reconciled against code — the OAuth/provider-token foundation is largely shipped (Google OAuth2, Google Calendar provider, Midtrans OAuth); per-provider action layers are next.

History: this initiative was formerly midtrans-native-integration/ (a single-provider initiative). On 2026-06-17 it was renamed and generalized into the Native Integration umbrella, with Midtrans as the inaugural payment provider.

Providers

ProviderAuthStatusEpic
MidtransMidtrans tokenPRD draft; midtrans_oauth auth shippedBOT-4340
Google CalendarGoogle OAuth2OAuth + calendar provider shipped; booking action pendingTBC
CalendlyCalendly OAuth2PRD draft; depends on Phase 1TBC
Google SheetsGoogle OAuth2Credential type shipped; actions pendingTBD
SalesforceSalesforce OAuth2PlannedTBD
ZohoZoho OAuth2PlannedTBD

Contents

  • prds/ — provider PRDs (each with its own ACs → Jira Epic) land here.
  • rfcs/ — Request for Comments (technical design proposals).
  • tests/ — E2E / acceptance test specs.
  • delivery/ — TPM program-management docs (timeline, status, decisions).