Skip to main content
Fibery logo
  • Category: project management
  • Auth: API_KEY
  • Composio-managed OAuth available? N/A
  • Tools: 26
  • Triggers: 0
  • Slug: FIBERY
  • Version: 20261101_00

Tools

Slug: FIBERY_DELETE_CUSTOM_APP_ENDPOINTDelete 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.

Input Parameters

string
required
Identifier of the custom app containing the endpoint
string
required
Identifier of the custom endpoint to delete

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

string
required
Full qualified type name in ‘Namespace/Type’ format (e.g., ‘Tasks/Task’, ‘Product Discovery/Feature’). This must match the entity’s type exactly. Use Get Entities action to find existing types.
string
required
The UUID (GUID) of the entity to delete in 8-4-4-4-12 hexadecimal format (e.g., ‘550e8400-e29b-41d4-a716-446655440000’). Use Get Entities or Get Entity actions to retrieve valid entity IDs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

string
required
The secret (fibery/secret) of the file to delete. This is NOT the file ID (fibery/id). When you upload a file, use the ‘secret’ field from the response. When querying files via commands API, request the ‘fibery/secret’ field.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

string
required
GraphQL query or mutation string to execute. For schema discovery, use introspection: ’{ __schema { types { name } } }’ to list all types, or ’{ __type(name: “Query”) { fields { name } } }’ to see available query operations. Standard queries follow the pattern: { queryName(args) { fields } }
string
Name of the Fibery space to query. Each space has its own GraphQL schema with different entity types. If not provided, the action will automatically try common space names (e.g., ‘Software Development’, ‘workflow’, ‘Product’). Spaces typically match your workspace’s app/database names.
object
Optional mapping of variable names to values for parameterized GraphQL queries.
string
Optional operation name when the query document contains multiple named operations.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

string
Optional custom app id to resolve app info via Fibery workspace proxy when base_url ends with /api.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: FIBERY_GET_CUSTOM_APP_ENDPOINTSList 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.

Input Parameters

string
required
Identifier of the custom Fibery app whose endpoints will be retrieved

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: FIBERY_GET_CUSTOM_APPSList Fibery workspace app records and their identifiers, titles, names and versions, subject to a configurable limit that defaults to 100.

Input Parameters

integer
Maximum number of custom apps to return (required by Fibery q/limit).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

string
required
Full database/type name in ‘Namespace/Type’ format. Common system types: ‘fibery/user’, ‘fibery/app’. Custom types follow pattern ‘YourSpace/YourType’ like ‘Product/Feature’, ‘Project/Task’. Use FIBERY_POST_FETCH_SCHEMA to discover available types.
integer
Maximum number of entities to return. Defaults to 100 to prevent oversized responses.
array
Optional filter expression using Fibery query syntax. Format: [operator, [field-path], value]. Operators: ’=’ (equals), ’!=’ (not equals), ’>’ (greater), ’<’ (less), ’>=’ (gte), ’<=’ (lte), ‘and’, ‘or’, ‘not’. Literal values are automatically parameterized (you can also use $-prefixed variables with ‘params’). Numeric values for text fields like ‘fibery/public-id’ are auto-converted to strings. Examples: [’=’, [‘fibery/id’], ‘$userId’] or [’>’, [‘task/priority’], 5] or [‘and’, [’=’, [‘status’], ‘active’], [’>’, [‘priority’], 3]]
integer
Number of entities to skip for pagination
object
Parameter bindings for $-prefixed variables used in ‘where’ clause. Map variable names to values, e.g., {‘$userId’: ‘uuid-string’, ‘$minPriority’: 5}. Literal values in ‘where’ are auto-parameterized, so this field is optional unless you explicitly use $-variables.
array
required
List of fields to return. PRIMITIVE fields (text, number, date, bool, etc.) are specified as strings. RELATION fields (entity references) require nested object syntax: {‘field-name’: [‘subfield1’, ‘subfield2’]} for single relations, or {‘field-name’: {‘q/select’: […], ‘q/limit’: ‘q/no-limit’}} for collections. Common primitive fields: ‘fibery/id’, ‘fibery/creation-date’, ‘fibery/public-id’, type-specific like ‘user/name’. For single-select enums use {‘enum-field’: [‘enum/name’]}. Use FIBERY_POST_FETCH_SCHEMA to discover field types (check fibery/primitive? in schema).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

