← All Workflows Dashboard Workflows Custom Builds Community Billing
The Vault›Workflows›Workflow 07
✦ Workflow 007 · Post-Session 002 ✦

Final Sale → Model Release.

The second she signs the Final Sale, this fires. Sends the Model Release. Required for every client regardless of advertising consent.

~8 Min Build Post-Session ✦ New
✦
Workflow 007 in GoHighLevel

The full workflow inside GoHighLevel.✦ Click to zoom

✦ The Overview ✦

What this workflow actually does.

The second she signs the Final Sale Form, this workflow fires and sends her the Model Release. The release documents her wishes whether she opts in to advertising or not.

No exceptions. Every client. Always.

✦ The Trigger ✦

What fires the workflow.

✦ Trigger Type · Document Signed

Final Sale Form Signed

When her Final Sale Form document status updates to Signed, this workflow fires automatically.

✦ The Steps ✦

The full sequence... step by step.

  1. I.

    Update Subject Field

    Sets the Subject for Proposal custom field to 'Model Release.'

  2. II.

    Update Intro Field

    Updates the Intro field with a message encouraging her to complete the image release agreement.

  3. III.

    Send Model Release

    Sends the Model Release document template directly to her email.

✦ How To Build This In GHL ✦

Click by click... exactly what to do.

Open GHL in another tab and follow these steps. Every button, every field, every click.

  1. I.Create The Workflow — Click Automation → Workflows → + New Workflow → Start From Scratch. Name it Final Sale to Model Release and click Continue.
  2. II.Set The Trigger — Search Document Signed, select your Final Sale Form template, click Save Trigger.
  3. III.Update Custom Fields — Click +, add Update Contact Field for Subject to 'Model Release.' Save. Add another for the Intro field. Save.
  4. IV.Send Model Release — Click +, search Send Document, select your Model Release template, click Save Action.
  5. V.Test Then Publish — Mark a document as signed on a test contact. Confirm the model release fires. Then publish.
✦ Why This Works ✦

Why I require this... always.

I require the model release even if she does NOT want her images shared. The release documents her wishes either way. Signed. On file. This protects YOU and HER. Always require it.

✦ What's Next ✦

What happens after this.

The moment she signs the Model Release, Workflow 008 (The Orchestrator) takes over.

✦ Common Mistakes ✦

Things that trip people up... and how to avoid them.

✦ Test Your Workflow ✦

Before you go live... check every box.

Test with your own contact first. Do not consider this workflow done until every box below is checked.

✦ Troubleshooting ✦

Something not firing? Start here.

?

Model Release did not send

Go to Documents and Contracts in GHL and find your Model Release template. If it shows Draft publish it then test again. Draft templates cannot be sent via automation.

?

Workflow triggered on wrong document

Go back to the trigger and confirm you selected your specific Final Sale Form from the dropdown rather than Any Document. The dropdown lists all your templates by name.

?

Custom fields blank after workflow ran

Click into each Update Contact Field action and confirm the correct field is selected from the dropdown. The field name must match exactly what exists in your contact custom fields.

✦ Questions & Discussion ✦

Have a question about this page?

0 Comments
Be the first to leave a comment or question. I read every single one. ✦