Skip to content
NocoAIby NocoDB
Sign inStart for free
Integrations

NocoAI builds on the data you already have.

A blank base is the easy case. The useful one is the database you already run, the tickets already in Jira and the model you already pay for. Connect them, then build on top.

ConnectSyncModelsAct
  • PostgreSQL
  • Jira
  • GitHub
  • Slack
  • OpenAI
  • Zendesk
  • HubSpot
  • Claude
  • GitLab
  • Snowflake
  • Google Drive
  • Outlook
  • Gemini
  • Linear
  • Dropbox
  • Freshdesk
  • Twilio
  • Mistral
  • SQL Server
  • Bitbucket
  • Groq
  • Gmail
  • BambooHR
  • Oracle
Connect

Point it at a database you already run.

NocoAI reads the schema that is already there: tables, types, foreign keys. On top it builds views, forms and an app. Your database stays the system of record, in your own infrastructure, with NocoDB as the interface.

Connect my Postgres database and build me an operations app on top of it: a dashboard of orders by month, a view of orders that shipped late, and a form my warehouse team can use to log a shipment.

Databases
  • PostgreSQL
  • MySQL
  • SQLite
  • MS SQL ServerEnterprise
  • SnowflakeEnterprise
  • OracleEnterprise
Sync

Pull records out of the tools your team already lives in.

A sync brings records into a base on a schedule and keeps them current. Once they're in, they're ordinary rows: join them to your own tables, filter them, chart them, and let NocoAI build on top of the lot.

Sync my Jira issues and my GitHub pull requests into one base, link them by branch name, and build me a sprint dashboard showing open issues by assignee, cycle time per issue, and anything that has been in review for more than three days.

Tickets & issues
  • Jira
  • Linear
  • GitHub
  • GitLab
  • Bitbucket
  • Zendesk
  • Freshdesk
  • Chatwoot
CRM
  • HubSpot
Calendars
  • Google Calendar
  • Outlook Calendar
  • CalDAVApple iCloud and others
Files
  • Google Drive
  • Dropbox
  • Box
People
  • BambooHR
Databases
  • PostgreSQL
  • MySQL
  • MS SQL Server
Models

Bring your own model, or your own endpoint.

AI fields, agents and the builder itself run on a provider you choose and a key you hold. Pick a hosted provider, or point NocoDB at any OpenAI-compatible endpoint. That includes a model on your own hardware, where no prompt or record leaves your network.

Add an AI field to my support tickets table that classifies each ticket as bug, billing, how-to or feature request, and a second field that summarises the customer's problem in one sentence for my weekly report.

Frontier providers
  • OpenAI
  • Anthropic Claude
  • Google Gemini
  • Mistral
  • Cohere
  • xAI
  • DeepSeek
  • Alibaba Qwen
Inference platforms
  • Groq
  • Together
  • Fireworks
  • Cerebras
  • Baseten
  • DeepInfra
  • Hugging Face
  • Vercel AI Gateway
Cloud providers
  • Amazon Bedrock
  • Azure OpenAI
Your own
  • Any OpenAI-compatible endpointOllama, vLLM, LM Studio, a gateway of your own
  • NocoDB-hostedIncluded, no key to bring
Act

Do something when the data changes.

Workflows watch a table and then reach outward: post to a channel, send the email, create the issue, call your own endpoint. The trigger is a record event or a schedule; the steps are these.

When a support ticket is created with priority set to urgent, post it to our #support Slack channel with the customer name and a link to the record, and email the on-call engineer if nobody has picked it up within fifteen minutes.

Messaging
  • Slack
  • Gmail
  • Outlook
  • TwilioSMS and WhatsApp
  • SMTPYour own mail server
Work tools
  • GitHub
  • Google Calendar
  • HubSpot CRM
  • Mailchimp
  • Zoho
Anything else
  • HTTP requestAny API, any auth
  • NocoDBRead and write your other tables
  • AI stepGenerate, classify or decide mid-workflow
  • Redis
  • ClickHouse
Import

Or move it across once and be done.

A sync keeps two systems in step. An import is the one-way move you make when you're leaving the other tool behind, Airtable included.

  • Airtable

    Tables, fields, links, views and records

    Guide

  • CSV

    One file or many, into new or existing tables

  • Excel

    Multi-sheet, with sheets you can exclude

  • JSON

    Nested objects flattened into fields

  • Google Sheets

    By URL

  • Another NocoDB base

    Duplicate schema, data, or both

Ways out

Nothing you build here is trapped here.

Every integration above brings data in. These four are how it gets back out: to your own code, your own agents, and services we've never heard of.

REST API

Every table gets a versioned REST endpoint the moment it exists: read, write, filter, sort, paginate. No generation step, no separate service to deploy.

See the API

MCP

A built-in Model Context Protocol server, so Claude, Cursor or an agent of your own can read and write your bases with the permissions you grant it.

See agents

Webhooks

Fire on create, update or delete, with conditions and a payload you shape. The way most teams connect NocoDB to something we've never heard of.

Read the docs

Scripts

When a workflow step doesn't fit, write the logic instead. Scripts run against your base with full access to its data.

Read the docs

Missing an integration? The framework is open source, and every package on this page is the same shape as one you could write. Read the source.

So, what do you want to build?

One sentence is enough to start. Free, no credit card, and the base it builds is yours to keep.