NOCODB n8n INTEGRATION: AUTOMATE NOCODB WITH N8N

The Update action modifies existing rows in your NocoDB tables. It's essential for keeping your data current—whether updating a customer's status, marking a task complete, or syncing changes from external sources. The critical requirement here: you must always include the primary key to identify which row to update.

Key parameters: Credential to connect with (required dropdown for your NocoDB Token account), Resource (required dropdown set to "Row" for record operations), Operation (required dropdown set to "Update" to modify existing data), Workspace Name or ID (dropdown for workspace selection), Base Name or ID (required field specifying the database base), Table Name or ID (required field identifying the target table), Data to Send (dropdown defining how update data is provided—typically "Define Below for Each Column"), and Fields to Send (dynamic section where you add the columns and new values for the update).

⚠️ Important: This operation requires the primary key to be included for each row. Without it, n8n can't identify which record to update.

Use cases: Update order status when a shipment is dispatched, mark leads as "contacted" after a sales call, sync inventory quantities from your e-commerce platform, or update project progress percentages from task management tools.

The Update action works best when paired with a Get Row action first—retrieve the current data, modify what you need, then push the update back. This ensures you're working with the latest record state.

When you need to retrieve multiple records at once, the Get Many action is your solution. It fetches rows from a NocoDB table in bulk, with options to limit results or return everything. This is perfect for batch processing, reporting, or syncing datasets between platforms.

Key parameters: Credential to connect with (required dropdown for your NocoDB authentication credentials), Resource (required dropdown set to "Row" for table record operations), Operation (required dropdown set to "Get Many" for bulk retrieval), Workspace Name or ID (optional dropdown for workspace selection), Base Name or ID (required field to specify the target database base), Table Name or ID (required field identifying the table to query), Return All (toggle switch that, when enabled, fetches all rows without limit), Limit (number input, default: 50, specifying maximum rows to retrieve when Return All is off), Download Attachments (toggle to include file downloads for retrieved rows), and Options (expandable section for adding filters and advanced query parameters).

Use cases: Export all orders from the past week for a summary report, sync customer records to an external CRM or mailing list, batch process inventory items for stock level updates, or retrieve pending tasks for a daily digest notification.

💡 Pro tip: Use the Options section to add filters when you don't need all records. This reduces data transfer and processing time, especially with large tables. Combine with the Limit parameter for paginated workflows that handle large datasets efficiently.

The Get Row action retrieves a specific record from your NocoDB table using its unique row ID. This is essential for workflows where you need to fetch detailed information about a particular entry—whether to display it, process it, or use it as context for subsequent actions.

Key parameters: Credential to connect with (required dropdown for selecting your authenticated NocoDB Token account), Resource (required dropdown set to "Row" for record-level operations), Operation (required dropdown set to "Get" to retrieve a single row), Workspace Name or ID (optional dropdown to specify the workspace context), Base Name or ID (required field identifying the database base), Table Name or ID (required field specifying which table contains the target row), Row ID Value (required text input where you provide the unique identifier of the row to retrieve), and Download Attachments (optional toggle that, when enabled, downloads any files attached to the row).

Use cases: Fetch customer details when processing a support ticket, retrieve product information for an order confirmation email, get task details to populate a notification message, or pull record data to verify before performing an update.

The Download Attachments toggle is particularly useful when your NocoDB records include files—enable it to access those attachments directly within your workflow for further processing or forwarding.

The Delete Row action permanently removes a specific record from your NocoDB table. Use it for data cleanup, archival workflows, or when records need to be removed based on external triggers. Since deletion is irreversible, this action requires precise identification via the row's primary key.

Key parameters: Credential to connect with (required dropdown for NocoDB authentication), Resource (required dropdown set to "Row" for record-level operations), Operation (required dropdown set to "Delete" for removal actions), Workspace Name or ID (required dropdown for workspace selection), Base Name or ID (required field identifying the database base), Table Name or ID (required field specifying the table containing the target row), Primary Key Type (required dropdown specifying your table's primary key type—typically "Default" for auto-generated IDs), and Row ID Value (required text input where you provide the unique identifier of the row to delete).

Use cases: Remove cancelled orders from your active orders table, clean up test records after development workflows, delete expired entries (coupons, temporary access, etc.), or remove duplicate records identified by deduplication logic. For advanced duplicate detection, explore our HubSpot duplicate merging workflow.

💡 TIP: Consider implementing a "soft delete" pattern instead of permanent deletion. Create a "Deleted" column in your table, and use the Update action to mark records as deleted rather than removing them. This gives you a recovery option if something goes wrong.

The Create Row action is your go-to for adding new records to any NocoDB table. Whether you're capturing form submissions, logging events, or syncing data from external sources, this action lets you programmatically insert data exactly where it needs to go.

Key parameters: Credential to connect with (required dropdown to select your NocoDB Token account for authentication), Resource (required dropdown set to "Row" to specify you're working with table records), Operation (required dropdown set to "Create" to indicate a new row insertion), Workspace Name or ID (dropdown to select your target NocoDB workspace), Base Name or ID (required field to identify which database base contains your target table), Table Name or ID (required field specifying the exact table where the new row will be created), Data to Send (dropdown defining how data is provided—typically "Define Below for Each Column" for manual mapping), and Fields to Send (dynamic section where you add column-value pairs for the new record).

Use cases: Automatically create a customer record when someone fills out a contact form, log each new e-commerce order as a row in your orders database, sync leads from your marketing platform into a NocoDB CRM table, or create project tasks from Slack messages or email triggers. You can also combine this with Baserow integrations for multi-database workflows.

This action shines when combined with webhooks or scheduled triggers from other platforms, enabling real-time data capture without manual intervention.