Integrations let Oikapi exchange data and trigger actions with the external services your
company already runs — accounting, CRM, support, identity, messaging, and more. This section is
the home for every first-party integration: what it does, how to connect it, and what you can do
with it once it’s wired up.
New to integrations? Start with How Integrations Work to
understand connections, actions, triggers, and syncs. Then pick a service below.
Each integration links to its own setup-and-reference page. Status badges: GA (generally
available), Beta (usable, may change), Planned (on the roadmap, not yet shipped).
Several providers already ship first-party actions — outbound operations you can call from
Business Rules and Workflows once you’ve stored a
credential. Today that covers Slack (post a message, send a DM), GitHub (create/close
issues, comment, open a pull request, list issues), Jira (create/update issues, comment, list
issues), and Salesforce (create/update records, run a query), plus a generic outbound HTTP
action and an email send action. These are marked Beta below: the actions are wired into
the engine, but broader bidirectional sync for the same services is still Planned.
| Integration | Status | What you’d do |
|---|
| QuickBooks Online | GA | Sync chart of accounts, customers, vendors, and transactions into the finance ledger; commit staged rows via the extract→stage→commit pipeline |
| Xero | Planned | Push Oikapi invoices out as Xero invoices; sync contacts and AR/AP |
| Stripe | Planned | Sync charges, invoices, and subscriptions for MRR/AR reconciliation; issue refunds and payment links |
| NetSuite | Planned | Two-way order-to-cash: pull AR via SuiteQL, push sales orders and invoices |
| Integration | Status | What you’d do |
|---|
| Salesforce | Beta | Create/update records and run SOQL queries from rules and workflows today; bidirectional sync of Accounts, Opportunities, and Cases is planned |
| HubSpot | Planned | Two-way contact/company/deal sync; trigger onboarding on Closed-Won |
| Mailchimp | Planned | Upsert contacts into audiences; ingest opens, clicks, and unsubscribes as engagement and consent |
| Integration | Status | What you’d do |
|---|
| Zendesk | Planned | Mirror tickets into ITSM/CRM; link support volume to the affected CMDB item or account |
| Jira | Beta | Create/update issues, add comments, and list issues from rules and workflows today (e.g. open a linked issue from an incident); full status mirroring is planned |
| Integration | Status | What you’d do |
|---|
| Okta | Planned | Provision/deprovision users on join/move/leave, grant/revoke groups, reset MFA, ingest the System Log |
| Microsoft 365 (Graph) | Planned | Directory sync, managed devices as CMDB items, and Outlook/Teams as notification and approval rails |
| Google Workspace | Planned | Run a shared support inbox via Gmail; schedule change windows with Calendar and Meet |
| Integration | Status | What you’d do |
|---|
| GitHub | Beta | Create/close issues, comment, open pull requests, and list issues from rules and workflows today; repos-as-CMDB-items and deployment timelines are planned |
| Integration | Status | What you’d do |
|---|
| Slack | Beta | Post messages to channels and send direct messages from rules and workflows today; interactive approval cards with button callbacks are planned |
| Microsoft Teams | Planned | Send Adaptive Cards to channels via a Workflows webhook |
| Twilio | Planned | SMS/WhatsApp paging and OTP verification behind the notifications abstraction |
| Integration | Status | What you’d do |
|---|
| Typeform | Planned | Route every form submission into the matching table to power lead, support, or NPS intake |
| SurveyMonkey | Planned | Ingest CSAT/NPS responses; auto-open a ticket or follow-up when a score is below threshold |
| DocuSign | Planned | Send a templated envelope on Closed-Won and drive the contract record from Connect webhooks |
| Snowflake | Planned | Materialize warehouse marts (churn risk, SLA counts) into Oikapi tables for rules and Iris to act on |
Oikapi is an open platform. If there’s no first-party integration for a service, you can build
your own using the HTTP Client inside
Business Rules, store credentials securely, and react to events with
Workflows. See How Integrations Work
for the building blocks.