Count Entities by Type
Request a count of entities for a specified Fibery type or database, such as users or features. The result may reflect a limited set of matching entities rather than the total.
Fibery is a work management platform designed to help teams collaborate, organize information, and manage their workflows.
Request a count of entities for a specified Fibery type or database, such as users or features. The result may reflect a limited set of matching entities rather than the total.
Tool to create a new Fibery entity. Use when you have prepared all necessary field values and need to persist a new record. Example: Create a 'Project/Task' with title and assignee.
Delete a custom app endpoint by app and endpoint IDs. The result reports success for HTTP 200, 204 or 404, so success does not by itself confirm deletion.
Permanently delete a Fibery entity by its UUID and type. Use this action when you need to remove an entity from the workspace. Requires both the entity's UUID and its full qualified type name. WARNING: Deletion is irreversible. Example: Delete a task with entity_id='550e8400-e29b-41d4-a716-446655440000' and type='Tasks/Task'.
Delete a file from Fibery storage using its secret identifier. Use this action to permanently remove an uploaded file. You must provide the file's secret (fibery/secret), not its ID (fibery/id). The secret is returned when you upload a file or can be queried via the commands API.
Delete/revoke an existing Fibery API access token by its ID. Uses the DELETE /api/tokens/:token_id endpoint to permanently remove an API token. Important: This endpoint typically requires cookie-based authentication (browser session). When using API token authentication, you may receive a 401 Unauthorized error. Use this when you need to invalidate a specific API token, such as during security rotation or when revoking access for a specific integration.
Request an OAuth2 authorization-code exchange for a Fibery custom integration, using the authorization code and redirect URI. The result may contain the existing configured authorization token rather than a newly exchanged token; a refresh token may also be returned.
Execute GraphQL queries or mutations against a Fibery workspace. Fibery organizes data into Spaces, each with its own GraphQL schema containing entity types and operations. This action automatically tries common space names if no space is specified, making it easy to use without prior knowledge. Best practices: - Start with introspection queries to discover schema: { __schema { types { name } } } - Use { __type(name: "Query") { fields { name } } } to see available queries - Space names typically match your workspace app/database names - The action returns both data and errors (GraphQL can return partial results)
Fetch a page of options for a field of a Fibery entity type for uses such as filtering or dropdowns. Pagination is caller-driven, with a page size from 1 to 1,000; the next-page indicator signals that more results may be available, not that another page is guaranteed.
DEPRECATED: Use FIBERY_GET_ENTITIES instead. Fetch entities from a Fibery workspace using flexible queries. This action retrieves entities of a specified type with support for: - Field selection (choose which fields to return) - Filtering with where clauses - Pagination with limit and offset - Parameterized queries for dynamic filtering Use FIBERY_POST_FETCH_SCHEMA to discover available entity types and their fields.
Fetch the complete schema metadata for a Fibery workspace. Returns all types (entities) and their fields, including system types (fibery/user, fibery/app) and user-defined types (MySpace/Task, etc.). Use this to discover available types before querying data or to understand the structure of your workspace.
Retrieve application information, including version, name, authentication methods and data sources when available. A workspace fallback can return minimal information with empty authentication and source lists.
List custom endpoints for a given Fibery app, for use when selecting an endpoint to invoke. An empty result does not necessarily mean the app has no endpoints.
List Fibery workspace app records and their identifiers, titles, names and versions, subject to a configurable limit that defaults to 100.
DEPRECATED: Use PostFetchData instead. Query Fibery entities from a specified database type with flexible filtering and pagination. Use this to retrieve entities (records) from Fibery databases. Common types include: - 'fibery/user' - workspace users - 'YourSpace/YourType' - custom databases in your workspace IMPORTANT - Field Selection: - PRIMITIVE fields (text, numbers, dates, bools) are selected as strings: ["fibery/id", "user/name"] - RELATION fields (entity references) require nested object syntax: * Single relations: [{"assigned-to": ["fibery/id", "user/name"]}] * Collections: [{"tasks": {"q/select": ["fibery/id", "task/name"], "q/limit": 10}}] - Selecting a relation field as a string will cause "field is not primitive" error The query uses Fibery's Commands API with fibery.entity/query command.
Retrieve a single Fibery entity by its type-qualified identifier. This deprecated tool returns the entity ID by default and can include additional fields selected with expand.
Download a file from Fibery by its secret or ID. Use this tool to retrieve file content from Fibery storage. The file secret is a UUID that uniquely identifies a file and is the preferred identifier. You can obtain the file secret: - From the 'fibery/secret' field when querying entities that have file fields - From the 'url' field in upload file response (extract the UUID from the URL) - From rich text content where files are embedded as /api/files/{secret}
Retrieve a Fibery GraphQL introspection response as a string to discover available types, fields and operations before composing queries. GraphQL schemas are scoped to individual spaces; the response may contain GraphQL errors rather than a schema.
Retrieve UI preferences from the first user returned by a Fibery user query. The query does not explicitly filter for the authenticated user.
Check Fibery access credentials and return token information. For an OAuth-style integration, the result may include a new access token.
Update fields on a Fibery entity of a specified type, including text, numbers, states and relations. The target is the UUID in the fields mapping when provided, otherwise the supplied entity UUID. Rich text fields require the documents API.
Update UI preferences for the first Fibery user returned by a workspace query. The supplied preferences are deep-merged with that user's existing preferences and written back through the Commands API.
Upload a file to Fibery storage for later attachment to entities or use in documents. Returns file metadata including the file ID and, when supplied, the secret.
Request an access token using an OAuth2 password grant or check the configured Fibery authorization. The result may contain the existing configured token rather than a newly issued token.
Test Fibery workspace credentials with a user query, supporting workspace tokens, API keys, basic auth and OAuth2. Returns the name of the first user returned by the query, which is not necessarily the authenticated user.
Check a filter definition for a Fibery data source before using it in a query. This check can execute a Fibery query, using the supplied query limit or a default of one.
The Fibery integration connects your Dench AI CRM directly to Fibery, so agents can read and act on your Fibery data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
26 actions are available for agents to invoke on your behalf. Every call runs through Fibery's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Fibery and click Connect — you'll authorize access through Fibery's own sign-in flow. No API keys or code required.
Ask an agent to use Fibery in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Fibery integration connects your AI CRM to Fibery, so AI agents can work with your Fibery 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 Fibery integration currently exposes 26 actions, including Count Entities by Type, Create Entity, Delete Custom App Endpoint, Delete Entity, Delete File, and Delete/Revoke Access Token. Agents invoke them on your behalf from chat or from automations.
No. You connect Fibery from your Dench workspace using Fibery's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Fibery's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Fibery connection from your workspace settings at any time.