Improve the Chrome extension to add entities through entity forms and prepopulation of form fields

[Yuri_BC]

Yes, there is a workaround:

This script places an Embedly frame in the Description of an entity created by the Fibery Chrome extension

This is a workaround for the limitations of using html iframes in Fibery. Script 1 adds the URL to a dedicated URL field Script 2 copies the embedly frame from a template entity and replaces the URL in it. [chrome_1UgnqHtDxO] Script 1 const fibery = context.getService('fibery'); for (const entity of args.currentEntities) { // Fetch the content of the Description field const descriptionContent = await fibery.getDocumentContent(entity.Description.Secret); // Extract the first URL…

[YvetteLans]

@Illusory

@YvetteLans I presume you can create a semi-workaround to update fields by creating replace to have AI update other fields based on what you provide.

Totally missed your comment! Thanks!

@Illusory

Not as straightforward as having functionality built into the extension and a bit hacky but still may be useful for some.

Yes it can be useful for our own use cases. But we are selling workspaces to customers → I’m afraid it’s not a very intuitive workflow for them.

[Minh_Tri_Do_Hang]

You’re genius

[helloitse]

@Chr1sG I created a video explaining why I like using the ClickUp extension that can speak to the needs expressed in this thread.

@Chr1sG

The current extension is intended for quick capture of information from the web into Fibery. The comments above seem to indicate a need for ‘quick creation’ of entities, potentially including population of Fibery-specific field data, without leaving the current (non-Fibery) browser tab.
Is this independent of capturing (some of) the information available in the current tab, I wonder?

For me it is definitely the need to populate Fibery specific data without leaving the current tab. The added bonus of the ClickUp extension right now is bi-directional linking from the inbox.

[Chr1sG]

The functionality you’re describing is very much an browser integration specifically for Gmail as far as I can see, rather than a generic web browser extension.
Have you considered using Ply to create buttons within Gmail? This might allow you to achieve a very customised integration between Gmail and Fibery.

[helloitse]

@Chr1sG

The functionality you’re describing is very much an browser integration specifically for Gmail

The team at ClickUp built one extension that handles Gmail & Outlook specially and still facilitates bookmarking and capturing across the web. I am excited about Ply as a current solution! I caught wind of it when looking at the ProductHunt 2023 awards.

But I would love to see Fibery own data entry to eliminate the need for external tools.

[Chr1sG]

@helloitse

The team at ClickUp built one extension that handles Gmail & Outlook specially and still facilitates bookmarking and capturing across the web.

Indeed. I meant that the Fibery extension is designed to do one thing - capture data from websites, whereas the ClickUp extension serves many purposes.
At the moment, there is no intention to devote resources to expanding the bookmarking capabilities of the extension nor to extend the functionality to support other use cases.

[Yuri_BC]

I’m happy to start working on an unofficial Fibery chrome extension that has more features. Its not a high priority for me at the moment so it may take a while. @Chr1sG its this one right? GitHub - Fibery-inc/fibery-web-extension

Are the contributors associated with the Fibery dev team?

Contributors3

• Mavrin Konstantin Krivlenia
• Maxim-Filimonov tpaktop
• rawkode David Flanagan

[Chr1sG]

@Yuri_BC

its this one right?

Yep

@Yuri_BC

Are the contributors associated with the Fibery dev team?

Y, N, N

[Oshyan]

Please do improve the existing extension! It would be nice if it at least reaches feature parity with the official Notion one.

[Yuri_BC]

I did not start with working the extension yet, but am currently using a workaround: I insert hashtags in the title of the Chrome extension form, and use a script that checks a ‘TagMapping’ database to get a target database to automatically convert it. So in the extension I use only one database ‘Bookmark’ that when it contains a hashtag is converted. Other automations like linking and complete workflows are possible simply by adding rules that the TagMapping can trigger. For example hashtags in the body of the extension form can allow specific fields to be populated, users assigned, etc. If you like an example let me know.