Form-Triggered Automations

Build automations that fire when someone submits one of your forms, with rules that look at the actual values they entered. The most common use: tag a lead based on a referral code field, or any other field on your intake form.

Perfect for: referral programs, marketing attribution, lead segmentation, and any "if someone fills in X, do Y" workflow.

How It Works

1. Build an automation in Automations → New Automation
2. Pick When a form is submitted as the trigger
3. Choose which form template the automation watches
4. Add steps that run when matching submissions come in. Each step can optionally include "run if field X equals Y" conditions, so the same form can fire different actions depending on what was entered.
5. As leads come in, the automation runs in the background — no manual work.

Setting Up a Form-Triggered Automation

Step 1: Build the Trigger

Open Automations → New Automation and give it a name like "Referral code tagging" or "Hawaii inquiry routing."

In the step editor, set the trigger to When a form is submitted and pick the form template you want to watch (your intake form, your referral form, etc.). All steps in this automation will run against submissions to that form.

One automation = one form. If you want to react to submissions on a different form, create a separate automation.

Step 2: Add the Action

The first action available for form-triggered automations is Add Tag. Pick one or more tags that should be applied to the lead when the step runs. New tags can be created right from the picker.

More actions (send an email, assign to an agent, add to a campaign) are on the roadmap.

Step 3: Optional — Add Field Conditions

Want the step to only run for some submissions? Add Field Conditions to the step. Each condition is shaped like:

• Field: which form field to check (e.g., "Referral Code", "Destination")
• Operator: equals, contains, or is not empty
• Value: what to compare against (leave blank for is not empty)

If you add multiple conditions to a step, all of them must match for the step to run.

Common Patterns

Tag by referral code

One step per code:

Step	Condition	Tag
1	referral_code equals FRIEND10	Friend Referral
2	referral_code equals PODCAST	Podcast Lead
3	referral_code equals INSTAGRAM	Social Lead

Whichever code the submitter enters, only that step's tag is applied.

Tag everyone who provides a referral code

One step:

Condition	Tag
referral_code is not empty	Has Referral

Tag by destination interest

One step per destination:

Condition	Tag
destination contains Hawaii	Hawaii Interested
destination contains cruise	Cruise Interested

How Matching Works

• Case-insensitive: FRIEND10, friend10, and Friend10 all match the same value.
• Whitespace-tolerant: leading and trailing spaces in either the user's entry or your configured value are trimmed before comparison. Pasted codes with extra spaces still match.
• AND across conditions: if a step has multiple conditions, all must match.
• Independent across steps: each step in the same automation is evaluated separately.

When Tags Are Applied

Tags are applied via the same queue the rest of the JourneyFuse automation system uses. They normally show up on the lead within a few minutes of submission. If you don't see a tag right away, give it five minutes before troubleshooting.

Limitations (Today)

• The only action is Add Tag. Send email, assign agent, and add to campaign are tracked for a future release.
• A form-triggered automation targets one form. If you change the form on an existing automation, future submissions of the new form fire it; past submissions of the old form aren't replayed.
• Re-submission of the same form by the same lead doesn't re-fire the steps. The automation runs once per (lead, step) pairing.

Troubleshooting

A submission came in but no tag was applied

1. Confirm the automation is Active (toggle on the Automations list page).
2. Confirm the form template attached to the automation matches the form the submitter used.
3. Open the step and verify the field condition matches what the submitter actually entered. Field keys (the field_key in the condition) come from the form schema — if you renamed a field, condition keys don't auto-update.
4. Wait five minutes — the queue processes on a short cron schedule, not instantly.

The tag is being applied twice

It shouldn't — re-submissions skip enrollment for leads already enrolled in that step. If you're seeing duplicates, check whether you have two automations targeting the same form with overlapping conditions.