Bonsai and Fibery Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Connect Bonsai and Fibery to automate project management workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Bonsai and Fibery

Detailed info you need to know about Bonsai and Fibery integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Bonsai

    • Project Management
    • 5 triggers
    • 26 searches
    • 33 actions

    Client, project, time and invoicing suite for freelancers and agencies.[5]

  • Fibery

    • Project Management
    • 3 triggers
    • 8 searches
    • 24 actions

    Work management with databases you design yourself.[6]

How to connect Bonsai to Fibery

Set up your Bonsai and Fibery integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Bonsai and Fibery work in WEXTL?

WEXTL exposes actions and triggers for Bonsai and Fibery that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

Bonsai triggersFibery actions

Bonsai modules

  • Add a Record to a Note Puts a record on a note, whether a contact, company, deal or project, up to 10 per note. Set Record Type to the kind being added.
  • Add an Invoice Line Item Appends a line to an invoice, giving a Name, an Amount for the quantity and a Rate for the price per unit. Use Unit to say what the rate is charged per.
  • Cancel an Invoice Recurrence Ends the repetition of a recurring invoice or subscription. It works on the newest invoice of the series, which can differ from the first one.
  • Create a Company Registers a client company from its Name. Bonsai does not check for duplicates, so search first, and use Industry, Company Size and Source to describe it.
  • Create a Contact Saves a person with a Name and an Email, which must be unique in Bonsai. Use Job Title and Phone Number for further details about them.
  • Create a Deal Opens a deal under a Title for one Company. Without a Contact the primary contact of the company is used, and an empty Stage starts it in the first stage.
  • Create a Deal Comment Writes a note into the thread of a deal. Nobody is notified about deal comments.
  • Create a Document Builds a draft from a Template and sends nothing. Use Title to override the template title, and link it to one client by adding a Company, Contact, Project or Deal.
  • Create a Note Writes a note from Content in Markdown, where headings, bold, italics, lists, links and quotes work. Use Attach To to tie it to a record and Visibility to control who can see it.
  • Create a Project Starts a project with a Title and a Billing Type, owned by a Company that cannot be changed later. Retainers also use Billing Fee and Billing Cycle.
  • Create a Project Budget Begins a budget for a project, which needs a start date. Use Mode for money or time, with the Amount in hours for a time budget, and Alert Threshold to set the notification percentage.
  • Create a Task Adds a task named by Title. Use Parent Task to make it a subtask, never together with Project, and Assignee, Priority and Due Date to plan the work.
  • Create a Task Comment Writes a Comment into the thread of a task, where @-mentions are not supported.
  • Create an Invoice Creates a draft invoice for the Contact who is billed, adding Line Items if you have them. Picking a Project also needs its Company, and a blank Kind gives a single invoice.
  • Delete a Note Removes one note from your workspace.
  • Delete a Task Deletes one task from the Bonsai workspace.
  • Delete an Invoice Removes a draft invoice, or cancels one that has been sent or scheduled. A paid invoice cannot be deleted.
  • List Board Groups Gives each stage on your deal and project boards, with a Color, Position and Deal Probability. Use Board to keep the stages of one board.
  • List Companies Finds client companies in your CRM by Name. Archived companies are never returned.
  • List Company Activity Shows what happened with one company. Use Activity Types such as invoice.paid to limit the kinds, and From with To to bound the days.
  • List Contact Activity Pulls the activity of one contact. Add Activity Types such as email.sent or form.submitted to narrow it, and From with To for a range.
  • List Contacts Lists people in your CRM. Search with Name, look up the contact with one Email address, or use Companies to keep those linked to certain companies.
  • List Deal Comments Collects the comments on one deal. Use Kind to switch from written comments to another type.
  • List Deals Searches deals by Title or Deal Number, and keeps those with chosen Owners or Stages.
  • List Documents Fetches your proposals and contracts, optionally by Statuses, or those tied to a given Company, Contact, Project or Deal.
  • List Invoices Gets invoices with their line items. Use Invoice Numbers to fetch specific ones, or scope the search by Projects, Companies and Contacts.
  • List Notes Retrieves notes from your account. Use Attached To to limit them to one record, Created By for certain authors, and From with To for a span of note dates.
  • List Projects Lists your active projects unless Status asks for others. Use Title to search, Stages to keep chosen stages, and Budget Min with Budget Max if you hold the budget permission.
  • List Subtasks Gives the child tasks that sit under one parent task.
  • List Task Comments Gets the comments written on one task. Use Kind to look at another sort of comment instead of written ones.
  • List Task Statuses Gives each column of your task board with its Status, State, Color and Position.
  • List Task Tags Lists the tags defined in your account. Use Tag Type to keep one kind and Name to match a tag by its name.
  • List Tasks Shows tasks, with active ones by default through Scope. Use Due for a named window, Due From with Due To for exact days, and narrow with Assignees or Projects.
  • List Tax Rates Shows each tax set up in your account, giving a Name, a Rate and whether it is the Default.
  • List Team Members Gets everyone in your Bonsai account with their Role, Permission Profile and Status. Use Project to see only the people on one project.
  • List Template Categories Gives the category and industry names that filter templates. Use Kind to choose one of the two.
  • List Templates Lists templates to start documents from. Narrow by Categories, Industries or Region, and use Source for where they come from.
  • List Time Entries Returns logged time. Use From and To for a span of days, Members, Projects or Companies to scope it, and Billing Status to match billing states.
  • Log a Time Entry Records time for a Date using Hours and Minutes. A Task decides the project, and an empty Rate falls back to the rate of the project.
  • Make an API Call Runs a free-form request against the Bonsai REST API using your saved credential.
  • Remove a Project Budget Stops tracking the budget of a project.
  • Remove a Record from a Note Detaches a linked record from a note.
  • Remove an Invoice Line Item Removes one billable row from an invoice.
  • Retrieve a Company Gets one company with its Name, Industry, Company Size and social page addresses.
  • Retrieve a Contact Loads one contact, returning the Name, Email, Job Title and Phone Number.
  • Retrieve a Document Fetches a document with its Status, Expiration Date and Recipients.
  • Retrieve a Note Pulls a note and its body, as Content Html and Content Plain Text, along with the Note Links.
  • Retrieve a Task Looks up a task, with its Description Html, Due Date, Priority and Assignee ID.
  • Set a Document Pricing Table Replaces the whole pricing table of a draft document, so Packages must list every package. Use Last Seen Update to stop the write if the document changed since then.
  • Update a Company Edits the profile of a company, where a new Name renames it.

