Guide
Connect Fibery to hundreds of other tools and automate repetitive tasks without code.
Make is a no-code automation and integration platform. Use it to wire Fibery into the rest of your stack:
Get notified in Microsoft Teams when someone assigns you to a task in Fibery.
Sync new leads from HubSpot CRM to Fibery.
Create a Bitbucket branch when a user story moves into a specific state.
For a simpler and pricier alternative, see Zapier Integration.
If the goal is to sync data into Fibery, check Integration templates first — a native integration is usually faster to set up than a custom Make scenario.
Fibery Modules
Triggers
Trigger | Description |
|---|
Entity is created | Fires the moment an entity is created. Instant. |
Entity is updated | Fires the moment an entity is updated. Instant. |
Entity is deleted | Fires the moment an entity is deleted. Instant. |
Triggers fire instantly, unlike the Zapier connection, which polls.
Searches
Search | Description |
|---|
Find entities | Searches entities of a selected type. Filter by text, date, and checkbox fields. |
Actions
Action | Description |
|---|
Create an entity | Creates a new entity of a selected type. Supports all field types, including File and Files. |
Update an entity | Updates an existing entity. Supports all field types, including File and Files. |
File fields
All Fibery actions and searches support File (single) and Files (multiple) fields.
Upload. Create an entity and Update an entity accept a file from any previous Make module - HTTP download, Google Drive, Dropbox, email attachment, an iterator over Airtable attachments - and attach it to a File or Files field on the entity.
Download. Find entities and the entity triggers return File and Files fields with the file URL and binary content, so downstream modules can re-upload the file elsewhere (S3, LinkedIn, Instagram, email, another Fibery entity).
Typical uses:
Attach an incoming email's CV to a new Candidate entity.
Migrate Airtable attachments into Fibery File fields in one scenario.
Publish a Fibery file to LinkedIn or Instagram when an entity changes state.
FAQ
When I create an entity via Make, does the file get attached in the same step?
No - Make handles it as two steps: first it uploads the file to Fibery, then it creates the entity and links the uploaded file in a separate transaction. From Fibery's perspective, the entity exists briefly without the file attached.
This matters if you're using an automation that triggers on entity creation and relies on a file being there — the file may not be linked yet when the trigger fires. Use Entity linked to → Files as your trigger instead of entity creation, so the automation runs only after the file is actually attached.