Credentials. An API token can change every record it can reach; store it in a secret manager, not in the script.
Who it is forA developer wiring a NocoDB base into other automations.
The problemManual copy and paste between tools and the table causes stale data.
The outcomeScripts that create and update rows, with notifications through App Store integrations.
What you need first
- Docker for the recommended install, or a prebuilt binary for quick local tests
- Optional PostgreSQL database for the Docker with PG setup
- Note the Sustainable Use License, which is not an OSI open source license
Steps
- Start NocoDB with the Docker with SQLite command and create your base
- Create a token (JWT or Social Auth) to sign API requests
- Call the REST APIs or the NocoDB SDK to create, read, update and delete rows
- Connect Slack or SMTP from the App Store so changes can notify the team
Prompt for your agent
Using nocodb/nocodb, write a script that signs requests with my NocoDB token and upserts rows from <my CSV> into table <table name> through the REST APIs, then explain how to add a Slack notification from the App Store.
Caveat. The README only names the REST APIs and SDK; endpoint details are in the NocoDB docs.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for nocodb/nocodb and "Read and write NocoDB records from scripts"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer