Overview
If you have multiple webforms (such as a Brochure Request form and a Refer a Child form), you can use a hidden, view-only field to identify which form was submitted. This allows you to create separate notification workflows for each form — for example, alerting your BD team differently depending on whether a brochure was requested or a referral was submitted.
Before You Begin
You must have administrator access to your Dazos CRM instance.
Your webforms must already be created and active.
You should have permissions to create and edit fields and workflows in the CRM.
Steps
Create a new hidden, view-only field
In your CRM field settings, create a new picklist field (e.g., named Source Form). Set this field as hidden and view-only so it does not appear to the end user filling out the form.Add picklist values for each webform
Add one picklist value for each webform you want to differentiate. For example:Brochure — for your Brochure Request form
Referral — for your Refer a Child form
Set a static override value in each webform's configuration
Open each webform's configuration settings in the CRM. For the Source Form field, set a static (override) value that corresponds to that specific form. For example:Brochure Request webform → set Source Form = Brochure
Refer a Child webform → set Source Form = Referral
This ensures that every time a form is submitted, the Source Form field is automatically populated with the correct value — no changes to the website embed code are required.
Verify the field populates correctly
Submit a test entry on each form. Open the resulting CRM record and confirm that the Source Form field displays the correct value for each form.Create separate workflows for each form
Navigate to your workflow settings and build a separate workflow for each form. Set the trigger condition to match the Source Form field value. For example:Workflow 1: Trigger when Source Form = Brochure → Send notification to BD team about a brochure request
Workflow 2: Trigger when Source Form = Referral → Send notification to BD team about a referral
Verification / Expected Result
After completing setup, each form submission will automatically populate the Source Form hidden field with the correct form-specific value. Your separate workflows will trigger independently based on that value, sending the appropriate notification for each form type.
Brochure Request submissions → Source Form = Brochure → Brochure notification workflow fires
Refer a Child submissions → Source Form = Referral → Referral notification workflow fires
Troubleshooting / Common Errors
Source Form field is not populating after submission:
Confirm that the static override value is saved correctly in each webform's configuration. Re-open the webform settings and verify the field value is set.
Workflow is not triggering:
Check that the workflow condition exactly matches the picklist value (spelling and capitalization must match). Confirm the workflow is set to Active.
Both workflows are firing for the same submission:
Review each workflow's trigger conditions to ensure only one value is specified per workflow and that the conditions are not overlapping.
Tips & Notes
⚠️ No code changes needed: The static override value is set entirely within the CRM webform configuration. You do not need to modify the HTML embed code on your website.
💡 Tip: You can use this same approach for any number of webforms — simply add a new picklist value and configure the override in each additional webform's settings.
✅ Best Practice: Use clear, descriptive picklist values (e.g., Brochure, Referral) that make your workflow conditions easy to read and maintain.