Fibery Make integrationAutomate Fibery with Make.
Can Make keep your Fibery workspace in step with the rest of your tools? Yes. The Fibery Make integration gives you 6 modules: one instant trigger, four actions and one search. This guide walks you through the connection, a first scenario and the right module for each job.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Fibery Make integration do for you?
The Fibery Make integration links your Fibery workspace to Make, a no-code automation tool. You build a scenario (the automation itself, a chain of bricks called modules) that reacts when an entity changes in Fibery, or that creates, updates, finds and deletes entities for you, without writing code.
Product feedback that files itself. A customer fills in a form in another app, and Create an Entity turns the answer into a Fibery record in your feedback database. Nobody retypes it, and the product team triages it where they already work.
Status that follows the deal. When a deal moves in your CRM, Search Entities finds the matching Fibery project and Update an Entity changes it. Sales stops pinging product for updates.
A team channel that knows what changed. Watch Events fires the moment an entity is created, updated or deleted, so a message can go out to the people who care while the change is still fresh.
Know the limits before you start. The Fibery app in Make works on entities; anything else in the Fibery API goes through Make an API Call, where you write the request yourself. It also needs a paid Fibery account. Fibery has an n8n node too: the Fibery n8n integration page covers it, and n8n vs Make helps you pick a tool. New to Make? The Make training starts from zero.
How do you connect Fibery to Make?
- 01
Add a Fibery module
Open a scenario, add any Fibery module and click Create a connection. A connection is your Fibery account linked to Make once; every Fibery module in your scenarios reuses it afterwards.
- 02
Name it and authorize Make
Give the connection a name if you like, handy when you manage several workspaces. Then follow what Fibery asks: either authorize Make on the Fibery page that opens, or paste the key Fibery gives you.
- 03
Save and check the lists
Click Save. Back in the module, Make now lists what it can read in your workspace. If those lists fill up, the connection works and you can move on to the module settings.
Your first scenario with Fibery
GoalEvery 15 minutes, Make finds the Fibery entities that match a value you choose and updates each one.
- 01
Create the scenario
On the Scenarios page, create a new scenario, then click the big + in the middle of the editor to add the first module.
- 02
Add Search Entities
Search for Fibery, pick Search Entities and click Create a connection if you have none yet. No trigger here: the scenario starts on its schedule and the search is its first step.
- 03
Say what to look for
Fill in the module. Make lists what it can read in your workspace, so you pick from a list instead of typing names. Each entity found leaves as its own bundle, one item passed from module to module.
- 04
Add Update an Entity
Click the + on the right of Search Entities, choose Update an Entity and map the entity it found. Pick a change that takes the entity out of the search, or the next run finds it again.
- 05
Test, then switch it on
Click Run once and read the bundles each module received. When the right entities changed, keep the default schedule of every 15 minutes and switch the scenario on.
What starts a Fibery scenario
1 module starts a scenario when something happens in Fibery. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Fibery as soon as it happens.
Watch Events
Instant triggerIn Make“Triggers when an Entity (Task, Document, etc.) is created, updated or deleted.”
Watch Events launches your scenario whenever an entity is created, updated or deleted in Fibery. An entity is any record in your workspace: a task, a document, a feature. One module covers all three kinds of change.
What the Fibery app can do in Make
Fibery gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Create an Entity
ActionIn Make“Creates a new Entity (Task, Document, etc.).”
Create an Entity adds a new record to one of your Fibery databases, whether a task, a document or anything else you track, and fills it with data mapped from earlier modules.
Delete an Entity
ActionIn Make“Delete an existing Entity (Task, Document and etc)”
Delete an Entity removes an existing record from Fibery. It has to be told exactly which entity to remove, so it usually sits right after Watch Events or Search Entities, which hand it the right item.
Make an API Call
ActionIn Make“Perform an authorized API call”
Make an API Call sends a request of your choice to the Fibery API and reuses the connection you already set up. It is the way out when none of the ready-made Fibery modules does what you need.
Update an Entity
ActionIn Make“Updates an existing Entity (Task, Document, etc.).”
Update an Entity changes the values of a Fibery record that already exists, instead of creating a second one. The item stays in place and simply reflects what happened elsewhere.
Search Entities
SearchIn Make“Finds entities with matching field values.”
Search Entities looks through Fibery and returns the entities whose field values match what you ask for. You can get zero, one or several results, and each one travels through the rest of the scenario as its own bundle.
Need help automating Fibery with Make?
A person reads every message.
