Add Connector Resource
Add one discovered provider resource to an existing connector with optional routing, filters, metadata, instructions, and access control.
HydraDB is a hosted context layer for ingesting, connecting, and querying data for AI applications.
Add one discovered provider resource to an existing connector with optional routing, filters, metadata, instructions, and access control.
Add new fields to a database metadata schema; existing fields cannot be deleted, renamed, retyped, or reconfigured.
Activate selected discovered resources on a connector and start their sync; unlisted existing resources remain unchanged.
Create a HydraDB connector and store the provider authorization required to sync one external account. Obtain the provider-specific shape from List Connector Providers.
Provision a HydraDB database asynchronously. This may create billable infrastructure; poll Get Database Status before ingestion.
Permanently delete one HydraDB collection and all of its data while leaving the database intact.
Permanently delete a HydraDB connector, all resource mappings, and its stored provider authorization.
Permanently remove one resource mapping from a HydraDB connector.
Permanently delete specific HydraDB knowledge or memory contexts. Uses strict provider status handling so missing, indexing, and store failures cannot appear successful.
Permanently delete a HydraDB database and all associated data. This cannot be undone.
Unregister the account's indexing webhook and stop all future event deliveries.
Remove the indexing webhook signing secret. Future deliveries remain enabled but can no longer be authenticated with HydraDB signatures.
List resources available through an existing connector's stored provider credentials. Discovery pagination is provider-dependent (currently Notion only); other providers may return the complete list despite limit. This may call the external provider.
Generate or set and replace the indexing webhook signing secret. The previous secret stops working immediately and the active secret is returned only once.
Get one connector's configuration and lifecycle state by connector ID.
Check a connector's overall health, sync state, errors, and per-resource health in one call.
Return extracted entity relations for one context or an entire collection, one page at a time.
Check processing status for one or more ingested or connector-synced context IDs.
Traverse context-level relations from one context and return reachable contexts and graph evidence up to bounded depth and size.
Get knowledge and memory collection row counts for one database.
Check whether one database's scheduler, graph, and vector infrastructure is ready for ingestion.
Get the account's indexing webhook URL, subscribed event types, registration state, and whether signing is configured.
Get the declared metadata fields and types for one database.
Get one indexing webhook delivery attempt by delivery ID for failure diagnosis.
Ingest documents, app knowledge, memories, or an explicit graph into a HydraDB database and return context IDs for asynchronous status checks.
Fetch one context's stored content, enrichment, and/or a time-limited download URL.
List the collections in one HydraDB database.
List supported connector providers, or describe one provider's resource types, credential schema, and setup requirements.
List the resources currently configured on a connector, including routing, filters, access controls, and per-resource health metadata.
List the connected data providers in the account, optionally filtered by provider, with optional health rollups.
List knowledge or memory contexts in a database or collection, one bounded page at a time.
List HydraDB databases and preserve per-database provisioning or failure diagnostics.
List recent indexing webhook delivery attempts, optionally filtered by status, one page at a time.
Search a HydraDB database for ranked chunks and graph context, with optional collection, metadata, source, ACL, and retrieval controls.
Register or replace the organization's HTTPS endpoint and event subscriptions for HydraDB indexing events. This call can preserve the existing signing secret, generate and return a new one, or install a caller-supplied secret.
Queue one failed indexing webhook delivery for another attempt. This repeats an external callback and may repeat downstream side effects.
Pause scheduled syncs or resume a paused HydraDB connector. Resuming immediately schedules a sync from the connector's saved positions.
Record a rating, comment, or known ground truth for a prior HydraDB query. This optional signal does not change the original query result. HydraDB allows 100 feedback submissions per minute per organization; if rate limited, skip the report rather than retrying in a loop.
Send one test event to the currently registered indexing webhook endpoint.
Start a connector sync now, causing external provider reads and HydraDB ingestion. If a sync is already running, it continues; paused connectors and connectors without active resources fail.
Update an existing HydraDB connector's sync cadence, default ingestion instructions, or provider credentials. Replacing credentials requires explicit confirmation.
Replace a HydraDB connector resource's access rules or change its ingestion instructions for subsequent syncs.
Merge metadata into one HydraDB context or replace its access-control list without re-ingesting content.
The HydraDB integration connects your Dench AI CRM directly to HydraDB, so agents can read and act on your HydraDB data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
43 actions are available for agents to invoke on your behalf. Every call runs through HydraDB's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find HydraDB and click Connect — you'll authorize access through HydraDB's own sign-in flow. No API keys or code required.
Ask an agent to use HydraDB in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench HydraDB integration connects your AI CRM to HydraDB, so AI agents can work with your HydraDB 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 HydraDB integration currently exposes 43 actions, including Add Connector Resource, Add Metadata Schema Fields, Configure Connector Resources, Create Connector, Create Database, and Delete Collection. Agents invoke them on your behalf from chat or from automations.
No. You connect HydraDB from your Dench workspace using HydraDB's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through HydraDB's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the HydraDB connection from your workspace settings at any time.