Fibery modules

  • Add a Comment Posts a Markdown Comment on an entity. The database needs the Comments extension, and the result carries the Comment ID and Document Secret.
  • Add Collection Items Links more entities to a collection field. Use Item IDs to name the entities to link, and items that are already linked are ignored.
  • Clear a Collection Empties the collection field of one entity so that it holds no linked entities.
  • Create a Database Sets up a database named in the form Space/Name, such as CRM/Lead, and the space must already exist. Use Color for a hex badge colour, and turn on Domain Database to make it available as cards on views.
  • Create a Field Defines a field from a Field Name such as Cricket/Salary and a Type. Turn on Unique to require different values, Read Only to block edits in the app, and use Text Style for the Text type.
  • Create a View Builds a board, table, list, calendar, timeline or whiteboard view inside a space from a Name, a Type and the Space ID. Use Meta to give the view settings as a JSON object.
  • Create an Entity Inserts an entity into a database with its ID, Public ID and Creation Date as the result. Use Fields to fill values straight away, and Entity ID to set a UUID yourself, otherwise Fibery chooses one.
  • Create or Update Entities Writes a JSON array of Entities in one call, creating new ones and updating matches. Give a Conflict Field with a Conflict Action to choose between skipping duplicates and updating the latest match.
  • Delete a Database Removes a database. Turn on Delete Entities to also delete its entities, and Delete Related Fields to delete the fields in other databases that point to it. A database with entities cannot be deleted without Delete Entities.
  • Delete a Field Deletes a field definition from a database. Turn on Delete Values to delete the stored values too, and a field that holds values cannot be deleted without it.
  • Delete a View Removes the saved view that has this View ID.
  • Delete an Entity Deletes one entity and returns its Entity ID with a Deleted flag.
  • Download a File Fetches the file behind a File Secret and returns the File with its File Name and Content Type.
  • Find Entities Searches a database and returns each match as an item, oldest first by default. Add Filters and Match to narrow the results, Fields to choose which values to read, and Sort Direction to reverse the order.
  • Get a Document Reads the rich text behind a Document Secret as Markdown, or use Format for HTML, JSON or plain text.
  • Get an Entity Reads one entity from a database using its Entity ID. Use Fields to limit the values returned, as the ID, public ID and dates always arrive.
  • Get Signed URLs for Files Creates download links for several files at once from their File Secrets. Each link works for 60 minutes and shows its Expires At.
  • Get the Schema Lists every database of the workspace with its fields. Turn on With Description to include the descriptions, which makes the schema several hundred kilobytes.
  • List Views Returns the views of the workspace with their Name, Type and Meta. Use View IDs or Public IDs to return only specific views.
  • Make an API Call Sends a free-form request to the Fibery REST API, signed with your saved credential.
  • Remove Collection Items Unlinks entities from a collection field. Use Item IDs to say which ones go.
  • Rename a Database Renames a database. Give its Current Name and a New Name, both as Space/Name.
  • Rename a Field Changes the name of a field, from the Current Name to the New Name written as Space/Name.
  • Replace Collection Items Makes a collection field contain exactly the entities given as Item IDs and removes every other item.
  • Run a Command Sends any Fibery command, such as fibery.entity/query, with Arguments given as a JSON object. It covers requests that have no dedicated module and returns the Result.
  • Run a GraphQL Query Runs a GraphQL query or mutation against the endpoint of one Space, with optional Variables as a JSON object. The reply carries Data and any Errors.
  • Search History Reads the change history, each entry with its Action, Date and Changed Values. Narrow it with Database ID, Entity ID, Author ID or Actions, and give both Start and End or neither, which gives the last 30 days.
  • Update a Document Replaces the whole text behind a Document Secret with new Content. Use Format to say whether the Content is Markdown, HTML or JSON.
  • Update a View Changes the Name or the Meta settings of the view with this View ID.
  • Update an Entity Edits an entity with the values of Fields, where a blank value changes nothing. Use Clear Fields to empty values instead, and a cleared field wins over a value given for it.
  • Upload a File Stores a File in Fibery and returns its ID and Secret. Attach it afterwards with Add Collection Items on the files field.
  • Upload a File from a URL Fetches a file from a web address into Fibery storage. Use Headers when the source needs them, Method to switch the request type, and File Name to store it under another name.
  • Watch Entity Changes (Instant) Fires instantly through a Fibery webhook when an entity changes, giving the Database, Field and Values Before. Use Effect to react to one kind of change, and each change in a delivery gives one run.
  • Watch New Entities Checks a database on a schedule for entities created since the last check. The first check reads up to Limit entities from the last day. Use Fields to add more values to each one.
  • Watch Updated Entities Polls a database for entities that are new or were modified since the last poll. Use Fields to receive extra values with each entity.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Bonsai and Fibery integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Bonsai and Fibery on WEXTL®

Claim your 3-day trial to build Bonsai with Fibery integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Bonsai and Fibery.

How do I connect Bonsai and Fibery?

Connect your Bonsai and Fibery accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Bonsai and Fibery?

Example: when the "Watch Company Activity" trigger in Bonsai fires, WEXTL can "Add a Comment" in Fibery. Bonsai has 5 triggers (including Watch Company Activity, Watch New Documents, and Watch New Invoices). Fibery has 32 actions (including Add a Comment, Add Collection Items, and Clear a Collection). Add filters and transforms between steps when you need them.[1]

Can Bonsai trigger actions in Fibery, and Fibery in Bonsai?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Bonsai and Fibery?

No. Bonsai-to-Fibery automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Bonsai integrate with Fibery in real time?

Yes. Trigger-based automations start the moment Bonsai (or Fibery) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Bonsai + Fibery integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Bonsai with Fibery?

You can build your Bonsai + Fibery automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Bonsai and Fibery integration.

  1. Bonsai and Fibery integration source code, module specs and credentials implementation.
  2. Our Bonsai and Fibery integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Bonsai and Fibery, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Bonsai integration information
  6. Fibery integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Bonsai and Fibery integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Bonsai and Fibery, or get started