Fibery is a work management platform designed to help teams collaborate, organize information, and manage their workflows.
Count the total number of entities for a given Fibery type (database). This tool queries the Fibery workspace to return how many entities exist for the specified type. Use it to get totals like "how many users", "how many features", etc. Authentication: Requires a valid Fibery API token with read access.
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.
Tool to delete a specific custom app endpoint. Use after confirming the app and endpoint IDs to remove.
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.
Exchange an OAuth2 authorization code for access and refresh tokens. This action is used during the final step of the OAuth2 authorization code flow when building Fibery custom integration apps. After a user authorizes your app on a third-party service and is redirected back with an authorization code, use this endpoint to exchange that code for access tokens. Important: This endpoint is typically implemented by YOUR custom integration app (connector), not by Fibery itself. The action probes multiple common endpoint paths across your app's base URL and Fibery's OAuth service to maximize compatibility. Typical flow: 1. User initiates OAuth authorization via /oauth2/v1/authorize 2. User approves on the third-party service 3. Third-party redirects to callback_uri with an authorization code 4. Call THIS endpoint with the code to get access/refresh tokens
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)
Fetches one page of distinct values for a specific field from a Fibery entity type. Returns a list of unique options that can be used for filtering, dropdowns, or autocomplete. ONE Fibery API call is made per invocation; pagination is caller-driven via the `offset` and `limit` request fields and the `next_offset` response field. The action first attempts the `/datalist` endpoint and, if that endpoint is unavailable on the workspace (404/405/501), falls back to a single `fibery.entity/query` command via `/commands`.
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.
Tool to retrieve application information. Use when you need the version, name, description, authentication methods, and available data sources before further operations.
Tool to list custom app endpoints. Use when you need the available custom endpoints for a given app before invoking them.
Tool to list all custom apps in the Fibery workspace. Use when you need the identifiers of all custom apps.
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.
DEPRECATED: Use PostFetchData instead. Retrieve a single Fibery entity by its unique identifier. Use this tool when you need to fetch details of a specific entity whose ID you already know. This is useful for: - Getting full details of an entity after listing entities with FIBERY_GET_ENTITIES - Refreshing entity data after an update - Fetching specific fields of an entity using the 'expand' parameter The entity_id must combine the type name and UUID (e.g., 'fibery/user/<uuid>'). Use FIBERY_GET_ENTITIES first if you need to discover entity IDs.
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}
Retrieves the GraphQL schema for the Fibery workspace using standard GraphQL introspection. Returns the schema as a JSON string that includes all types, queries, mutations, and their fields. Use this to discover available GraphQL operations before executing queries.
Tool to retrieve the current user's UI preferences. Use after authentication to tailor UI to user settings.
Tool to validate and refresh an access token. For Fibery's standard API, this validates the current token is still working (Fibery tokens don't expire). For OAuth2 integrations with third-party services, this could be used to refresh tokens through the validate endpoint.
Update an existing Fibery entity's fields. Use this to modify text fields, numbers, single-select states, workflow states, or relation fields on an entity. Prerequisites: - You need the entity's UUID (fibery/id) - obtain via Get Entities or Create Entity. - You need the fully-qualified type name (e.g., 'Engineering/Task'). - For workflow/state fields, you need the state's UUID. Limitations: - Rich text fields cannot be updated via this command. - Entity collection fields should be updated after entity creation.
Tool to update the current user's preferences by using the Commands API. It fetches the current user id and preferences, merges the provided payload, and writes back the merged object into 'fibery/ui-preferences' of the current fibery/user.
Upload a file to Fibery's file storage. Use this action to upload files that can later be attached to entities or used in documents. Returns file metadata including the file ID and secret needed for subsequent operations.
Validates Fibery API authentication and returns the active access token. This action validates that your API token is working correctly by attempting to query the Fibery API. For standard Fibery workspaces, it validates the pre-configured API token from the Authorization header. Behavior: 1. First attempts OAuth2 password grant at /auth/token (rare, only custom installations) 2. If /auth/token returns 404 (standard case), validates existing token via /commands endpoint 3. Returns the validated token that can be used for subsequent API calls The returned access_token should be used in the header: `Authorization: Token <access_token>` Note: Most Fibery workspaces use pre-generated API tokens (created in workspace settings), not username/password authentication. The username/password parameters are only used if a custom OAuth2 endpoint exists.
Validates Fibery workspace credentials by performing a test API query to retrieve the authenticated user's name. This action verifies that the provided credentials (or existing metadata credentials) are valid and have access to the workspace. Use this to confirm authentication before executing other Fibery operations. Supports multiple authentication types: workspace tokens, API keys, basic auth, and OAuth2.
Validates filter definitions before executing data queries. Use this tool to verify that a filter's structure and syntax are correct without actually fetching data. For Fibery workspaces: Validates by executing a safe test query with limit=1. For custom apps: Calls the app's POST /validate/filter endpoint if available. Returns validation result indicating whether the filter can be safely used.