Automation management using databases + Prompt to create script comment

Fibery Showcase
1

Automations in Fibery I find currently ‘underdeveloped’ in that management of automations ans scripts is not easy. Seen the focus on AI and workflows, this becomes even a greater need, so its likely that at some point this will be improved. In the meantime I have the following solution:

Automation & Script management using databases

Scripts in Fibery are dependent on the correct automation setup.
This is how I manage that:

  • ‘Automation’ database (with rich text field describing the automation)
  • ‘Script’ database (with a rich text field that automatically inserts an empty code block)

Each automation has its own script(s), and you can have multiple versions of a script for the same automation, that’s why its useful to have the separate databases automation + Script.

I have a number of useful fields in both database, in order to categorize them with tags, to indicate what methods or dependencies are included, automatic description + summary etc.

image
image1635×569 102 KB

Adding the automation setup as comment in the script

Another good practice that I started using, is to always include the required automation setup as comment in the script itself. That ensures that you or another admin can easily reproduce the automation even without having the automation entity attached.

Easy way: take a screenshot of the automation setup, and feed it to AI.

Here is a prompt that I made for that purpose:

–start of prompt–

Please analyze the provided screenshot of the Fibery.io Automation configuration and create a comment block that describes the required automation setup. Use the following guidelines:

  • Display the comment as a code block using triple backticks (```) at the start and end.
  • Start the comment with /** and end with */.
  • Begin the comment with the line * Required Fibery.io Automation Setup:.
  • Preserve the exact structure and labels as shown in the screenshot, including “When” and “Step 1” sections, using the same indentation levels (e.g., “When” and “Step 1” at the top level, actions indented with two spaces, and fields indented with four spaces).
  • Use the exact action numbers (e.g., “1:”, “2:”, etc.) as shown in the screenshot, instead of dashes, with a space after the colon.
  • Include field names exactly as shown (e.g., with “#” for “MaxLevel”, or full labels like “Split BlockBody to BlockTree by Header ”), followed by a colon (“:”) and a space, then their corresponding values.
  • Remove any headers like ‘FIELDS’ and helper text sentences such as “Set new values for fields”, “Update Config linked to Page”, “Create new TargetBlock and link to Page”, or “Execute JavaScript code”.
  • Ensure proper spacing: include a space after each colon (e.g., “Field: Value”), and avoid extra spaces at the end of lines.
  • Do not add any additional information, timestamps, or notes beyond what is shown in the screenshot.
  • Example: For a screenshot with the provided structure, the output should look like:
    /**
 * Required Fibery.io Automation Setup:
 * When
 *   1: Button Clicked
 * Step 1
 *   2: Update
 *     Config: Split BlockBody to BlockTree by Header [ ]
 *   3: Update
 *     SourceBlock: Ask user to provide value
 *   4: Update Config
 *     # MaxLevel: Field value will be cleared
 *     IncludeHeaderInBody: Field value will be cleared
 *   5: Update Config
 *     # MaxLevel: Ask user to provide value
 *     IncludeHeaderInBody: Ask user to provide value
 *   6: Add TargetBlock
 *   7: Script
 */

–end of prompt–

Example screenshot

Best is to use the Zoom function in your browser to have as much on your screenshot as possible, or to simply to feed AI multiple screenshots in the same message.

image
image671×1345 67.9 KB

Hopes for future improvements:

Fetching Script from Entity field:

Note that currently automations do not allow to fetch a script from an entity its Document field. This is for security reasons, but I seen the great benefit it would have to allow this for admin users, the setup as shown above would creating and updating scripts much easier.
The script editor in fibery is very minimal, so using an entity for that is a great solution.

Automations as entities

Again, seen the importance and complexity of Automations, it is surprising that they are not yet implemented in Fibery as automation ‘Entities’, or that an automation its configuration can automatically be inserted in any database entity.
Recently there were posts in the community around automatic automation creation using AI, and that would probably allow for building and maintaining an automation management system using Automation and Script databases.

Maybe its good to brainstorm about this in this topic.

1 Like
2

Replacing all buttons with Rules

I also try to minimize the use of Buttons, because of the overload of buttons in the context menus that cannot be filtered or grouped.

My solution to that is under development, but involves always using Rules and not Buttons.

  • I use one single ‘Operation’ button plus a to-one relation field to the database ‘Automation’ (or Rule of you like).
  • Upon clicking the Operation button, the user can select in the popup field the desired automation and click Run.
  • Another automation will be triggered when the Automation field is updated.
    I actually refine that step by adding a field ‘TriggerTime’ which is a datetime field that gets populated with the current datetime in the button automation. This is cleaner and more reliable.

The challenge here is to design a solution to get additional user input in possible follow-up steps in connected automations. I remember having posted an example in the past, if needed we can explore this further here

1 Like