Fibery + Stream Deck
project-management · team-collaboration · 0 triggers · 23 actions
Fibery is a work management platform designed to help teams collaborate, organize information, and manage their workflows. Add Fibery to your Stream Deck workflows with guided setup for the connection details it needs.
- No code
- Free tier
- One Stream Deck press
- Pairs with OBS & Elgato tools
- OAuth & keys handled in-builder
Popular ways to use Fibery
Add Fibery to a workflow and pair it with a Stream Deck button to run it in one press — handy for project-management tasks. Combine it with OBS, your Elgato tools, or any other app you connect to build a routine that fits how you work.
Browse all templatesTriggers & actions
Steps your workflow can perform in Fibery.
Count Entities by Type
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.
Create Entity
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 Entity
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/Revoke Access Token
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 OAuth2 authorization code
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 Query
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 Datalist Options
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.
Fetch Schema
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.
About Fibery
Fibery is a work management platform designed to help teams collaborate, organize information, and manage their workflows.
project-managementteam-collaboration
How to connect
1
Sign up for free
Create your Conductor Deck account: no credit card required.
2
Connect Fibery
Follow the setup prompts for Fibery. Conductor Deck handles the app authorization or required connection details inside the workflow builder.
3
Build a workflow
Add a Fibery action to your visual workflow canvas. Configure the options you need, then connect it to other steps.
4
Assign to Stream Deck
Sync your workflow to any Stream Deck button. Press once to trigger the entire sequence.
Frequently asked questions
- How do I connect Fibery?
- Sign up for Conductor Deck, then add a Fibery step to a workflow on the visual canvas. The builder walks you through the connection it needs — an account authorization or the required keys — right inside the step. No separate setup or code.
- Is it free?
- Yes — Conductor Deck has a free tier you can build and run workflows on, with no credit card required. Paid plans raise the monthly run limits and add advanced features when you need them.
- What's the difference between a trigger and an action?
- A trigger is the event that starts a workflow — for example, a Stream Deck button press or an incoming event from a connected app. An action is a step the workflow performs once it runs. A workflow is one trigger followed by one or more actions.
Automate Fibery with your Stream Deck
Sign up for free and start building Fibery workflows in minutes.