Free & open source Airtable alternative. NocoDB turns any database into a smart spreadsheet with REST APIs.
Free & open source Airtable alternative. NocoDB turns any database into a smart spreadsheet with REST APIs. On Nagent, NocoDB is exposed as a fully-configurable databases integration that any agent can call — 28 actions, and API_KEY, API_KEY authentication. No code is required to wire NocoDB into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use NocoDB to automate the kinds of tasks databases teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire NocoDB into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against NocoDB, with input parameters and output schema. Drop these into any step of an agent built in Helix.
NOCODB_AUTH_METool to get authenticated user information including email, name, roles, and profile details. Use when you need to verify user authentication or retrieve the current user's profile information.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_AUTH_PASSWORD_FORGOTTool to initiate password reset process by sending a reset email to the user. Use when a user has forgotten their password and needs to receive a password reset link via email.
Input parameters
The email address of the registered user account. Must be a valid email format.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_AUTH_SIGNOUTTool to sign out the authenticated user and clear their refresh token from the database and cookie. Use when you need to invalidate a user's authentication session and log them out of the NocoDB application.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_DB_TABLE_SORT_GETTool to retrieve sort configuration by ID from NocoDB. Use when you need to get details about how data is ordered in a specific view.
Input parameters
Unique identifier of the sort configuration to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_DB_VIEW_COLUMN_UPDATETool to update a column configuration in a view. Use when you need to change column visibility, order, or width in a specific view.
Input parameters
Whether to show or hide the column in the view. Set to true to show, false to hide.
The display order of the column in the view. Lower numbers appear first.
The width of the column when displayed in the view. Should be a string with 'px' suffix (e.g., '200px').
The unique identifier of the view containing the column. An alphanumeric string prefixed with 'vw' or 'v'.
The unique identifier of the view column configuration to update. An alphanumeric string prefixed with 'nc'. This is the view column ID from the view columns list, not the table field ID.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_DB_VIEW_DELETETool to delete a view from a NocoDB table. Use when you need to permanently remove a view. This action cannot be undone.
Input parameters
Unique View ID identifying the view to delete. An alphanumeric string prefixed with 'v' (e.g., vw_wtdg2meyig5l4q) with a maximum length of 20 characters.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_DB_VIEW_ROW_DELETETool to delete a specific row from a table view in NocoDB. Use when you need to remove a single record from a view.
Input parameters
Organization identifier. Defaults to 'noco' if not specified.
Unique identifier of the row to be deleted.
Name of the base/project containing the table.
Name of the view from which to delete the row.
Name of the table containing the row to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_INTEGRATIONS_INFOTool to retrieve metadata for a specific NocoDB integration by type and subtype. Use when you need to get integration configuration schema, display information, or available capabilities for an integration.
Input parameters
The category/type of integration (e.g., 'Database', 'ai'). Specifies the integration type classification.
The specific variant within the integration type. For databases: 'pg' (PostgreSQL), 'mysql2' (MySQL), 'sqlite3' (SQLite), 'snowflake', 'databricks'. For AI: 'openai', etc.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_INTEGRATIONS_LISTTool to retrieve all available integrations in NocoDB. Use when you need to list all integrations including AI, authentication, sync, and workflow-node types.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_INTEGRATION_STORETool to store configuration for a NocoDB integration. Use when you need to save or update integration settings like API keys, models, or other configuration parameters.
Input parameters
Configuration object containing integration settings like API keys, models, and other parameters specific to the integration type
Unique identifier for the integration to store configuration
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_LIST_WORKSPACESTool to list all workspaces accessible to the authenticated user. Use when you need to discover workspace_id before base operations, primarily relevant for NocoDB Cloud or multi-workspace deployments.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_NOTIFICATION_DELETETool to delete a notification for the authenticated user. Use when you need to remove a notification. This performs a soft-delete operation.
Input parameters
The unique identifier of the notification to delete. An alphanumeric string that uniquely identifies a specific notification for the authenticated user.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_NOTIFICATION_LISTTool to retrieve paginated notification records for the authenticated user. Use when you need to list notifications with optional filtering by read status and pagination support. Only returns notifications that haven't been soft-deleted.
Input parameters
Maximum number of notifications to return per request. Defaults to 10 if not specified.
Filter notifications by read status. Pass true for read notifications, false for unread. If omitted, returns all notifications.
Number of notifications to skip for pagination. Defaults to 0 if not specified.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_NOTIFICATION_POLLTool to poll for notifications using long-polling mechanism. Use when you need to check for new notifications for the authenticated user. The connection is maintained for up to 30 seconds; if no notification arrives, returns status 'refresh' and the client should poll again.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_PLUGIN_STATUSTool to check if a NocoDB plugin is active or not. Use when you need to verify the operational status of a specific plugin by its identifier.
Input parameters
Unique identifier for the plugin to check status (e.g., 'S3', 'SES', 'Backblaze', 'Vultr', 'OvhCloud', 'LinodeObjectStorage', 'UpcloudObjectStorage', 'Minio', 'GCS', 'Spaces', 'Scaleway').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_PUBLIC_GROUPED_DATA_LISTTool to retrieve grouped data from a publicly shared NocoDB view. Use when you need to access grouped records from a public shared view without authentication.
Input parameters
Sort order for the grouped data. Format: columnName for ascending, -columnName for descending.
Maximum number of grouped records to return. Used for pagination.
Filter condition to apply on the data in URL-encoded format.
Number of records to skip before starting to return results. Used for pagination.
Unique identifier of the column to group data by.
Unique identifier (UUID) of the public shared view to retrieve grouped data from.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_STORAGE_UPLOAD_BY_URLTool to upload attachments from remote URLs to NocoDB storage. Use when you need to import files from external URLs or migrate attachments from other platforms like Airtable. The server fetches files from provided URLs and stores them in configured storage.
Input parameters
Storage path/scope for the uploaded files
Array of attachment objects to upload from URLs. Each object must contain at least a 'url' field.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_TABLE_READTool to retrieve complete schema information for a specific table. Use when you need to understand table structure, field definitions, or available views.
Input parameters
Unique identifier for the base containing the table
Unique identifier for the table to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_USER_PROFILE_UPDATETool to update authenticated user's profile information including display name, first name, and last name. Use when you need to modify the current user's profile details in NocoDB.
Input parameters
User's last name.
User's first name.
The display name for the user. Used to update how the user's name appears in the interface.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_UTILS_AGGREGATED_META_INFOTool to get aggregated meta information such as tableCount, dbViewCount, viewCount and other statistics about the NocoDB instance. Use when you need an overview of the system's data structure and usage metrics.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_UTILS_APP_HEALTHTool to get the NocoDB application health status. Use when you need to check if the application is running and responsive, typically for load balancers or monitoring systems.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_UTILS_APP_INFOTool to get comprehensive NocoDB application information including authentication settings, version, limits, and deployment configuration. Use when you need to discover application capabilities, feature flags, or system configuration.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_UTILS_CLOUD_FEATURESTool to get NocoDB Cloud features. Use when you need to retrieve available cloud-specific features and capabilities, including their availability status and highlight information.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_UTILS_COMMAND_PALETTETool to get dynamic command palette suggestions based on scope. Use when you need to retrieve available commands and actions for the NocoDB interface.
Input parameters
Optional search query to filter command suggestions.
Optional scope to filter command palette suggestions. Determines the context for available commands.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_UTILS_ERROR_REPORTTool to report errors to NocoDB's error tracking system. Use when you need to submit error reports including error type, message, stack trace, and timestamp for monitoring and debugging purposes.
Input parameters
Error name or type identifier. Provides a concise label for the error category.
Stack trace or call stack showing the sequence of function calls leading to the error. Helps in debugging.
Detailed error message describing what went wrong. Should be human-readable and informative.
ISO 8601 timestamp indicating when the error occurred. If not provided, the server may use current time.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_UTILS_FEEDTool to get NocoDB product feed from social media sources including GitHub, YouTube, Twitter, and Cloud. Use when you need to retrieve social media updates and content from NocoDB's various channels. Supports filtering by feed source and pagination.
Input parameters
Page number for pagination. Must be >= 1.
Specifies the feed source to retrieve. Valid values: 'github', 'youtube', 'twitter', 'cloud', or 'all'.
Number of items per page. Must be between 1 and 100.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_UTILS_URL_TO_CONFIGTool to convert JDBC URL or database connection URL to connection configuration object. Use when you need to parse and extract database connection parameters from a URL string for configuration purposes.
Input parameters
Database connection URL in JDBC format or standard format (e.g., 'jdbc:mysql://localhost:3306/mydb?user=root&password=test', 'pg://user:pass@host:5432/dbname', 'sqlite://path/to/db.db').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCODB_WORKSPACE_BASE_LISTTool to list all bases in a NocoDB workspace. Use when you need to retrieve bases associated with a specific workspace. Supports pagination via page and pageSize parameters.
Input parameters
Current page number for pagination. Must be >= 1.
Number of items per page. Defaults to 25 if not specified.
Unique identifier for the workspace to list bases from.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 87 agents privately built on Nagent that already use NocoDB.
Build on Nagent
Connect NocoDB to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find NocoDB, and click "Connect Now." You'll authenticate with API_KEY, API_KEY — Nagent handles credential storage and refresh automatically. Once connected, NocoDB is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once NocoDB is connected, you configure its 28 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop NocoDB steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a NocoDB event fires, the agent kicks off automatically.
Every NocoDB action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While NocoDB ships with 28 pre-built databases actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching NocoDB together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build NocoDB-based workflows tailored to your business.