array
Optional list of field names to include in the response. By default, only ‘fibery/id’ is returned. Specify additional fields using their fully-qualified names in ‘<namespace>/<field>’ format. Common fields include: ‘fibery/name’, ‘fibery/public-id’, ‘fibery/creation-date’, ‘fibery/modification-date’. For type-specific fields, use the type’s namespace, e.g., ‘user/name’, ‘user/email’ for users, or ‘Task/Status’, ‘Task/Assignee’ for custom types.
string
required
The unique entity identifier consisting of the fully-qualified type name followed by the entity UUID, separated by ’/’. Format: ‘<Namespace>/<Type>/<UUID>’. For system types like users, use ‘fibery/user/<uuid>’. For custom types, use the app namespace, e.g., ‘Product Discovery/Feature/<uuid>’ or ‘Project Management/Task/<uuid>’. The UUID is a 36-character string (with hyphens).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

string
Unique ID of the file. IMPORTANT: The Fibery API does NOT support downloading files by ID - only file_secret works. This parameter is provided for backward compatibility but will likely fail. Always use file_secret when available.
string
Secret UUID of the file to retrieve. This is the preferred identifier for downloading files. You can obtain the file secret from the ‘fibery/secret’ field when querying entities with file fields, or from uploaded file metadata.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: FIBERY_GET_GRAPH_QL_SCHEMARetrieve 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.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: FIBERY_GET_USER_PREFERENCESRetrieve UI preferences from the first user returned by a Fibery user query. The query does not explicitly filter for the authenticated user.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

string
required
The refresh token to validate and use for obtaining a new access token. For Fibery’s standard API, this can be the current API token. For OAuth2 integrations, this should be the refresh token from the third-party service.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

string
Password for OAuth2 password grant flow (only used if /auth/token endpoint exists; use placeholder for standard workspaces)
string
Username for OAuth2 password grant flow (only used if /auth/token endpoint exists; use placeholder for standard workspaces)
string
OAuth2 grant type (fixed as ‘password’)

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

string
required
Full qualified type name for the entity, e.g., ‘App/Type’.
object
required
Field values for the new entity. Relations must be provided as objects with ‘fibery/id’ keys, e.g., {‘assignee’: {‘fibery/id’: ‘<uuid>’}} or arrays of such objects.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

integer
Maximum number of entities to return. Defaults to 100. Use a large value like 10000 to fetch all entities.
array
Optional filter expression as a nested list. Format: [‘operator’, [‘field/path’], value] or [‘operator’, [‘field/path’], ‘$param’]. Use with ‘params’ for parameterized queries.
integer
Number of entities to skip for pagination.
object
Parameter bindings for variables used in ‘where’ clause. Keys should match $variable names in the where expression.
array
List of field names to include in the response. Must use ‘Namespace/field-name’ format matching the schema. If omitted, only ‘fibery/id’ is returned. Common fields: ‘fibery/id’, ‘fibery/name’, ‘fibery/creation-date’. Use FIBERY_POST_FETCH_SCHEMA to see available fields for each type.
string
required
The Fibery entity type to query, in ‘Namespace/Type’ format (e.g., ‘fibery/user’, ‘Project/Task’). System types use the ‘fibery/’ namespace. Custom app types use the app name as namespace. Use FIBERY_POST_FETCH_SCHEMA to discover available types in your workspace.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

object
Optional filter object for custom-app endpoints. Note: This action counts all entities of the type. For filtered counts, use Get Entities with a where clause.
string
required
Full Fibery type name in ‘Namespace/Type’ format. Examples: ‘fibery/user’, ‘Product/Feature’, ‘Sales/Lead’. Use Post Fetch Schema or Get Entities to discover available types.
object
Optional account/credentials object for custom-app endpoints. Not required when using workspace API token authentication.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

