- Category: project management
- Auth: API_KEY
- Composio-managed OAuth available? N/A
- Tools: 26
- Triggers: 0
- Slug:
FIBERY - Version: 20261101_00
Tools
Delete Custom App Endpoint
Delete Custom App Endpoint
Delete Entity
Delete Entity
FIBERY_DELETE_ENTITYPermanently 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’.Input Parameters
Output
Delete File
Delete File
FIBERY_DELETE_FILEDelete 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.Input Parameters
Output
Execute GraphQL Query
Execute GraphQL Query
FIBERY_EXECUTE_GRAPH_QL_QUERYExecute 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)Input Parameters
Output
Get App Information
Get App Information
FIBERY_GET_APP_INFORetrieve 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.Input Parameters
Output
Get Custom App Endpoints
Get Custom App Endpoints
Get Custom Apps
Get Custom Apps
Get Entities (Deprecated)
Get Entities (Deprecated)
FIBERY_GET_ENTITIESDEPRECATED: 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.Input Parameters
Output
Get Fibery Entity (Deprecated)
Get Fibery Entity (Deprecated)
FIBERY_GET_ENTITYRetrieve 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.Input Parameters
Output
Get File
Get File
FIBERY_GET_FILEDownload 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}Input Parameters
Output
Get GraphQL Schema
Get GraphQL Schema
Get User Preferences
Get User Preferences
Refresh access token
Refresh access token
FIBERY_POST_AUTH_REFRESH_TOKENCheck Fibery access credentials and return token information. For an OAuth-style integration, the result may include a new access token.Input Parameters
Output
Validate Fibery authentication and get access token
Validate Fibery authentication and get access token
FIBERY_POST_AUTH_TOKENRequest 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.Input Parameters
Output
Create Entity
Create Entity
FIBERY_POST_CREATE_ENTITYTool 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.Input Parameters
Output
Fetch Entities (Deprecated)
Fetch Entities (Deprecated)
FIBERY_POST_FETCH_DATADEPRECATED: 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.Input Parameters
Output
Count Entities by Type
Count Entities by Type
FIBERY_POST_FETCH_DATA_COUNTRequest 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.Input Parameters
Output
Fetch Datalist Options
Fetch Datalist Options
FIBERY_POST_FETCH_DATA_LISTFetch 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.Input Parameters
/datalist primary path and the /commands fallback (q/limit). NOTE: this caps ROWS fetched, not unique options — duplicate field values are deduplicated in the response, so len(options) may be smaller than limit.next_offset returned by the previous call. Applies to both the /datalist primary path (where it is forwarded as a query parameter) and the /commands fallback (where it is forwarded as q/offset).Output
Fetch Schema
Fetch Schema
FIBERY_POST_FETCH_SCHEMAFetch 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.Input Parameters
Output
Delete/Revoke Access Token
Delete/Revoke Access Token
FIBERY_POST_REVOKE_TOKENDelete/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.Input Parameters
Output
Validate Fibery Workspace Credentials
Validate Fibery Workspace Credentials
FIBERY_POST_VALIDATE_ACCOUNTTest 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.Input Parameters
Output
Validate Filter
Validate Filter
FIBERY_POST_VALIDATE_FILTERCheck 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.Input Parameters
Output
Update Entity
Update Entity
FIBERY_UPDATE_ENTITYUpdate 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.Input Parameters
Output
Update User Preferences
Update User Preferences
FIBERY_UPDATE_USER_PREFERENCESUpdate 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.