Create Bucket
Create an object-store bucket in an existing Prisma project. Optionally set a display name, associate a branch by ID or Git name, and declare a logical identity unique within that branch. Returns bucket metadata.
Prisma Data Platform provides database tools including Accelerate (global database cache), Optimize (AI-driven query analysis), and Prisma Postgres (managed PostgreSQL). Manage workspaces, projects, environments, and API keys programmatically.
Create an object-store bucket in an existing Prisma project. Optionally set a display name, associate a branch by ID or Git name, and declare a logical identity unique within that branch. Returns bucket metadata.
Create an access key for an existing Prisma object-store bucket. Choose read-only or read/write access and optionally a display name. Returns connection details and a secretAccessKey that is returned exactly once and never stored by Prisma; copy it immediately.
Create new API key connection for database access. Creates connection string with embedded credentials for application database access. Returns complete connection details ready for immediate use.
Create a managed connection for an existing Prisma database. Returns connection metadata and endpoint connection strings with credentials on creation. Use the returned endpoints for direct, pooled, or Accelerate access.
Create a managed database in a Prisma project, optionally cloning or restoring it. Omit source for an empty database. Select a region, default status, branch and declared logical identity as needed. Returns database and connection metadata.
Create new Prisma project with managed postgres database. Creates project in authenticated user's workspace with postgres database in specified region. Returns complete project details including connection strings and API keys.
Create new postgres database in an existing Prisma project. Creates database in specified region with connection strings and API keys. Returns complete database details ready for immediate use.
Create a service token in a Prisma workspace, optionally limited to one project. Returns the secret value exactly once; copy it immediately. Expiry defaults to 90 days when omitted; explicitly pass null to create a token without expiry.
Permanently delete a bucket, all objects stored in it, and all its access keys. This action cannot be undone. Returns a tool-local success acknowledgment after the provider accepts the deletion with no response body.
Revoke and delete a bucket access key by its bucket and key IDs. Returns a tool-local success acknowledgment after the provider accepts the deletion with no response body.
Permanently delete database connection and revoke API key access. WARNING: This immediately revokes database access for any applications using this connection string. Ensure no critical systems depend on this connection.
Revoke the integration tokens by integration ID. Returns a tool-local success acknowledgment after the provider accepts the revocation with no response body.
Permanently delete Prisma database and all stored data. WARNING: This action cannot be undone. All data in the database will be permanently destroyed. Default databases typically cannot be deleted.
Permanently delete Prisma project and all associated resources. WARNING: This action cannot be undone. All databases, environments, and project data will be permanently destroyed. Use with extreme caution in production environments.
Revoke a workspace service token by deleting it. Returns a tool-local success acknowledgment after the provider accepts the deletion with no response body.
Execute SQL commands that modify database data or structure. Runs INSERT, UPDATE, DELETE, CREATE TABLE, and other data modification commands safely through PostgreSQL driver with parameterized query support.
Execute SQL queries through a direct SSL PostgreSQL connection and return rows, row count, and execution time. SQL is not restricted to read-only statements; commands may modify data even if fetching results fails.
Get an object-store bucket by ID, including its project and branch metadata.
Get a connection by ID, including its endpoints and database metadata.
Get the user, workspace, and credential represented by the current token.
Retrieve usage metrics for a specific Prisma database. Returns metrics including storage usage and operation counts (reads/writes) for the specified time period. Use for monitoring resource consumption, cost analysis, and capacity planning.
Get an integration by ID, including its scopes, client, and creating user.
Retrieve specific Prisma database by ID. Returns database details including status, project context, and regional deployment. Use for database monitoring, validation, and administrative operations.
Retrieve specific Prisma project by ID. Returns project details including name, creation timestamp, and workspace information. Use for project detail views, validation, and administrative operations.
Get a workspace by ID, including its name, resource URL, and creation time.
Get a workspace's subscription plan, usage-blocked status, and upgrade URL.
Inspect tables and columns in the public database schema, optionally for a named table. Returns data types, nullability, defaults, primary and foreign key information, and row counts.
List all accessible connections, optionally filtered by database. Returns one page with endpoint and database metadata. Pass pagination.nextCursor as cursor to retrieve the next page, retaining the database filter if used.
List databases across all projects accessible to the authenticated token. Optionally filter by project, declared identity, branch ID or Git branch name. Pass pagination.nextCursor as cursor with the same filters to fetch another page.
List access-key metadata for a bucket, without returning secret access keys. Returns one page. Pass pagination.nextCursor as cursor with the same bucketId to retrieve the next page.
List accessible object-store buckets with optional project and branch filters. Returns one page of bucket metadata. Pass pagination.nextCursor as cursor to retrieve the next page, retaining any filters used for the first page.
Retrieve list of available backups for a specific database. Returns backup details including status, size, type, and restoration readiness. Use for backup monitoring, restoration planning, and compliance auditing.
Retrieve paginated list of connections for a specific database. Returns connection details including names, creation dates, and database context. Use for API key management, security audits, and access control.
List integrations for a workspace, including clients, creators, and scopes. Returns one page. Pass pagination.nextCursor as cursor to retrieve the next page, retaining the same workspaceId.
Retrieve all available regions for Prisma Accelerate. Returns regions where Accelerate global database cache can be deployed. Use for cache region selection to minimize latency for your users.
Retrieve all available regions for Prisma Postgres. Returns regions where Prisma Postgres databases can be deployed with current availability status. Use for region selection during database creation and capacity planning.
Retrieve paginated list of Prisma projects accessible to authenticated user. Returns project IDs, names, workspace info, and timestamps with cursor-based pagination. Use for project discovery, UI selection flows, and administrative operations.
Retrieve paginated list of Prisma workspaces accessible to authenticated user. Returns workspace IDs, names, creation timestamps with cursor-based pagination. Use for workspace discovery, UI selection flows, and administrative operations.
Retrieve paginated list of databases for a specific Prisma project. Returns database details including status, region, and project context. Use for database discovery, monitoring, and project administration.
List all available regions across products, optionally filtered by product. Returns region identifiers, names, products, and availability status when provided.
List workspace service-token metadata, newest first, without secret values. Returns one page. Pass pagination.nextCursor as cursor with the same workspaceId to retrieve the next page. The list is empty when the workspace does not exist or the caller is not a member of it.
Retrieve paginated list of integrations for a specific Prisma workspace. Returns integration details including OAuth client info, granted scopes, and creator. Use for security audits, integration management, and workspace administration.
Poll an approval for the authenticated agent to await the sponsor's decision. Only the agent the approval belongs to can read it. Inspect the returned status before retrying an operation that returned approval_required.
Destructively overwrite all target database data with a specified backup. This immediately and irreversibly replaces all data in the existing target; data written since the backup was taken is lost. Ensure you have a recent target backup before proceeding. Connections and credentials are preserved. Restore is asynchronous: status remains recovering until it completes.
Restore database backup to new database instance. Creates new database from existing backup with specified name. Operation is asynchronous - monitor the returned database status for completion. Restoration may take several minutes.
Revoke integration tokens for the specified client in the specified workspace. Returns a tool-local success acknowledgment after the provider accepts the revocation with no response body.
Generate new credentials for an existing Prisma connection. Previous credentials are invalidated on a best-effort basis: revocation is not guaranteed. Update applications to use the returned new connection strings and credentials, and store them securely.
Transfer Prisma project ownership to another user's workspace. Transfers project ownership from the current authenticated user to the recipient specified by their OAuth2 access token. This is typically used in partner integrations where databases are provisioned on the partner's workspace and later transferred to end users. The project and all its databases are moved to the recipient's workspace. The current owner loses access unless the new owner explicitly grants it. Requirements: - Valid project ID owned by the current user - Valid OAuth2 access token for the recipient user - Recipient workspace must have sufficient quota for the project
Update a bucket's display label, logical identity, or branch. A display name change leaves the provider bucket name, objects, and access keys unchanged. Move the bucket separately from setting or clearing logicalId. To replace an existing logicalId, clear it with null first, then set the new one.
Update a database's display name, logical identity, or branch. Every database belongs to a branch; null branch selectors cannot detach it. Move the database separately from setting or clearing logicalId. To replace an existing logicalId, clear it with null first, then set the new one.
Update an existing Prisma project's display name or settings. Omitted fields are not sent. Returns the updated project metadata and its containing workspace.
The Prisma integration connects your Dench AI CRM directly to Prisma, so agents can read and act on your Prisma data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
51 actions are available for agents to invoke on your behalf. Every call runs through Prisma's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Prisma and click Connect — you'll authorize access through Prisma's own sign-in flow. No API keys or code required.
Ask an agent to use Prisma in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Prisma integration connects your AI CRM to Prisma, so AI agents can work with your Prisma data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Prisma integration currently exposes 51 actions, including Create Bucket, Create Bucket Key, Create Database Connection, Create Managed Connection, Create Managed Database, and Create Prisma Project. Agents invoke them on your behalf from chat or from automations.
No. You connect Prisma from your Dench workspace using Prisma's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Prisma's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Prisma connection from your workspace settings at any time.