NocoDB

· #88 most-used

Your relational database, now your agent's playground

DatabaseSpreadsheetsProductivityProjectsAutomationDeveloperAnalyticsStorage

NocoDB is an open-source no-code platform that turns any PostgreSQL, MySQL, SQLite, or MSSQL database into a collaborative spreadsheet interface — used by over 2,000 organisations to manage live operational data without writing SQL. Connect it to Actionist and your agents can create rows, search records, build filtered views, and react to data changes in real time. Whether you're syncing a sales pipeline, filing support cases, or tracking inventory, your agents work directly against the source of truth — not a copy of it.

Average time saved
10 hours
per person · per month
1 workdays back

Eliminates manual work. Cuts hours of repetitive row entry, status patching, and cross-tool copy-paste from every team's week by routing data automatically to the right NocoDB table the moment it exists.

Schedule

What your NocoDB agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs
7Agents at work
24/7Always on
Mon
Tue
Wed
Thu
Fri
7am
8am
9am
10am
11am
12pm
1pm
2pm
3pm
4pm
5pm
6pm
Agents
Multi-app workflows

NocoDB × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows
9Apps spanned
~35 hrsSaved / week
6Personas served
customer-success★ FeaturedSaves 1h saved · runs ~10× /week

Support ticket to NocoDB case log in 30s

When a customer complaint arrives via Gmail, your agent fetches the sender's full account record from NocoDB in one read, logs a new case row with severity, tier, and history attached, pings the assigned CSM on Slack with a pre-drafted context brief, and books a follow-up call on Google Calendar — before the customer has finished refreshing their inbox.

Trigger: When an email arrives in the support inbox with subject containing 'urgent' or 'issue'
Step 1 trigger
Gmail
Watch for inbound support email
Step 2 read
Nocodb
Get account row by customer email
Step 3 write
Nocodb
Create row in Support Cases table
Step 4 write
Slack
Post case brief to CSM channel
Step 5 write
Google Calendar
Book 30-min follow-up call with customer
Zero cases fall through the cracks
Savings

What this looks like for your team

The comparison strip shows real manual tasks your agent replaces. The calculator translates that into your team's numbers.

Without Actionist
With NocoDB agent
  • Sales
    Pipeline data entry
    Reps manually add closed deals and update stage fields in NocoDB after every call — 18 minutes of clicking that delays the pipeline view staying current.
    18 min/week
    Sales Agent
    Agent files deals automatically
    The moment a deal is marked Closed Won, the agent creates the NocoDB row, fills every field from the CRM record, and the pipeline view updates before the rep puts down the phone.
  • Marketing
    Campaign results filed
    After each campaign closes, someone manually creates rows in the NocoDB results table from a HubSpot export — a 13-minute task done imperfectly at end-of-week.
    13 min/week
    Marketing Agent
    Agent loads campaign rows
    When a campaign completes, the agent bulk-creates contact rows in NocoDB with engagement scores attached — done in seconds, not end-of-week.
  • Customer Support
    Case logging on intake
    Support reps manually create a NocoDB case row for each ticket, copy in the customer tier from a separate sheet, and fill the assignee — 18 minutes per agent per day.
    18 min/week
    Customer Support Agent
    Agent creates and routes cases
    On every new support email, the agent reads the account row, creates the case record with full context, and notifies the CSM — in 30 seconds flat.
  • Human Resources
    Applicant tracking updates
    HR manually updates the NocoDB Candidates table after each interview round, entering status, feedback summary, and next-step date by hand.
    7 min/week
    Human Resources Agent
    Agent updates candidate rows
    When an interview is logged, the agent updates the candidate row with the outcome and next-step date automatically, keeping the hiring pipeline current.
  • Finance
    Invoice row creation
    Finance manually creates a NocoDB invoice row for every approved invoice — entering vendor, amount, due date, and GL code from the approval email each time.
    13 min/week
    Finance Agent
    Agent files invoices on approval
    The moment an invoice is approved, the agent creates the NocoDB row with all fields pre-filled from the source document, creating a searchable audit trail instantly.
  • Operations
    Sheet-to-database sync
    Ops manually reconciles a Google Sheet against NocoDB every morning to find new rows, creates missing records by hand, and checks for drift — a 25-minute ritual.
    25 min/week
    Operations Agent
    Agent syncs on schedule
    Each morning the agent reads the sheet, searches NocoDB for matches, creates any missing rows, and posts a one-line diff — zero manual effort.
  • Legal
    Contract status updates
    Legal manually updates the NocoDB Contracts table when agreements are signed, storing the date, counterparty, and file link — 6 minutes per contract.
    6 min/week
    Legal Agent
    Agent files on signature
    When a DocuSign envelope completes, the agent updates the NocoDB contract row and attaches the PDF before legal has refreshed their inbox.

