Skip to content
AksharAI

Integrations

Agents are only as useful as the systems they can reach.

An invoice agent needs your purchase orders. A support agent needs order status. AksharAI connects to the systems Indian businesses already run, in two ways: ready adapters you configure in the platform, and connectors our team builds for your exact setup.

One agentSame rules,every channelWebsite chatSchool admissionsIs there a bus to Bopalfor Class 4?Yes, route 7 stops at Bopalcrossroads at 7:10 am.Logged with sourcesWhatsAppD2C kurta brandOrder 58213 kabaayega?Dispatched from Surat today.Delivery by 14 October.Logged with sourcesEmailDistributor accountsPlease share our ledgerfor September.Statement drafted. Ketanreviews it before sending.Logged with sourcesVoice callNBFC collectionsCaller asks to move theEMI date, in Hindi.Request logged. An officerwill call back today.Logged with sources

Ready adapter · 11 listed

Configured in the platform

Standard adapters for REST APIs, common databases, cloud storage, email and messaging. Someone on your team fills in the connection details and chooses what the agent may read or write. No code is written for these.

Built for you · 19 listed

Connected by our team on the project

ERPs, CRMs and HR systems vary by version and customisation, so the Code Colonies AI team connects them through the system's API, export or database. This work is bought on 2good terms: INR 199 an hour, a 150 hour minimum, and you pay after you accept it.

ERP and accounting

Where purchase orders, invoices, stock and ledgers live. Agents read from these to check work, and write drafts back only where you allow it.

  • Tally Prime and Tally ERP 9

    Read masters, POs and vouchers; prepare draft vouchers for approval. Usually through Tally's XML interface or a small connector on your Tally server.

    Built for you
  • SAP Business One and SAP S/4HANA

    Through the Service Layer or OData APIs, limited to the objects the agent needs.

    Built for you
  • Zoho Books and Zoho Inventory

    Through Zoho's REST APIs with an account scoped to the task.

    Built for you
  • Microsoft Dynamics 365 Business Central

    Through its standard APIs.

    Built for you
  • Odoo, ERPNext and in house ERPs

    Through their APIs, or a read only database view when there is no API.

    Built for you

CRM and sales

Customer records, deals, notes and quotes. Copilots read these to prepare briefs and suggest updates that a person confirms.

  • Zoho CRM

    Accounts, contacts, deals and notes, read and update with confirmation.

    Built for you
  • Salesforce

    Through the REST API with a permission set limited to what the copilot needs.

    Built for you
  • HubSpot

    Contacts, companies, deals and tickets through the HubSpot API.

    Built for you
  • LeadSquared and Freshsales

    Common with Indian sales and admissions teams, connected through their APIs.

    Built for you
  • Any CRM with a REST API

    Configured through the platform's API connector, with fields mapped in the builder.

    Ready adapter

Communication channels

Where your customers and staff already talk. The same agent can answer on several channels with the same rules.

  • WhatsApp Business Platform

    Through Meta's Cloud API or a business solution provider you already use, with approved message templates.

    Built for you
  • Email

    Read an inbox and send replies over IMAP and SMTP, or through Gmail and Microsoft 365 APIs.

    Ready adapter
  • Microsoft Teams and Slack

    As an app your staff chat with, scoped to the channels you choose.

    Built for you
  • Web chat widget

    Embedded on your website or inside your own app, styled to match.

    Ready adapter
  • Voice

    Phone calls through a telephony provider such as Exotel or Twilio, with speech to text and text to speech.

    Built for you

Storage and documents

Policies, contracts, scans and reports. Agents read documents with the same access rules your people have.

  • Google Drive and Google Workspace

    Docs, Sheets and PDFs in the folders you share with the agent.

    Built for you
  • SharePoint and OneDrive

    Through Microsoft Graph, respecting site and folder permissions.

    Built for you
  • Amazon S3 and compatible storage

    Buckets or prefixes you grant, synced for the knowledge sources.

    Ready adapter
  • File uploads and shared folders

    PDFs, Word, Excel and images uploaded in the app or dropped into a watched folder.

    Ready adapter
  • Document management systems

    Systems such as M-Files or OpenText, through their APIs.

    Built for you

Databases

Your own data, read directly where that is the simplest and safest route. We prefer read only views limited to the fields a task needs.

  • PostgreSQL

    Read only views or a scoped user, through the database adapter.

    Ready adapter
  • MySQL and MariaDB

    Through the database adapter, with queries reviewed by your team.

    Ready adapter
  • Microsoft SQL Server

    Common behind older Indian ERPs and hospital systems.

    Ready adapter
  • Oracle Database

    Through a read only account, usually set up with your DBA.

    Built for you
  • MongoDB and other stores

    Connected per project where the data lives there.

    Built for you

APIs and model providers

Everything else, and the models themselves. Models are chosen per project for the task, the cost and where data may go.

  • REST APIs and webhooks

    Call any documented API, or start a flow when another system sends an event.

    Ready adapter
  • Google Sheets, Excel and CSV

    Read and write rows in sheets your team already maintains.

    Ready adapter
  • Helpdesks

    Freshdesk, Zoho Desk and Jira Service Management, for tickets and replies.

    Built for you
  • HR systems

    Keka, greytHR, Zoho People and Darwinbox, for policies, balances and requests.

    Built for you
  • Model providers

    OpenAI, Anthropic Claude, Google Gemini and open models you host yourself, chosen per application.

    Ready adapter

How a connector is added

From your system to a working agent

The exact route depends on your versions and setup, so it is confirmed in the first call.

  1. Step 1Check the routeAPI, database view or export
  2. Step 2Agree the scopeWhich objects, read or write
  3. Step 3Build and testOn a copy or test company
  4. Step 4Limit accessScoped account per agent
  5. Step 5Hand overDocumented and logged

Ground rules

How every connection is set up

Least access

Each agent gets its own account with the narrowest access its task needs, so a support agent sees order status and nothing about payments.

Drafts before writes

New agents prepare drafts in your systems for a person to approve. Direct writing is switched on later, step by step, where the record supports it.

Every call logged

Each read and write is recorded in the run log with the agent, the time and the result, so you can trace any entry back.

Questions

About connecting your systems

Our Tally runs on a desktop in the accounts office. Can an agent reach it?

Usually, yes. Tally can expose data through its XML interface, and a small connector on the same machine or server passes only the data the agent needs. We check your version and setup in the first call.

Can the agent write into our ERP?

Where you allow it. We recommend starting with drafts, such as a voucher or purchase order waiting for approval, so a person checks it before it reaches the books. Writing goes through the ERP's normal rules and permissions.

What if our system has no API?

There are still routes: a read only database view, scheduled exports, an email inbox the system already writes to, or a shared folder. Each is slower or less complete than an API, and we say which one fits before any work starts.

Who maintains a connector after it is built?

Connectors built on a project are documented and handed over. Our team can maintain them under a support arrangement, or your engineers can take them on.

See it on your work

Bring one slow, repetitive process. We will show you an agent doing it.

A working session with someone who builds these every week.

Or get a ballpark proposal in two minutes

What happens next

  1. Step 1A short call about one process and the systems involved
  2. Step 2A demo of an agent working on a version of your task
  3. Step 3A clear view of fit, approvals and what it would take