Guide
Forms - the most popular way to grab outside data from users, customers, co-workers, and potential employees. After you've created your first form, go through our sub-guides where we offer potential workflows and combinations you can try for your unique business needs.
https://youtu.be/Pa4u_JCwn9Q
Make a Form
Find one of your Spaces and click the + button to add a new View.
Click Form and you will be brought to a blank page. In the top right of your screen, there will be a dropdown asking you to select a Database.
And just like that, we have a form! Notice on the right sidebar that the fields created in the Database you chose are the ones available as a field. You can choose which ones to show to the public and which ones are only used internally.
The form description is a rich text field, so you can use / for rich text commands.
Preview
You can Preview the form to see what it will look like to the end user. Anything filled out in Preview mode will be submitted to the database it is linked to. This is a great way to test the flow of the form and any automations that you've built, like notifying your Customer Success Manager of a new piece of feedback, or HR of a new job application.
An existing form opens in Preview mode by default, thus it is easier to add new entities for users.
Sharing
To share the form with your users, click the Share button to generate a public link. Anything that is currently being shared will have a dot by Share.
You can embed a Form View into your website. Click Share, copy the Embed Form code, and insert it into your gorgeous website page.
Form View preview in social media and web works shows actual form name and description
Tips and Hints
Here are some hints that will help you to create a useful form.
If you have some forms created for a database, you can select them in Quick Add. It may be handy if you have several scenarios for new entity.
Use default values in Rich Edit fields to capture additional info
Sometimes you don’t want to add new fields to the database to capture some info, in this case, you can capture it into a single rich edit field.
Here we have a Description rich edit field with some questions, so a user can answer these questions inline.
Select between compact and full layout for quick add
Compact Form is not displaying fields descriptions and it is more dense. Full form shows all the details and it more sparse.
Choose desired layout for every form on every view:
Use hidden fields to set some fields automatically
In some cases, you just want to hardcode values in fields. For example, you can create a checkbox “Created via Form” and mark it in a Form View.
You can use it in automations to execute some actions for entities created via form view.
Create a meaningful form description
You can explain why the form should be filled out and include some links to useful pages.
Create a separate database to capture form results
You can collect data into an existing database, but in some cases, it is better to create a new database. For example, we created a separate Application database to collect requests for Startups, Educational, and Nonprofit organizations.
Then we linked the Application database to the Account database in our CRM Space and set up Slack notifications for every new Application. Thus we are not overloading the Account database and can create better Form Views.
Set initial field values via URL
You can pre-fill parts of forms or connect created entities to existing stuff. Add required values in the URL after the ? symbol as query parameters, here is the example:
fibery_io/public/forms/wLLEvDIy?What+is+your+name%3F=Dmitry&date=2022-01-01&free-shipping=yes&price=340
Check detailed guide how to do it → Set Initial Field Values via URL Parameter on Form View
You can also enable Allow to set hidden fields via URL setting for a Form. When this option is enabled, any database field can be set via URL (well, except rich text field).
FAQ
If you're missing any functionality - please, let us know 💖
Can I get a source of where was the form filled in? (ex. landing, user id, page name, etc.)
Unfortunately, not at the moment.
Why can't I choose the formula field on the Form?
It's quite hard to do, since the formula result is only calculated when the entity exists, and the entity doesn't exist til the form is submitted. So we postponed that for a while. Please, let us know about the use case you have in our support chat.
How do you get notifications when a user has completed a form and therefore a record has been created in the database?
Please, go to the database that your form is populating. There you may open “Automations” tab. Set it up as follows:
1. When <Database name> created (trigger)
2. Then send notification (action)
You can choose which users it goes to. If those users have turned on email notifications in their settings they’ll get an email, if not it just goes to inbox.
If you want it to ONLY trigger when the form is used, then you need to create a new field like “form triggered” (maybe a checkbox). You will have to add it to the form pre-ticked, and then change the tick box “hidden” on the form (not excluded, hidden). Now go to the rule you just created and add a filter to Step 1 specifying the relevant checkbox is ticked.
Please, check this community topic for more details
Can I share the Form publicly but only among employees of my company? (based on the email domain)
Not yet. Please, let us know if this functionality is needed.
I am trying to use this iframe to show a form on my website. I want to change the background color of the form to match that of the website, it is possible to do?
Unfortunately no, but it is possible to specify theme, by appending &force-theme=dark or light
Why does the form sometimes preselect a different default value for some users?
We've set up a default form for Task creation with "Task" as the default type. However, for one user, the form shows "Bug" as default instead. Why does this happen?
This behavior depends on where the form is opened from. If a user opens the form from a specific view (e.g. Board, Table, Timeline), Fibery applies the view's filters as default values. This ensures that newly created entities automatically match the filters of the view they are being created in, so they appear in that view after creation.
For example:
If a user opens a form from a view filtered to show only Type = Bug, then Fibery pre-fills "Bug" in the Type field.
If another user opens the same form from a view without filters (or with Type = Task filter), the form pre-fills "Task."
This behavior is intentional and applies to all views.
To avoid filters affecting the default values, you can use the global "New" button in the sidebar — it always opens the form without any context filters applied.
How required fields work in Forms?
Fibery automatically adds all Required fields to form on new Form Creation. It is not possible to remove required fields from Form View. If there are some public Forms for a database, Fibery shows a warning when marking fields as required, listing affected public forms.
What if I found phishing Fibery form?
If you believe this is actually a malicious site impersonating Fibery, you should:
Report to Fibery directly - contact Fibery support at support@fibery.io or via intercom chat.
Why doesn’t my public Form View work if the database is in another (non-shared) space?
Public Form Views only work if the Form’s database is part of the same space that’s shared publicly.
This is a deliberate limitation designed to prevent accidental data exposure. If the database is not in the shared space, submissions to that form are blocked — otherwise, it could allow anyone to add entities to an unshared database.
Example:
✅ Works: The form and its database are both in a public (shared) space.
❌ Doesn’t work: The form is in a shared space, but its database is private or in another space.
Why this works this way:
If the database were in a public space, all existing entities in it would become publicly visible. To avoid that, Fibery currently requires both the form and the database to be within the same shared space.
