Bulk Submit Context Data
Merge a non-empty batch into a Rulebricks context and execute ready bound rules or flows. External effects and partial writes may occur; retrying after an uncertain response can repeat effects. Returns per-instance outcomes.
Rulebricks is a decision automation platform for building, testing, publishing, and executing business rules and decision flows.
Merge a non-empty batch into a Rulebricks context and execute ready bound rules or flows. External effects and partial writes may occur; retrying after an uncertain response can repeat effects. Returns per-instance outcomes.
Re-evaluate registered pending rule and flow work for a Rulebricks context instance after dependencies may have become available. Flows may invoke external actions, and retrying an uncertain request can repeat their effects.
Count decision logs matching asset, status, trace, payload-content, or time-range filters without returning log payloads.
Create a saved test case for a Rulebricks rule or flow with an input, expected response, comparison policy, and criticality.
Create a Rulebricks context with stored and derived fields, an identity fact, retention settings, and access controls.
Create a has-many, has-one, or belongs-to relationship from one Rulebricks context to another.
Create a folder for rule, flow, or context assets; the asset type defaults to rule.
Create new vocabulary values or update existing values by name, including nested values and per-value metadata.
Create a new user directly with a password, bypassing the email invitation flow. The user can immediately log in with the provided credentials. The provider-issued API key is omitted from the response.
Create a new user group in your Rulebricks organization.
Permanently delete one saved test case from a Rulebricks rule or flow.
Delete a Rulebricks context and all of its live instances, returning affected bindings and pending evaluations.
Permanently delete one Rulebricks context instance and its history, cancel its pending evaluations, and re-evaluate dependent context instances. Ready dependent rules or flows may execute; flows may invoke external actions.
Delete a specific relationship owned by a Rulebricks context.
Permanently delete one Rulebricks flow by ID.
Delete one folder by ID without deleting the assets it contains.
Delete a workspace object by ID or exact name and archive, delete, or detach its generated values.
Permanently delete one Rulebricks rule by ID.
Delete one vocabulary value by ID and replace references from other values with its content; rule or flow references and object-managed namespaces can block deletion.
Execute multiple published Rulebricks rules or flows in parallel from one named map. Each entry is independent, so successful results are returned alongside reserved `$error` details for entries that fail. Flows may invoke external actions, and retrying an uncertain request can repeat their effects. A successful call uses the organization's monthly execution allowance for each entry.
Execute one published Rulebricks rule against up to 1000 ordered input objects and return one aligned result per input. A successful call uses the organization's monthly execution allowance for each input.
Execute a published Rulebricks flow once or in bulk and return the ordered flow-defined output and execution ID for querying its decision logs. A flow may invoke external actions, and retrying an uncertain request can repeat their effects. A successful execution uses the organization's monthly execution allowance.
Execute a published Rulebricks rule with its input payload and return the rule-defined decision output. A successful execution uses the organization's monthly execution allowance.
Export selected Rulebricks rules, flows, contexts, or values with their resolved dependencies, or preview the export. Provide at least one of root_ids, root_collection, root_collections, or all_values=true for value catalogs; selectors may be combined.
Export one flow as a Rulebricks Flow Schema document that can be round-tripped through the flow import endpoint. Provide flow_id or flow_slug; at least one is required, and the provider accepts both together.
Export one rule by ID as a raw rule document that can be round-tripped through the Rulebricks rule import endpoint.
Retrieve a Rulebricks context by ID, including its schema, bindings, access controls, and relationships.
Retrieve the current base facts, derived facts, status, and selected execution or relationship data for one Rulebricks context instance.
Retrieve newest-first historical values for all fields or one selected field on a Rulebricks context instance.
Fetch one workspace object (JSON Schema) by its ID or exact name.
Return the organization's current plan and monthly Rulebricks execution usage, limit, and remaining allowance.
Atomically create or update rules, flows, contexts, and values from a Rulebricks manifest. Override updates conflicts in place while preserving prior versions, release pins, context records, IDs, folders, and access groups. Use PREVIEW_IMPORT_MANIFEST to inspect the write-free plan first.
Create or update a flow from a Rulebricks Flow Schema document; imported flows publish by default unless publish (provider field _publish) is false.
Create a rule from a complete raw rule document, or partially update an existing rule when the document includes its ID.
Invite a new user to the organization or update role or user group data for an existing user.
List saved test cases for a Rulebricks rule or flow, including expected responses and latest execution state.
List incoming and outgoing relationships configured for a Rulebricks context.
List contexts visible to the connected API key, optionally filtered or paginated by the provider's opaque cursor.
List flows visible to the connected API key, optionally selecting an exact asset version or filtering by identifier, search, folder, labels, group, or name.
List asset folders visible to the connected API key, optionally filtered by user group or name.
List workspace objects (JSON Schemas) visible to the connected API key's user groups.
List rule and flow evaluations registered as pending for one Rulebricks context instance, including their missing dependencies.
List rules visible to the connected API key, optionally selecting an exact asset version or filtering by identifier, search, folder, labels, group, or name.
List all user groups available in your Rulebricks organization.
List all users (including the admin and all team members) in the organization with their email, name, role, user groups, and join date. Provider-issued API keys are omitted from the response.
Return one page of vocabulary values visible to the connected API key, with optional name, prefix, type, group, and usage filters.
Return the server-authoritative plan for importing Rulebricks rules, flows, contexts, and values without writing any assets.
Validate and preview creating or updating a workspace object and synchronizing its JSON Schema enum values without writing any changes.
Preview the created, updated, unchanged, archived, and deleted values for one complete single-request collection synchronization without writing changes.
Return one page of decision logs filtered by assets, status, trace, payload content, or time range. Check limited even when no next cursor is returned; a limited page does not cover all matching history.
Replace or clear all custom metadata for one vocabulary value by ID without resending its value payload. The API key must have edit-values permission.
Run all saved tests, or only critical tests, against the latest draft of a Rulebricks rule or flow and return pass totals and failure diagnostics. Version targeting is not supported.
Persist optional facts and execute one rule or flow bound to a Rulebricks context instance, or register it pending when dependencies are missing. Flows may cause external effects; retrying an uncertain outcome can repeat them.
Merge facts into one Rulebricks context instance. This may immediately execute bound rules or flows and cause their external effects; returns the resolved state and triggered evaluations.
Synchronize one vocabulary collection to a desired set. Chunks commit independently and must run sequentially under one fresh sync_id; finalize only after every chunk succeeds and do not overlap collection pipelines. Completion archives or deletes omitted members. This action always writes.
Update a Rulebricks context's name, schema, identity, retention, execution behavior, folder, or access groups. Changing identity_fact on a context with live instances changes how future writes resolve them.
Update an existing folder's required name and optional description by ID without changing its asset type.
Upload one plain UTF-8 or gzip-compressed part of a Rulebricks manifest larger than 4 MiB. Reuse one upload_id, send parts in zero-based order, then pass that ID and the total part count as manifest_upload to IMPORT_MANIFEST. Parts expire after 24 hours.
Create a workspace object by name or update one by ID or name, then synchronize values generated from its JSON Schema enums. Generated values removed from the submitted schema are archived. This action always writes.
The Rulebricks integration connects your Dench AI CRM directly to Rulebricks, so agents can read and act on your Rulebricks data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
59 actions are available for agents to invoke on your behalf. Every call runs through Rulebricks's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Rulebricks and click Connect — you'll authorize access through Rulebricks's own sign-in flow. No API keys or code required.
Ask an agent to use Rulebricks in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Rulebricks integration connects your AI CRM to Rulebricks, so AI agents can work with your Rulebricks 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 Rulebricks integration currently exposes 59 actions, including Bulk Submit Context Data, Cascade Context Instance, Count Decision Logs, Create Asset Test, Create Context, and Create Context Relationship. Agents invoke them on your behalf from chat or from automations.
No. You connect Rulebricks from your Dench workspace using Rulebricks's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Rulebricks's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Rulebricks connection from your workspace settings at any time.