string
required
Field identifier to fetch distinct values for. Use fully-qualified field names in ‘Namespace/FieldName’ format. Note: for system entity ‘fibery/user’, fields use ‘user/’ prefix (e.g., ‘user/name’), while ‘fibery/id’ works for all entities.
integer
Maximum number of rows/options to fetch in this single call (1-1000). Forwarded to Fibery as the page size for both the /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.
integer
Zero-based offset for caller-driven pagination. On the first call pass 0 (or omit). To fetch the next page, pass the 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).
string
required
Full Fibery entity type name in ‘Namespace/Type’ format. Use the workspace schema to discover available types.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

boolean
Include field descriptions in the response
boolean
Include soft-deleted types and fields in the response

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: FIBERY_POST_OAUTH2_ACCESS_TOKENRequest 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.

Input Parameters

string
required
The authorization code received after user authorizes the OAuth2 request. This code is typically obtained from the redirect URL after user consent.
string
OAuth2 grant type. For authorization code flow, this must be ‘authorization_code’.
string
required
The redirect URI (callback URL) that was used in the initial authorization request. Must match exactly the URI registered with the OAuth2 provider.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

string
required
The unique ID of the API token to delete/revoke. This is the token’s identifier (e.g., ‘12345678’), not the token value itself. You can get token IDs by listing tokens via GET /api/tokens.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

string
required
Authentication type identifier. Supported values: ‘basic’ (username/password), ‘token’ (API token), ‘api_key’ or ‘api-key’ (API key), ‘workspace’ (workspace token), or ‘oauth2’ (OAuth2 bearer token). When fields dict is empty, uses the existing authorization from metadata.
object
Credential fields for the authentication type. Can be empty {} to use existing metadata credentials. For ‘basic’: {‘username’: str, ‘password’: str}. For ‘token’/‘api_key’: {‘token’: str} or {‘api_key’: str}. For ‘oauth2’: {‘access_token’: str, ‘expire_on’: str (optional ISO 8601 datetime)}.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

object
required
Filter definition to validate. For Fibery workspaces, use Fibery query keys: ‘q/select’ (list of fields), ‘q/where’ (filter conditions), ‘q/limit’ (max results), ‘q/offset’ (pagination), and ‘params’ (query parameters). For custom apps, structure depends on the app’s filter schema.
string
required
Data source identifier. For Fibery workspaces, use the full type name (e.g., ‘fibery/user’, ‘Project Management/Task’). For custom apps, use the source ID as defined in the app’s GET / response.
object
Account credentials for custom app authentication. Not required for Fibery workspace queries (workspace auth is handled via headers). For custom apps, include credentials as defined by the app’s auth schema.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

string
required
Fully-qualified Type name in ‘Space/Type’ format. Example: ‘Product Discovery/Opportunity’, ‘Engineering/Task’, ‘HR/Employee’. Use the Get Entities or Fetch Schema action to discover available types.
object
required
Mapping of field API names (in ‘Space/FieldName’ format) to new values. For text fields: use strings. For numbers: use integers or floats. For single-select/workflow states: use {‘fibery/id’: ‘<state-uuid>’}. For relations (single): use {‘fibery/id’: ‘<entity-uuid>’}. For relations (multiple): use [{‘fibery/id’: ‘<uuid1>’}, {‘fibery/id’: ‘<uuid2>’}]. IMPORTANT: Rich text fields (like description, notes, etc.) CANNOT be updated via this action. Rich text fields are collaborative documents that require: (1) querying for the field’s fibery/secret, then (2) updating via the /api/documents/commands endpoint with the ‘create-or-update-documents’ command. Use a dedicated rich text update action or the documents API directly.
string
required
The UUID of the entity to update in standard format (8-4-4-4-12 hex). Obtain this from a previous Get Entity or Create Entity response.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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.

Input Parameters

object
required
Dictionary of preference keys and values to merge into existing preferences. Common keys: ‘firstDayOfWeek’ (1=Monday to 7=Sunday), ‘weekends’ (list of day numbers), ‘isoWeekends’ (e.g., [6, 7]). Custom keys are also supported. Values are deep-merged with existing preferences.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: FIBERY_UPLOAD_FILEUpload 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.

Input Parameters

object
required
The file to upload to Fibery.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not