Fibery n8n integrationAutomate Fibery with n8n.
Where does the Fibery n8n integration actually start? The node covers 6 operations across 2 resources, from listing databases to creating, reading, updating and deleting entities. A webhook trigger listens to a database and hands each change to a workflow within a few seconds.
Community node This node is not shipped with n8n: it is a community package (@fibery/n8n-nodes-fibery) you install from Settings › Community nodes on a self-hosted instance. npm
Verified Trustpilot reviews · AI, automation & growth agency
What does the Fibery n8n integration give you?
The Fibery n8n integration adds two nodes to a workflow: one that reads, updates, writes and deletes data from Fibery through 6 operations spread over 2 resources, Database and Entity, and a trigger. The trigger handles Fibery events on a database and hands each of them to a workflow as they happen, without any polling in between.
Fibery holds the work: features, bugs, accounts, candidates, whatever the workspace models as databases and entities. n8n holds the plumbing around it. The node exists so a workflow can read an entity, write one back, or sweep a whole database without anyone opening the app.
Three shapes come up again and again. First, intake: a form or an inbox produces something that belongs in Fibery, and entity.create puts it in the right database with the fields already filled. Second, sync out: entity.getMany pulls a filtered slice of a database on a schedule and pushes it into a reporting sheet such as Google Sheets, or mirrors it into a tracker like Jira Software so the engineering side sees the same state. Third, reaction: the trigger fires on a database and the workflow posts to Slack or opens a task in ClickUp before anyone refreshes a view.
The node is deliberately narrow. Entities and databases are all it touches, and only the 6 operations listed below. Anything else in the Fibery API, and any operation the node skips, goes through the HTTP Request node, which calls any endpoint of the API while reusing the same credential through predefined authentication.
Two limits are worth knowing before building. The package is a community node, so it lives on a self-hosted instance and gets installed by hand; n8n Cloud only accepts verified community nodes. And the trigger carries no event list: it watches a database, and the workflow decides what to do with what arrives.
On the platform question itself, the trade-offs between self-hosting and a hosted tool are laid out in the n8n review, which is the better place for that comparison than a node page.
How do you connect Fibery to n8n?
- 01
Install the community package
The Fibery node is not bundled with n8n. On a self-hosted instance, open Settings, then Community nodes, and install the npm package
@fibery/n8n-nodes-fibery, currently at version0.1.26. n8n restarts the node list and two entries appear in the node panel: Fibery and Fibery Trigger. On n8n Cloud the install only goes through for verified community nodes. - 02
Create the Access Token credential
Authentication uses an access token, stored in the credential type
fiberyTokenApi. Open the Credentials menu in n8n, create one, paste the token from Fibery and save it. A credential is created once and reused across every workflow, so the token stays in one place. The node then offers it in its own dropdown, and so does the trigger. - 03
Point the node at a database
Drop the Fibery node on the canvas, pick the credential from the list, then choose a resource, Database or Entity, and an operation. Most operations ask for Database, a resource locator that lets you pick from a list or pass a value with an expression such as
{{ $json.database }}, which is how n8n reads a field from the incoming item. A required field left empty stops the node.
What starts a Fibery workflow?
Fibery Trigger is the node that starts a workflow when Fibery calls n8n. Activate the workflow: n8n gives you the webhook URL to register in Fibery, and every call becomes an execution.
What you see in n8n
Configuration notes
01Set up the Fibery Trigger
The Fibery Trigger node handles Fibery events on a database and starts the workflow with them. It comes from the same community package, runs on version 1, and takes the same Access Token credential as the main node. There is no event list to tick: the node watches one database and passes on what happens there.
Key parameters
- Database: required, a resource locator pointing at the Fibery database to listen to. Pick it from the list once the credential is connected, or pass a value with an expression when the database is decided by an earlier node.
02How events reach n8n
This trigger works by webhook, which means a URL that Fibery calls whenever something happens. n8n registers that URL with Fibery when the workflow is activated, so there is nothing to schedule and nothing to check on an interval. Each event lands in the workflow within a few seconds of happening in Fibery.
That has one consequence worth planning for: the URL is registered on activation, so a workflow left inactive receives nothing, and anything that happened while it was off does not arrive later. If a run needs to catch up, a second workflow with entity.getMany over the same database covers the gap.
What can the Fibery node do?
The Fibery node exposes 6 operations across 2 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
Database
1 operationGet many databases
database.getAllWhat you see in n8n
Notes & use cases
This operation returns the databases of the Fibery workspace, which is how a workflow discovers what the workspace actually contains instead of hard coding a name. It takes no parameters at all: connect the credential, run it, and the list comes back.
Entity
5 operationsCreate an entity
entity.createWhat you see in n8n
Notes & use cases
Create writes a new entity into a Fibery database and returns it, so the rest of the workflow can keep working on the record that was just created.
Key parameters
- Database: required, the database the entity lands in, picked from the list or set with an expression such as
{{ $json.database }}. - Fields: the values to write, added one by one behind the Add Field button.
- Output: Simplified, Raw, or Selected Fields, which decides how much of the created entity comes back.
- Fields To Select: the fields to include in the response when Output is set to Selected Fields.
Delete an entity
entity.deleteWhat you see in n8n
Notes & use cases
Delete removes one entity from a database. It is the bluntest operation of the node and the one to guard with an IF node, because nothing in the workflow puts the record back.
Key parameters
- Database: required, the database the entity belongs to.
- Entity: required, a resource locator for the entity itself. Selecting it from the list works while building; in production the value usually comes from a previous node, as an expression.
Get an entity
entity.getWhat you see in n8n
Notes & use cases
Get reads a single entity and hands its fields to the next node, which is what most enrichment workflows need before deciding anything.
Key parameters
- Entity: required, the entity to read, alongside the Database it belongs to.
- Output: Simplified keeps the payload readable, Raw keeps everything, Selected Fields narrows it down.
- Fields To Select: the list of fields to return when Output is Selected Fields.
- Download Files: an option that downloads a file when the database field holds one, instead of returning a reference to it.
Get many entities
entity.getManyWhat you see in n8n
Notes & use cases
Get Many sweeps a database and returns several entities at once, filtered on the fly rather than sorted out later in the workflow.
Key parameters
- Database: required, the database to read.
- Limit: the maximum number of entities returned, so a wide database does not flood the run.
- Filter: None takes the database as it is, Build Manually opens the conditions.
- Must Match: All Filters requires every condition, Any Filter accepts one.
- Filters: the conditions themselves, each one a field, an Operator such as Is, Contains or Is Empty, and a Field Value.
Update an entity
entity.updateWhat you see in n8n
Notes & use cases
Update changes the fields of an entity that already exists and returns the updated version, which makes it the operation that closes most loops: something happened elsewhere, Fibery gets the new state.
Key parameters
- Entity: required, the entity to modify, in the required Database.
- Fields: the fields to overwrite, added behind Add Field; untouched fields stay as they are.
- Fields To Select: pairs with an Output set to Selected Fields to keep the response small.
Need help automating Fibery with n8n?
A person reads every message.