+ 100s of other automations your agent handles

Average monthly savings
10 hours / person
ROI calculator

See what your team gets back

Team size
10 people
Fully-loaded rate
$20 / hour
Hours / week
25
Hours / year
1,250
Annual ROI
$25,000

Baseline: 2.5 hrs saved per person per week, across the full NocoDB automation set.

Connect

How to plug NocoDB into Actionist

Pick the connection method that suits your environment.

The fastest path to NocoDB from Actionist. The edwinbernadus/nocodb-mcp-server connects over a permissioned API token handshake — no OAuth dance, no SDK to configure, and the agent gains read/write access to all your tables in under a minute.

1
Open the Apps tab

Find NocoDB in the Apps library and click Connect. MCP is selected by default.

2
Generate your NocoDB API token

In NocoDB, click your avatar → Team & Settings → API Tokens → Add new token. Give it a name (e.g. 'Actionist') and copy the token — it appears only once.

3
Test the connection

Actionist runs a read-only call to verify the handshake. You're ready.

Read the NocoDB docs →
Actions

15 actions your agent can call

Read and write operations available to your Actionist agent.

Triggers

8 events your agent can react to

Events your agent watches for, and the actions it kicks off in response.

Skills

Skills that pair with NocoDB

Reusable agent skills that work well alongside this app.

No paired skills curated yet. Add this app to your agent to discover what fits.
MCP servers

MCP servers that work with NocoDB

Connect Actionist to MCP servers built for or around this app.

edwinbernadus/nocodb-mcp-server

Provides full NocoDB database access — read and write rows, manage tables, and interact with attachments — via the Model Context Protocol.

FAQs

Questions about NocoDB + Actionist

How do I connect Actionist to NocoDB?
Open the Apps tab, find NocoDB, and click Connect. Select MCP (recommended) — Actionist will prompt you to paste your NocoDB API token, which you generate in NocoDB under your avatar → Team & Settings → API Tokens. The agent confirms the connection with a read-only test call. Total setup time: under two minutes.
What API credentials does Actionist need for NocoDB?
You need a NocoDB API token with access to the projects your agent will work with. Generate one in NocoDB under your avatar → Team & Settings → API Tokens. The token grants access to all tables in your workspace, so create a dedicated token named 'Actionist' rather than reusing a personal one — makes it easy to revoke without disrupting other integrations.
Which NocoDB objects can the agent read and write?
The agent can create, read, update, and delete rows in any table; list and create tables; search rows with filter conditions; add columns; create and list views; list projects; create new projects; and upload file attachments to row fields. It covers the full CRUD surface of NocoDB's REST API — both rows and schema management. Trigger-based automations fire on row creation, row updates, row deletions, table creation, column additions, attachment uploads, and project sharing events.
Can the agent work with self-hosted NocoDB?
Yes. The API token connection method works with any NocoDB instance — cloud or self-hosted. When configuring the connection, ensure your self-hosted NocoDB instance is reachable from Actionist's network. If it's behind a firewall, you'll need to allowlist Actionist's outbound IP range or use a tunnel. The MCP server also supports self-hosted instances when pointed at the correct base URL.
How do I avoid overwriting rows when the agent runs multiple times?
Use the Search rows action before any Create row call to check whether a matching record already exists — search by a unique field like email or external ID. If a match is found, route to Update row instead. For trigger-based workflows, NocoDB's Row created trigger fires once per insert, so duplicate triggers aren't a risk unless your workflow itself creates a row that re-fires the same trigger — avoid that loop by checking a field value (e.g. a 'processed' flag) before writing.
What happens if a NocoDB table schema changes after I've set up a workflow?
If a column is renamed or deleted, any workflow step that references that field by name will fail with a field-not-found error. Use the List columns action at the start of sensitive workflows to validate the schema before attempting writes. For scheduled agents, add a schema-check step and route failures to a Slack alert so you're notified before data loss occurs — NocoDB doesn't send schema-change webhooks by default.
How do I use NocoDB triggers without polling?
NocoDB supports webhooks for row-level events (created, updated, deleted). In your NocoDB table, open the toolbar → More → Webhooks and create a webhook pointed at Actionist's inbound URL for that trigger. Actionist receives the payload in real time — no polling interval, no delay. For table-level events (table created, column added), use NocoDB's audit log API with a scheduled fetch if webhooks aren't available for those events in your version.
Does the agent support NocoDB's linked record (relation) fields?
Yes. When creating or updating a row, pass the linked record's row ID in the relation field — NocoDB stores the link. When reading a row with Get row or Get many rows, the response includes linked record IDs which the agent can use for subsequent lookups. Full linked-record expansion (fetching the related row's fields inline) requires a separate Get row call on the related table using the returned ID.