Fibery

Syncs your project data across tools, automates entity creation from external triggers, and runs complex GraphQL queries to keep your workspace organized.

Try Fibery in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Fibery integration

    • Describe the outcome and Ceven picks the right Fibery calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Fibery data, across all 23 of its actions.
  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Fibery access.
    • Per user and per environment credentials instead of shared keys.
  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Fibery, when, and on whose behalf.
    • The agent pauses and asks when Fibery is unclear instead of plowing ahead.
  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Fibery.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Fibery action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Fibery, and when to use it.

Create entity
Use this when you need to persist a new record, such as a new project task or customer lead, with specific field values.
Update entity
Use this to modify an existing record in your workspace, such as changing a task status or updating a due date.
Get entity
Pull detailed information for a specific Fibery entity using its unique ID.
Get entities
Query multiple entities of a specific type with optional filters and pagination settings.
Execute GraphQL query
Use this for complex data fetches or mutations that require the full power of the GraphQL API.
Get GraphQL schema
Pull the current workspace schema to understand available types and fields for integration mapping.
Upload file
Use this to attach a local file to a Fibery record via the files API.
Get file
Retrieve a file by its secret or ID to download raw bytes and metadata.
Delete entity
Permanently remove a specific Fibery entity by its ID. Use only after verifying the record is no longer needed.
Get data count
Return the total number of records for a specific Fibery type or source.
Fetch data from source
Pull data from a specified external source connected to your Fibery space.
Get custom apps
List all custom apps installed in the workspace to find necessary identifiers for app operations.
Delete Custom App Endpoint
Tool to delete a specific custom app endpoint. Use after confirming the app and endpoint IDs to remove.
Delete File
Tool to delete a specific file. Use when you need to remove a file from Fibery by its ID.
Authenticate (validate token via API call)
Tool to validate existing Fibery personal API token by performing a real API call. If the call succeeds, returns the token value extracted from the Authorization header. Use the returned token in the `Authorization: Token <value>` header fo
Get App Information
Tool to retrieve application information. Use when you need the version, name, description, authentication methods, and available data sources before further operations.
Get Custom App Endpoints
Tool to list custom app endpoints. Use when you need the available custom endpoints for a given app before invoking them.
Get Fibery Entity
Tool to retrieve detailed info of a specific Fibery entity by its ID. Uses Fibery Commands API (fibery.entity/query) filtered by fibery/id with q/limit = 1.
Get User Preferences
Tool to retrieve the current user's UI preferences. Use after authentication to tailor UI to user settings.
Refresh access token
Tool to refresh an access token using a refresh token. Use when the current access token has expired and a valid refresh token is available.
Authenticate with username and password
Tool to authenticate with Fibery using resource owner password credentials. Use when you need an access token by providing username and password. Include the returned token in the `Authorization: Token <access_token>` header for subsequent
POST_FETCH_DATA_COUNT
Tool to return the count of records for a given Fibery type (source). Uses Fibery commands API and returns the total number of entities of the type.
Fetch Datalist Options
Tool to fetch options for a datalist filter field. Use after retrieving field metadata to build dynamic filters.
Fetch Schema
Tool to fetch predefined data schema. Use after authenticating when mapping and integrating Fibery data.
Exchange OAuth2 authorization code
Tool to finalize OAuth2 authentication for Fibery custom apps. Use when exchanging an authorization code for access and refresh tokens after user authorization. Notes: - In Fibery custom app flows, the access_token endpoint is typically imp
Revoke Access Token
Tool to revoke an existing Fibery API access token. Use when invalidating a user session or logging out.
Validate Fibery account
Tool to validate account credentials. Use when confirming provided credentials (and optionally refreshing OAuth2 tokens) before further API calls.
Validate Filter
Tool to validate filter definitions. Use when ensuring filter structure and syntax are correct before running a data query.
Update User Preferences
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.

29 actions · scroll to see them all

Frequently asked questions

Ceven uses personal API tokens or OAuth2 flows depending on your setup. When you connect your account, we store the token encrypted at rest. For custom app flows, we exchange the authorization code for an access token and a refresh token. This allows the agent to maintain a persistent connection to your workspace without requiring you to reauthenticate every few hours. You can revoke this access at any time from your Fibery account settings, which immediately kills the token and prevents the agent from making further calls to your data.
Yes. Because Ceven can execute raw GraphQL queries, it is not limited to simple one to one updates. The agent can navigate deep entity relations, such as finding all tasks linked to a specific sprint which are then linked to a parent epic. When creating entities, the agent can pass the IDs of related records to establish these links automatically. This means you can build workflows that maintain the integrity of your relational data model without having to manually link every single single record.
Ceven respects the Fibery API rate limits to ensure your workspace remains stable. A known quirk of the Fibery API is that very large GraphQL queries with deep nesting can occasionally time out or be throttled by the server. To handle this, Ceven automatically implements pagination for list requests and breaks down massive mutations into smaller chunks. If you are managing tens of thousands of entities, you may notice a slight delay as the agent walks the cursor to ensure no data is missed during the sync.
Currently, Ceven focuses on managing data within your existing schema. This means it can create, update, and delete entities of types that already exist in your space. It cannot programmatically create a brand new entity type or add new fields to an existing type via the API. You should define your spaces, types, and fields within the Fibery UI first. Once the schema is set, the agent can fully automate the data flow into those structures using the provided field identifiers.
When a workflow triggers a file upload, Ceven sends the binary data to the Fibery Files API. Once Fibery accepts the file and returns a file ID or secret, the agent then updates the target entity to link that file to the record. This two step process ensures that the file is safely stored in Fibery storage before the entity is updated. You can use this for attaching screenshots from error reports or uploading contracts from a CRM directly into your project management space.
Yes, Ceven can interact with custom app endpoints. The agent can list the available custom apps in your workspace and then invoke specific endpoints associated with those apps. This is particularly useful if you have built custom logic within Fibery that is exposed via an endpoint. The agent can send the required payload to the endpoint and use the response to trigger further actions in your workflow, effectively bridging the gap between custom app logic and external tools.
Ceven uses a combination of polling and webhook listeners to stay in sync. When a change occurs in Fibery, the agent can be triggered to run a specific workflow. Because it has access to the entity history and current state, it can determine exactly what changed and take the appropriate action. For example, if a status changes to Done, Ceven can immediately trigger a billing event in your accounting software. This ensures that your external tools are always a mirror of your Fibery workspace state.
Data security is handled through industry standard encryption. We never store your Fibery data on our own permanent disks; we only use it as transient context to execute the logic of your workflow. All communication between Ceven and Fibery happens over HTTPS using TLS encryption. We follow the principle of least privilege, meaning the agent only accesses the entities and fields required to complete the specific task you have prompted it to do, and all access is logged for your review.

Alternatives to Fibery

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Fibery and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free