A practical guide to adding and configuring the Form block to capture leads, registrations, and responses directly from your UniLink page.
- The Form block lets you build custom forms — lead capture, event registration, client intake, waitlists, and more — directly on your UniLink page.
- Add it from the block picker, then configure fields, set up notifications, and optionally connect a webhook for external integrations.
- The most important setting is your notification email — without it, you won't know when submissions come in.
- Common gotcha: adding too many fields. Every extra field you add reduces form completion rates; start with the minimum you actually need.
What the Form block does
The Form block is a customizable data collection form you embed directly on your UniLink page. You build the form by adding fields — text inputs, email, phone, dropdowns, checkboxes, file uploads, and more — and configuring how responses are handled. Submissions are stored in UniLink's built-in CRM, where you can view, filter, and export them. You can also set up email notifications so you're alerted immediately when someone submits the form.
Beyond basic field collection, the Form block supports conditional logic: you can show or hide specific fields based on a visitor's previous answers. This is useful for multi-purpose forms where different visitor types need different questions — for example, showing a "business name" field only when someone selects "Business" from a type dropdown. Conditional logic keeps the form lean for most visitors while still capturing the right data from each segment.
For teams or workflows that use external tools, the Form block supports webhook delivery — when a form is submitted, UniLink sends the submission data as a POST request to any URL you specify. This makes it straightforward to route form data into Zapier, Make, an email marketing platform, a CRM like HubSpot, or a custom backend endpoint without any native integration required. Combined with the spam protection that's built into every form, the Form block covers the full range of data collection needs from simple lead capture to complex multi-step intake flows.
How to add the Form block
- Open the page editor: In your UniLink Dashboard, navigate to the page you want to edit and open the editor.
- Add the Form block: Click the "+" button to open the block picker. Search for or scroll to "Form" and click to add it to your page.
- Set the form title: Give the form a clear, specific title that tells visitors exactly what they're signing up for or submitting — "Join the Waitlist," "Register for the Workshop," or "Request a Quote."
- Add fields: In the block settings panel, click "Add field." For each field, choose the field type (text, email, phone, dropdown, checkbox, file upload), write the label, and mark it required or optional as appropriate.
- Configure the submit button: Change the default button text to something specific to the action — "Join Waitlist," "Submit Registration," or "Send My Request."
- Set up notifications: Enter the email address where you want to receive submission alerts. This step is often skipped and then forgotten — don't skip it.
- Add a confirmation message: Write the message visitors see after a successful submission. Confirm their action ("You're on the waitlist!") and set expectations ("We'll email you within 24 hours").
- Connect a webhook (optional): If you want submissions routed to an external tool, enter your webhook URL in the integration settings. Test it with a dummy submission before publishing.
- Publish the page: Save and publish. Your form is now live.
Key settings to configure
| Setting | What it does | Recommended value |
|---|---|---|
| Form title | The heading shown above the form fields | Specific to the action: "Register for the April Workshop" beats "Contact Form" |
| Field types | Determines what kind of input each field accepts | Use the most specific type available — "email" field instead of "text" for email addresses, so built-in validation kicks in |
| Required vs. optional fields | Controls which fields must be filled before the form can be submitted | Mark only the fields you truly can't function without as required; every required field reduces completion rates |
| Submit button label | The CTA text on the submission button | Action-specific verb: "Join Waitlist," "Send Request," "Register Now" |
| Notification email | Where submission alerts are sent | Your primary working email — or a dedicated inbox if you expect high volume |
| Confirmation message | What the visitor sees after successful submission | Confirm the action and set next-step expectations: "You're registered! Check your email for confirmation." |
| Webhook URL | Sends submission data to an external endpoint in real time | Use for routing to external CRMs, email tools, or automation platforms; test before going live |
| Spam protection | Built-in filter that blocks automated bot submissions | Leave enabled — no reason to disable it |
Best practices for the Form block
Keep your forms short. Every additional field you add reduces the percentage of visitors who complete it. Research consistently shows that form completion rates drop significantly with each extra question. The right approach is to ask only for what you absolutely need at this stage of the relationship. For a waitlist, that's usually just a name and email. For an event registration, you might add phone number and a dietary restriction field. For a client intake form, you'll need more — but even then, ask yourself whether you could collect the less critical details in a follow-up email after they've already expressed interest.
Match your form's field count and complexity to the visitor's level of intent. A visitor arriving at your page cold has low commitment — a 10-field form will drive them away. A visitor who has already watched your video, read your page, and clicked a "Apply to Work With Me" button is self-selected and motivated — they'll fill in more. Think about where on the page the form appears and what the visitor has experienced before reaching it. Forms that appear after a clear value proposition or a compelling piece of content outperform forms dropped at the top of a cold page.
Use the confirmation message to do real work. Most people write something generic like "Thank you for your submission" and move on. A well-written confirmation message can reduce support inquiries, set accurate expectations, and build trust — all at zero cost. Tell them what happens next and when. If they'll get an email, say so. If there's a review process, name the timeline. If they're on a waitlist, tell them how long it typically is. Visitors who know what to expect are less likely to submit twice, email you asking "did you get it," or disengage while waiting.
Review your CRM submissions regularly. UniLink stores every form submission in the CRM with a timestamp, so even if your notification email setup breaks or gets buried, your data is safe. Make a habit of checking the CRM view for your form at least weekly. If you have a high-traffic page, check it more often. You can export submissions as a CSV if you need to load them into a spreadsheet or another tool. The CRM is also where you can add notes to individual submissions — useful for flagging leads you've followed up with.
Common mistakes and how to fix them
| Mistake | Why it happens | Fix |
|---|---|---|
| No notification email set | The setting is easy to skip during setup | Go to form settings → Notifications, enter your email, and send a test submission to confirm it's working |
| Too many required fields | Wanting to collect as much data as possible upfront | Audit each field: if you don't use it in your immediate follow-up, make it optional or remove it entirely |
| Generic submit button text ("Submit") | Leaving the default label unchanged | Change to an action-specific label that matches the form's purpose: "Join Waitlist," "Register," "Send Request" |
| No confirmation message or a generic one | Overlooked during setup | Write a confirmation that confirms the action and states what happens next; set realistic timing expectations |
| Webhook not triggering | Incorrect URL format or endpoint not expecting POST requests | Test the webhook URL with a tool like webhook.site before connecting it; confirm the endpoint accepts POST with JSON body |
| Spam submissions filling the CRM | Spam protection disabled or a known bypass | Verify spam protection is enabled in form settings; if spam persists, add a required checkbox field ("I am a human") as a secondary filter |
When to use the Form block
- You need to collect structured data from visitors: event registrations, waitlist signups, contest entries, client intake details
- You want submissions stored automatically in UniLink's CRM without a separate tool
- You need to route submission data to an external platform via webhook
- You want a form that matches your page's visual style without linking out to a third-party form tool
- You need conditional logic to show different fields to different visitor segments
When to use something else
- You just need a simple contact email link — use an Email link block instead of a full form
- You need a long, multi-page survey with scoring or branching logic — a dedicated tool like Typeform or Tally may handle complex logic better
- You're collecting payments alongside form data — use a Product or Membership block, which has native payment flow built in
- You need real-time chat or live support — a chat widget is a better fit than a form for that use case
Frequently asked questions
Where do form submissions go after someone submits?
All submissions are stored in UniLink's CRM, accessible from your Dashboard under the Forms or CRM section. You'll also receive an email notification for each submission if you've configured a notification email. You can view, filter, and export submissions from the CRM at any time.
Can I accept file uploads through the Form block?
Yes. The Form block supports a file upload field type. You can specify which file types are accepted (e.g., PDF, JPG, PNG) and set a maximum file size limit. Uploaded files are stored securely and linked to the submission in the CRM.
How do I send form submissions to my email marketing tool?
Use the webhook setting. In the form's integration settings, enter your email tool's webhook or automation trigger URL. For tools like Mailchimp, ActiveCampaign, or ConvertKit, you can create a Zapier or Make automation that listens for the UniLink webhook and adds the contact to your list. Test with a real submission before going live to confirm the data is mapping correctly.
Can I have more than one Form block on the same page?
Yes, you can add multiple Form blocks to a single page. This is useful if you have distinct capture goals in different sections — for example, a waitlist form at the top and a detailed inquiry form further down. Each form block has its own settings, fields, and CRM submission log, so submissions are tracked separately.
- Set up your notification email immediately after creating the form — it's the most commonly skipped setting and the most immediately painful when missed.
- Fewer fields convert better; ask only for what you need right now, and collect additional details in follow-up.
- Write a specific confirmation message that names the next step — generic "thank you" messages leave visitors uncertain and generate unnecessary follow-up emails.
- Use webhooks to route submissions into external tools like Mailchimp, HubSpot, or Zapier without leaving UniLink.
- All submissions are backed up in the UniLink CRM, even if your email notifications break — check it regularly as a safety net.
Ready to get started? Create your free UniLink page and add your first Form block today.