Form Finished Trigger Block

What’s in This Article

• What this trigger does

• When to use this trigger

• When not to use this trigger

• Block settings explained 

• Common use cases

• What data this block uses

• Important things to know

• Example automations

• Best practices

 

---

 

What This Trigger Does

The Form Finished trigger fires when:

1. A contact submits a Patch form

2. Patch records the submission

3. Patch sends the form event + contact information into the automation

In simple terms:
“Run this automation when someone completes a form.”

 

---

 

When to Use This Trigger

Use Form Finished when you want to:

• Send an instant confirmation (ex: “Got it — we’ll follow up soon”)

• Route leads to the right team (parties, group sales, rentals, memberships)

• Tag contacts based on form intent (ex: “Lead – Party Inquiry”)

• Deliver a lead magnet or download link

• Start a drip campaign tied to a specific request

---

 

When Not to Use This Trigger

Don’t use this trigger when you need a workflow based on behavior or transactions:

• Order Finished → revenue + product data

• Check-In Finished → visits/check-ins

• Calendar Event → scheduled reminders

• Membership Started/Ended → membership lifecycle

• SmartLink Clicked → intent from link clicks

 

---

 

Block Settings Explained

Details (Info Panel)

This area explains how the trigger works. It does not change behavior—your settings below do.

---

Add Conditions

Use Add Conditions to control which submissions can trigger this automation.

Common condition ideas:

• Form = “Party Request” (recommended)

• Time (only run during business hours)

• Contact fields like Tags, Location, or Lead Source

Tip

If you have more than one form, always filter by Form so the right follow-up runs.

---

Configure Trigger Frequency

This section controls how often the automation can trigger for the same contact over time.

Run this trigger…

• Every X completions
  Runs the automation every time the contact completes a form (or every Nth time).

Number of completions

Set how many form completions must happen before the trigger runs.

• Example: 1 = run on every submission

• Example: 3 = run on every 3rd submission

Starting with completion

Controls when the counting begins.

• Example: Starting with 1 means the first submission counts immediately.

• Example: Starting with 2 skips the first submission and starts triggering after that point.

 

---

 

Common Use Cases

• Lead follow-up for parties, group events, and rentals

• “Thanks for reaching out” confirmation messages

• Add tags like “Lead – Party Inquiry”

• Internal alerts to staff (email or Slack via integration)

• Post-form drip campaigns (Day 0 / Day 1 / Day 3)

 

---

 

What Data This Trigger Has Access To

This trigger includes:

• Contact data (standard + custom contact fields)

• Form context (which form was completed)

This is typically enough to route, tag, and personalize follow-ups without needing purchase or visit data.

 

---

 

Important Things to Know

• If a contact submits the same form multiple times, use trigger frequency controls (if enabled) or conditions/tags to prevent duplicates.

• For SMS follow-ups, make sure the contact is eligible to receive texts based on your account rules and consent settings.

 

---

 

Example Automations

Example 1: Party Inquiry → Fast Follow-Up

1. Trigger: Form Finished

2. Condition: Form = “Party Request”

3. Send SMS: “Got it! What date are you thinking?”

4. Create internal alert for staff

5. Delay 1 day → send reminder if no response

Example 2: Feedback Form → Review Request

1. Trigger: Form Finished

2. Condition: Form = “Feedback”

3. If rating is high → send review link

4. If rating is low → notify manager

 

---

 

Best Practices 

• Keep the first message short and helpful (confirm + next step).

• Use tags to avoid duplicate experiences (ex: tag “Party Lead” and check before re-sending).

• If staff needs to respond, include an internal alert step early in the automation.

---