Form Submission Trigger¶
Overview¶
The Form Submission trigger captures data when visitors submit forms on your website. This creates a seamless connection between your website and your automation workflows, enabling instant follow-ups, lead nurturing, and data processing.
When to use this trigger:
- Capture contact form submissions
- Process lead generation forms
- Handle registration forms
- Manage support ticket submissions
- Collect survey responses
- Process quote requests

Quick Start¶
Builder fields¶
The Field column is the label as it appears in the task builder; Key is the name the value is stored under and referenced by.
| Field | Key | Type | Default | Notes |
|---|---|---|---|---|
| How should this form be shared? | output_mode |
select | javascript |
Options: JavaScript Embed · Public URL |
| Header text | header_text |
text | Book Online Now |
|
| Form theme color | base_color |
text | #0066cc |
|
| Success message | success_message |
text | – | |
| Form Fields | _form_fields |
website-form-fields | – | |
| Keep unfinished forms | keep_partial |
checkbox | – | |
| Keep them once this field is filled in | partial_after_field |
text | – | Only shown when keep_partial is 1 |
- Create a workflow and add a Website Form trigger
- Build the form — its fields, branding, and the link or embed code to put it on your site — in the classic BaseCloud portal, as the trigger's panel says
- Put the form on your website
- Add the tasks to run for each submission, and switch the workflow on
- Submit the form once yourself and check the run's output
Each submission starts the workflow once, with the submitted fields as its outputs.
In the form editor, each text box saves when you click away from it, and flashes green once it is saved.
Outputs¶
| Field | Type | Example | Notes |
|---|---|---|---|
task_name |
string | Website contact form |
The name of the trigger task that fired. Always present — useful when several forms share a workflow. |
run |
boolean | true |
|
run_text |
string | Inbound data received and processed successfully. |
|
form_status |
string | Complete |
Complete when the visitor sent the form, Partial when they left it unfinished. See Keep Unfinished Forms. |
last_page_reached |
string | Contact Info |
The step the visitor was on, for a form in steps. Empty otherwise. |
submission_id |
string | b76bb8f4-… |
The visit, on a form that keeps unfinished forms. A Partial and a Complete from one visit carry the same id. |
partial_already_run |
string | No |
On a form that keeps unfinished forms: Yes when this visit's unfinished copy already ran the workflow (the visitor came back after the 15 minutes). See Keep Unfinished Forms. |
Every other field is whatever the form posted, spread across the top level of the output. A form
posting name, email and message produces {{task_<ID>_name}}, {{task_<ID>_email}} and
{{task_<ID>_message}}.
The rest of the output is the incoming payload
This trigger spreads the payload it received across the top level of its output, so the remaining field names come from the source, not from BaseCloud. Run the workflow once and read the task's OUTPUT panel to see exactly what arrived.
Field Types¶
Each field on the form has a Field type, chosen in the trigger's Form Fields list.
| Field type | What the visitor sees | What your workflow receives |
|---|---|---|
| Text | One line of text | The text |
| One line for an email address | The address. See Email Fields | |
| Phone number | A country next to a box for the number | The number in full, like +14155552671. See Phone Number Fields |
| Date | A date picker, or a month calendar with only your open days (Show a calendar) | The date, like 2026-11-09. See Calendar |
| Long text | A larger box for longer text | The text |
| Checkbox | A tick box | Yes or No |
| Choose one | A list to search and pick one option from, or large buttons (Show as: Cards) | The option. See Cards |
| Choose several | A list to search and pick several options from | The options, separated by commas |
| Text block (no answer) | Your own text or HTML, with nothing to fill in | Nothing |
| Address | An address box that suggests real addresses as they type | The address, plus its street, city, state, ZIP, country and coordinates. See Location Fields |
| Page break (added with + → Add page break) | Nothing: it starts a new step, named by its label | Nothing. See Forms in Steps |
Required Fields¶
Tick Required on a field and the form will not send until the visitor fills it in. BaseCloud also checks every submission when it arrives, so a submission that skips the form, such as a bot sending straight to the form's address, cannot get around it.
The workflow does not start, and nothing is recorded, when a submission:
- leaves a required field empty, or sends only spaces
- leaves a required tick box unticked
- sends something that field could not hold, such as an incomplete email address, a date that does not exist, or an option that is not on the list
The visitor sees what to fix, for example First Name is required.
A required field that is hidden because of its show-if rule is not needed. It is only needed when it is showing.
A phone number that cannot be read is still accepted, because a lead with a mistyped number is still a lead. A required phone field left empty is not accepted.
Dropdown Fields¶
Choose one and Choose several fields can be searched. The visitor clicks the field and types a few letters, and the
list shows only the options that contain them. Typing new in a list of US states shows New Hampshire, New Jersey,
New Mexico and New York. They can also use the arrow keys and Enter to choose.
- Choose one shows the chosen option in the box. To clear it, the visitor deletes the text.
- Choose several shows each chosen option as a tag. Choosing an option again, or clicking the × on its tag, removes it.
Enter the options one per line under Options. A list can hold up to about 4,000 characters, which is room for every country in the world. If a list is longer than that, the field tells you and does not save it.
Email Fields¶
Use the Email field type for an email address, instead of a Text field. A Text field accepts anything, so a
visitor can send sam@gmail, sam.gmail.com or their phone number by mistake. An Email field only accepts a
complete address: a name, an @, and a domain with its ending, like name@example.com.
If the address is not complete, the visitor sees a message on the field and the form is not sent until they fix
it. Spaces before and after the address are removed. Your workflow receives the address as
{{task_<ID>_form_field_<N>_value}}, the same as a Text field, so nothing else in the workflow changes.
What the check cannot tell
The form checks that the address is written properly, not that the mailbox exists. sam@gmial.com is a
properly written address, so it is accepted. If reaching the person matters, ask for a phone number too.
Phone Number Fields¶
Use the Phone number field type for any phone or cellphone number, instead of a Text field. A Text field accepts anything: words, a number with a digit missing, a number with no country code. A Phone number field only accepts a real phone number.
What the visitor sees: a country next to the box for their number. The country is already set to where they are,
and they can change it. They type the number the way they normally would, such as (415) 555-2671 or
082 123 4567, with or without spaces and brackets. A visitor who types the number with its country code, such as
+44 20 7946 0958, has the country set for them.
What the form checks: that the number is a real one for that country, with the right number of digits. If it is not, the visitor sees a message under the field and the form is not sent until they fix it. Cellphone and landline numbers are both accepted.
What your workflow receives:
| Field | Example | Notes |
|---|---|---|
{{task_<ID>_form_field_<N>_value}} |
+14155552671 |
The number in full: +, the country code, then the number, with no spaces. Ready for SMS, WhatsApp, calls and Match to Client. |
{{task_<ID>_form_field_<N>_country}} |
US |
The two-letter code of the country the number belongs to. Empty when the field was left empty. |
Because the number already arrives in full, you do not need a Phone Formatter after the form.
Country the field starts on: by default this is the visitor's own country, worked out from their internet address. If nearly all your enquiries come from one country, choose that country under the field's settings and every visitor starts there. They can still pick another.
Only this country: once you have chosen a country, you can also tick Only this country (hide the country list). The country list then disappears and visitors just type their number, which is checked as a number for that country. Use it when you only serve one country, such as a US business whose customers all have US numbers. The tick box goes away if you set the field back to the visitor's own country, because there would be no one country to check against.
Changing an existing form
Open the trigger, find your phone field in Form Fields, and change its Field type from Text to Phone number. The field keeps its name, so the rest of your workflow carries on working, and you can remove the Phone Formatter that came after it. Do the same for your email field, choosing Email.
A form sent without the embed script
The check happens in the form BaseCloud gives you (the JavaScript embed or the Public URL). If your own website code posts straight to the form's address instead, a number sent with its country code is still tidied into the full format, and anything else is passed on as it was sent.
Preview Your Form¶
Click Preview at the bottom of the trigger's settings (it stays in view as you scroll) to open the form in a small window, exactly as a visitor sees it: steps, show-if rules, address suggestions and every check work as they will on your website. It is your live form: what you send from the preview is a real submission and runs your workflow, so it doubles as a test of the whole thing. After changing the form, click Preview again: the same window reloads with your changes.
Forms in Steps¶
A long form is easier to finish one step at a time. In the trigger's field list, hover over the + under any field (the last one too) or above the first field, and it opens into Add field and Add page break: click Add page break to start a new step right there, then type the step's name, such as Contact Info. Add field adds a field in that spot the same way. A page break at the very top names the first step.
The form then shows:
- a progress bar with the name of every step
- one step at a time, with its name as a heading
- Next on every step but the last, Back on every step but the first, and Submit on the last
Next only moves on when the fields on that step are filled in properly. A step whose fields are all hidden by their show-if rules is skipped. A form without page breaks looks and works exactly as it always has.
Once the visitor sends it, the steps make way for your Success message with a tick, and a Send another button that starts the form over. Leave the message as something the visitor needs to hear, such as Thanks! We'll call you shortly to confirm your appointment.
Show fields as the visitor goes¶
Use the show-if rule Is filled in to reveal a field once the one before it has an answer. For example, set Address to show when Phone number is filled in, and First Name, Last Name and Email to show when Address is filled in. The visitor sees one question, answers it, and the next appears.
When you tick Only show this field when…, the rule starts as Is filled in on the field directly above it, so building a chain like this takes no choosing. Change either if you need something else: Show when offers the fields above this one, and the rules are Is filled in, Equals, Does not equal, Is one of, Is not one of, Includes all of, Is ticked and Is not ticked. For the rules that compare, type the value, or several separated by commas.
On an optional field, Is filled in means answered or skipped: the next field appears once the visitor fills it in, leaves it empty and moves on, or presses Next or Submit. So a required field after an optional one is still asked for. For example, with Email (required) waiting on Surname (optional), a visitor who skips Surname still sees Email and cannot send the form without it.
An email counts as filled in once it is a whole address, a phone number once it is a real number, and an address that must be chosen from the suggestions once one is chosen. While the visitor is typing, the next field waits until they pause or leave the box, then opens smoothly rather than popping in.
Cards¶
Set a Choose one field to Show as: Cards and each option becomes a large button, which is easier to tap on a phone. When the cards are the only question on their step, picking one moves the visitor straight to the next step.
Calendar¶
Tick Show a calendar on a Date field to show a month calendar instead of a date box. Choose the days of the week you are open, the earliest day (how many days from today) and the latest day. Only those days can be picked, and BaseCloud turns away a submission with a day of the week you are not open.
The day is a request, not a booking: tell the visitor you will confirm the time, and confirm it in your workflow.
Location Fields¶
An Address field suggests real addresses from Google as the visitor types, like the address box on a delivery site. Choose:
- Only suggest places in: the countries to search, such as United States
- Prefer places near: your area, so nearby addresses come first
- Visitor must choose a suggested address: the visitor has to pick one from the list, so every address is a real one. If the suggestions cannot load, the visitor can still type the address.
When the visitor picks a suggestion, your workflow receives the address and also its parts, for example
{{task_<ID>_form_field_5_city}} and {{task_<ID>_form_field_5_zip}}: street, city, state, zip, country, lat and
lng. Use the ZIP code to send the lead to the right team.
Only take addresses in your service area¶
Tick Only take addresses in your service area on an Address field to turn away bookings from places you don't serve. Set the area in either way, or both:
- Within a distance of: search for your town or address, then set how far you go, in miles or km
- Or with one of these ZIP codes: list them, separated by commas.
760*takes every ZIP code that starts with - Postal codes from other countries work too.
An address is in your area when it's within the distance or its ZIP code is on the list.
When a visitor picks an address outside the area, the box turns red with your Message for addresses outside it under it (for example Sorry, we don't serve that area yet. Call us on (469) 200-0982.), the fields after it stay hidden, and Next and Submit stay off until they choose an address inside it. BaseCloud checks the address again when the form arrives, so it can't be sent another way, and with Keep unfinished forms on, an unfinished form from outside the area isn't kept.
The visitor has to choose a suggested address, so it can be checked. If the suggestions can't load, or Google can't find the address and the visitor types it in full, the form lets it through, because there is nothing to check it against.
Keep Unfinished Forms¶
Many visitors start a form and leave before they send it. Turn on Keep unfinished forms in the trigger's Unfinished Forms section, and choose the field that makes an unfinished form worth keeping, usually the phone number.
Once the visitor has filled in that field, the form submits itself if they leave without pressing Submit: they
close the form, leave the page or switch to another app, and 15 minutes later the workflow runs with whatever they
filled in and Form Status Partial. If they come back and submit the form within those 15 minutes, only their
finished form is sent, with Form Status Complete.
If they come back after the 15 minutes and finish the form, the workflow runs twice: first as Partial, then as
Complete. The Complete run then has Partial Already Run {{task_<ID>_partial_already_run}} = Yes, so you
can skip what the first run already did, like a second welcome text, with an If.
It is off unless you turn it on. With it off, nothing is sent until the visitor presses Submit.
An unfinished form with an address outside your service area is never kept, and neither is one held earlier in the same visit.
Add an If on {{task_<ID>_form_status}} to treat unfinished forms differently, for
example a call from the team instead of the booking confirmation.
Call, do not text, a partial lead without SMS consent
A visitor who left before ticking your SMS consent box has not agreed to text messages. Give an unfinished form without that tick a phone call, never automated texts. Your privacy policy should also say that details typed into a form may be kept even if it is not sent.
Match the Form to Your Website¶
The form arrives with a plain look in your Form theme color. Your website's own stylesheet can change all of it, whether the form sits on the page or opens as a pop-up.
Colour, corners and font. Set these on .bcf-inline-wrapper, and the header, buttons and field borders follow:
.bcf-inline-wrapper {
--bcf-accent: #ff6000; /* buttons, header, the border of the field being filled in */
--bcf-accent-hover: #e05500; /* the button under the mouse */
--bcf-accent-dark: #c94c00; /* the far end of the header's colour fade */
--bcf-radius: 8px; /* the corners of fields and buttons */
--bcf-font: inherit; /* your website's font */
}
Anything else. Every part of the form has its own class, such as bcf-inline-input, bcf-inline-label,
bcf-inline-submit and bcf-inline-header. Give your rule two classes for a form on the page, and three for the
pop-up:
.my-site .bcf-inline-input { padding: 8px 12px; } /* on the page */
.bcf-modal .bcf-inline-wrapper .bcf-inline-input { padding: 8px 12px; } /* in the pop-up */
Your website's general rules for inputs and buttons do not reach the pop-up, so a pop-up you have not styled keeps the form's own look.
When the form is sent. The form tells the page with a bcf-submitted event, so your website can react, for
example by closing its own pop-up. The thank-you of a form in steps is bcf-inline-thanks, with bcf-inline-thanks-text
and bcf-inline-thanks-again (the Send another button) inside it.
document.addEventListener('bcf-submitted', (event) => {
console.log('Form sent:', event.detail.token);
});
What BaseCloud Adds to a Submission¶
Besides the form's own fields, a submission carries:
| Fields | What they hold | Notes |
|---|---|---|
referrer, utm_source, utm_medium, utm_campaign, utm_term, gclid, gbraid, wbraid, fbclid |
Where the visitor first came from: the website that sent them, and the campaign and ad click details from the link they followed. | Remembered in the visitor's browser for 30 days (7 days in Safari and iPhone browsers), so they are still there when the visitor submits on a later visit. Empty when there was none. |
| Any other value in the page address | A form opened at …?source=email&ref=partner123 also sends source and ref. |
Taken from the page the form was submitted on. |
ip_address, country, country_code, city, region, timezone, latitude, longitude |
Roughly where the visitor is, worked out from their internet address. | Left out when the location cannot be worked out. |
journey and the other journey_… fields |
The pages the visitor viewed before submitting. | See Visitor Journey. |
There is no submission time or form id
A submission has no form_id, user_agent or submitted_at unless your form sends a field with that
name. If you need the submission time, use a Date Formatter, or add the
value to the form itself.
Visitor Journey¶
A form placed on your own website with the JavaScript embed also sends the pages the visitor viewed before submitting, including earlier visits in the last 30 days. If someone visited three days ago, came back today and only then submitted, both visits are there, page by page.
| Field | Type | Example | Notes |
|---|---|---|---|
journey |
list | see below | One entry per page, oldest first. Use {{task_<ID>.JSON.journey}} for the whole list, or {{task_<ID>_journey_0_url}} for one value. |
journey_summary |
string | Visit 1 - 2026-10-06 (from https://www.google.com/) … |
The same journey as readable text, one line per page (times in UTC) — for a workflow note or an email. To choose the columns, the order or your own timezone, use a List Formatter on journey. |
journey_visits |
number | 2 |
How many separate visits. A pause of more than 30 minutes starts a new visit. |
journey_pages |
number | 7 |
How many pages were viewed. |
journey_first_visit |
string | 2026-10-06T14:02:11.000Z |
When the first recorded page was viewed (UTC). |
journey_landing_page |
string | https://example.com/pricing |
The first recorded page. |
Each entry in journey holds type (page, or form_submitted for an earlier submission on the same website),
url, title, time (UTC), visit (1, 2, 3 …) and, on the first page of a visit that came from another website,
referrer.
Show the journey in a workflow note¶
Two ways, depending on how much say you want over the layout:
- Quick: place
{{task_<ID>_journey_summary}}in the note. One line per page, grouped by visit. - Your own layout: add a List Formatter, set its List to
{{task_<ID>.JSON.journey}}, choose the columns (for example Page →url, Date →time), and place itsoutputin the note. Dates are shown in your account's timezone.
Form Submission
└─ List Formatter List: {{task_55001.JSON.journey}} Columns: Page → url, Date → time
└─ Workflow Note "Pages viewed before submitting: {{task_72001_output}}"
Put the script on every page
Only pages that load the form script are recorded. Add the script to every page of the website — without
data-auto-open="true" on pages where the form should not pop up by itself. Several forms on one website share
one journey, and a page with more than one form is still recorded once.
What the journey cannot see
- It is kept in the visitor's browser, so a visit on a phone and a submission on a laptop are two journeys, and a private window or cleared browsing data starts a new one.
- Safari and iPhone browsers forget it after 7 days without a visit; other browsers keep it for 30 days.
- It covers one website address:
www.example.comandshop.example.comkeep separate journeys. - It holds the latest 100 pages.
- A form opened from its Public URL has no journey.
- It is visitor tracking. If the website asks visitors for cookie consent, include it there.
Real-World Examples¶
Capture an enquiry into the CRM¶
Create the client when nobody matches¶
Form Submission
└─ Match to Client contact_email from the form
└─ If Statement run is false
└─ New Client create the record
Confirm to the person who submitted¶
Assign the enquiry fairly¶
Field names come from your form
Everything except task_name is whatever the form posted. Run it once and read the OUTPUT
panel to see the exact names.
Best Practices¶
- Match the person first — Match to Client on the submitted email — so a returning enquirer is not created twice.
- Tick Required on every field the workflow needs, such as the names on a sign-up form. A submission without them never starts the workflow. See Required Fields.
- Use the Phone number field type for phone numbers, so every number arrives real and in full. See Phone Number Fields.
- Use the Email field type for email addresses, so an incomplete address is caught while the visitor is still on the form. See Email Fields.
- Test with a real submission and read the run's output to see each field's name as it arrives.
Troubleshooting¶
Submissions not starting the workflow¶
- Check the workflow is switched on
- Check the form on your site is the one built for this trigger
- Submit it yourself and look for the run in the workflow's Records
- Check every required field was filled in. A submission with a required field empty is turned away and does not show in Records. See Required Fields
A field is missing from the output¶
The output holds what the form submitted, under the field's name — check the field exists on the form and was filled in.
Frequently Asked Questions¶
Can I have several forms?¶
Yes — give each its own Website Form trigger (and workflow), or one workflow that branches on a field.
Do I still need a Phone Formatter after the form?¶
Not for a Phone number field. It already gives your workflow the number in full, like +14155552671. You only
need a Phone Formatter for a number collected in a Text field.
Can a visitor from another country fill in their number?¶
Yes. The country starts on where the visitor is, and they can choose any country from the list.
Can I prevent spam submissions?¶
Tick Required on the fields that matter. BaseCloud turns away any submission that leaves one empty, even one sent without the form. Use the Email field type too, so a submission needs a complete email address. For anything further, check the submission with an If before acting on it.
Next Steps:
- Inbound Email - Trigger workflows from incoming emails
- Webhook In Trigger - Trigger workflows from external systems
- Match to Client Task - Find/update contact records