> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoflo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations Overview: Connect Neoflo to Your Tech Stack

> Neoflo connects to your existing ERP, CRM, and business systems using pre-built connectors and an API-first architecture — no new software required.

Neoflo fits into your existing technology stack without asking you to replace or reconfigure anything. It pulls data from your systems, processes it using agentic AI and human expertise, and pushes the completed results back — whether that means posting a journal entry in SAP, closing a ticket in Zendesk, or updating an invoice record in NetSuite. You do not install new software or manage additional infrastructure. Neoflo handles the integration layer so your team keeps working in the tools they already know.

## Two ways to connect

Neoflo offers two integration paths to cover virtually any business system:

**Pre-built connectors** are ready-made integrations for the most common ERP, CRM, and helpdesk platforms. These connectors are maintained by Neoflo, tested against each platform's latest API version, and require no custom development on your side.

**API connectivity** covers any system not included in the pre-built connector library. If your platform has an API, Neoflo can integrate with it. This path is designed for proprietary tools, custom-built ERPs, legacy systems, and any business application unique to your environment.

## Integration setup timeline

Integration configuration happens as part of Neoflo's standard four-week go-live process. During weeks one and two, Neoflo's integration team works with you to establish system access, configure connectors, map data fields, and validate data flows. By week four, your integrations are live and processing real work. You do not need internal engineering resources to complete setup — Neoflo's team manages the technical configuration end to end.

## Explore integrations by category

<CardGroup cols={2}>
  <Card title="ERP Systems" icon="building-columns" href="/integrations/erp-systems">
    Connect SAP, Oracle ERP Cloud, or NetSuite to automate invoice processing, journal entries, reconciliations, and financial close.
  </Card>

  <Card title="CRM & Helpdesk" icon="headset" href="/integrations/crm-helpdesk">
    Connect Salesforce or Zendesk to automate ticket handling, customer support workflows, and order-to-cash operations.
  </Card>

  <Card title="API Connectivity" icon="plug" href="/integrations/api-connectivity">
    Integrate any system using Neoflo's API-first layer — ideal for proprietary tools or platforms not covered by pre-built connectors.
  </Card>

  <Card title="Security & Compliance" icon="shield-halved" href="/security/overview">
    All integrations operate under Neoflo's SOC 2 Type II, ISO 27001, GDPR, and CCPA compliance framework.
  </Card>
</CardGroup>

## Supported platforms

The table below lists platforms with pre-built Neoflo connectors and the back-office processes each integration supports.

| Platform           | Category        | Supported Processes         |
| ------------------ | --------------- | --------------------------- |
| SAP S/4HANA & ECC  | ERP             | Finance Ops — P2P, R2R, O2C |
| Oracle ERP Cloud   | ERP             | Finance Ops — P2P, R2R, O2C |
| NetSuite           | ERP             | Finance Ops — P2P, R2R, O2C |
| Salesforce         | CRM             | Customer Support, O2C       |
| Zendesk            | Helpdesk        | Customer Support            |
| QuickBooks         | Accounting      | Finance Ops                 |
| Microsoft Dynamics | ERP / CRM       | Finance Ops                 |
| ServiceNow         | ITSM / Helpdesk | Customer Support            |

<Note>
  Don't see your system in the table? Neoflo's API-first architecture supports custom integrations for any platform with an available API. [Learn more about API connectivity](/integrations/api-connectivity) or contact your Neoflo account team to discuss your stack.
</Note>