Learn how to automate workflows in GHL Customer Care using the Documents & Contracts trigger. Filter by status, template, value, and streamline client document handling.
5 min read1,095 words10 explained imagesUpdated Fri, 25 Jul, 2025 at 11:13 AM
Assistants need to reach this page over the internet. While it is only running on your machine, these two buttons will not be able to load it.
Each image has a one line explanation. Switch to full detail for the step it belongs to, the fields and buttons involved, examples and the whole procedure.
This article explains how to use the “Documents & Contracts” workflow trigger to automate actions based on document status. Whether a document is sent, signed, viewed, or completed, this trigger allows you to kick off automated workflows like sending notifications, tagging contacts, or updating pipelines. You can also filter workflows by template, recipient type, or document values to create highly specific automation paths. This is especially useful for managing proposals, NDAs, and signed agreements more efficiently.
The Documents & Contracts workflow trigger in GHL Customer Care is designed to automate actions when the status of a document changes—such as when it’s sent, viewed, signed, or completed. This trigger connects the document lifecycle to your workflow automation, allowing you to take action instantly based on recipient interactions. It’s ideal for streamlining communication, record-keeping, and follow-up tasks tied to proposals, agreements, or contracts.
This trigger is especially useful for agencies, service providers, and businesses that regularly send documents for signature or approval. By enabling filters like Status, Template Name, and Recipient Type, users can build highly targeted workflows that match specific scenarios. Whether you’re managing NDAs, sales proposals, or contracts, this trigger helps keep your processes organized, timely, and scalable.
Key Benefits of Documents & Contracts Workflow Trigger
This workflow trigger gives users the ability to automate document-based tasks with precision. Whether you’re tracking signatures or customizing follow-up based on document status, the trigger enhances operational efficiency and communication.
Automated Follow-Up Based on Document Status: Trigger personalized workflows when a document is sent, viewed, signed, or completed—ensuring timely reminders, updates, or internal actions without manual tracking.
Improved Record Management: Automatically update CRM fields, Google Sheets, or Slack channels based on document activity to keep your records up to date and eliminate data entry errors.
Dynamic Filtering for Targeted Automation: Use filters like Template Name, Status, and Recipient Type to trigger workflows only for specific documents or recipients—perfect for managing multiple document types with different workflows.
Enhanced Internal Team Collaboration: Send instant internal notifications when key actions are taken on a document, allowing sales or operations teams to follow up or take the next step without delay.
Personalized Client Experience: Use custom values from the contact or document to personalize outgoing emails, notifications, or actions—helping you maintain a professional and client-focused communication flow.
How to Configure the Documents and Contracts Workflow Trigger
Navigate to Automation
From the left-hand navigation panel, click on Automation, then select the blue + Create Workflow button on the top-right. Choose Start from Scratch to build a custom workflow.
Navigate to Automation (image 1 of 10)What this shows From the left-hand navigation panel, click on Automation, then select the blue + Create Workflow button on the top-right.What this showsIllustrates the "Navigate to Automation" section of "Workflow Trigger - Documents & Contracts".This screenshot appears in the "Navigate to Automation" section of "Workflow Trigger - Documents & Contracts". The text alongside this image reads: From the left-hand navigation panel, click on Automation, then select the blue + Create Workflow button on the top-right. Choose Start from Scratch to build a custom workflow. Immediately after, the guide continues: Inside the workflow builder, click + Add New Trigger to set your entry condition. In the trigger list, scroll to the Payments section and click Documents & Contracts. This will trigger the workflow when a document-related event occurs.Image 1 of 10What to chooseFrom the left-hand navigation panel, click on Automation, then select the blue + Create Workflow button on the top-right. Choose Start from Scratch to build a custom workflow.Next stepInside the workflow builder, click + Add New Trigger to set your entry condition. In the trigger list, scroll to the Payments section and click Documents & Contracts. This will trigger the workflow when a document-related event occurs.
Add a New Trigger
Inside the workflow builder, click + Add New Trigger to set your entry condition. In the trigger list, scroll to the Payments section and click Documents & Contracts. This will trigger the workflow when a document-related event occurs.
Add a New Trigger (image 2 of 10)What this shows Inside the workflow builder, click + Add New Trigger to set your entry condition.What this showsIllustrates the "Add a New Trigger" section of "Workflow Trigger - Documents & Contracts".This screenshot appears in the "Add a New Trigger" section of "Workflow Trigger - Documents & Contracts". The text alongside this image reads: Inside the workflow builder, click + Add New Trigger to set your entry condition. In the trigger list, scroll to the Payments section and click Documents & Contracts. This will trigger the workflow when a document-related event occurs. Immediately after, the guide continues: For organizational clarity, give your trigger a specific name (e.g., “Contract Viewed – Onboarding Doc”) in the Workflow Trigger Name field.Image 2 of 10What to clickInside the workflow builder, click + Add New Trigger to set your entry condition. In the trigger list, scroll to the Payments section and click Documents & Contracts. This will trigger the workflow when a document-related event occurs.Next stepFor organizational clarity, give your trigger a specific name (e.g., “Contract Viewed – Onboarding Doc”) in the Workflow Trigger Name field.
Name Your Trigger
For organizational clarity, give your trigger a specific name (e.g., “Contract Viewed – Onboarding Doc”) in the Workflow Trigger Name field.
Name Your Trigger (image 3 of 10)What this shows For organizational clarity, give your trigger a specific name (e.g., “Contract Viewed – Onboarding Doc”) in the Workflow Trigger Name field.What this showsIllustrates the "Name Your Trigger" section of "Workflow Trigger - Documents & Contracts".This screenshot appears in the "Name Your Trigger" section of "Workflow Trigger - Documents & Contracts". The text alongside this image reads: For organizational clarity, give your trigger a specific name (e.g., “Contract Viewed – Onboarding Doc”) in the Workflow Trigger Name field. Immediately after, the guide continues: Click Add Filters to set the specific conditions that determine when the workflow should trigger.Image 3 of 10What this coversFor organizational clarity, give your trigger a specific name (e.g., “Contract Viewed – Onboarding Doc”) in the Workflow Trigger Name field.Next stepClick Add Filters to set the specific conditions that determine when the workflow should trigger.
Add Filters
Click Add Filters to set the specific conditions that determine when the workflow should trigger.
Add Filters (image 4 of 10)What this shows Click Add Filters to set the specific conditions that determine when the workflow should trigger.What this showsIllustrates the "Add Filters" section of "Workflow Trigger - Documents & Contracts".This screenshot appears in the "Add Filters" section of "Workflow Trigger - Documents & Contracts". The text alongside this image reads: Click Add Filters to set the specific conditions that determine when the workflow should trigger. Immediately after, the guide continues: You can choose from the following standard filters.Image 4 of 10What to clickClick Add Filters to set the specific conditions that determine when the workflow should trigger.Next stepYou can choose from the following standard filters:
Choose Filter Fields and Conditions
You can choose from the following standard filters:
Recipient Type: Contact or Business User
Status: Viewed, Signed/Accepted, Completed, Sent
Template: Specific document template
Value: Contract value, useful for high-ticket filtering
Choose Filter Fields and Conditions (image 5 of 10)What this shows Value: Contract value, useful for high-ticket filteringWhat this showsIllustrates the "Choose Filter Fields and Conditions" section of "Workflow Trigger - Documents & Contracts".This screenshot appears in the "Choose Filter Fields and Conditions" section of "Workflow Trigger - Documents & Contracts". The text alongside this image reads: Value: Contract value, useful for high-ticket filtering. This part of the guide covers 4 fields, listed below. Immediately after, the guide continues: Use the “Recipient Type” filter to specify who the document was sent to—either a Business User or a Contact. This ensures your workflow only triggers based on actions taken by the intended recipient type.Image 5 of 10What this coversValue: Contract value, useful for high-ticket filtering
Fields in this part of the guideRecipient Type: Contact or Business UserStatus: Viewed, Signed/Accepted, Completed, SentTemplate: Specific document templateValue: Contract value, useful for high-ticket filtering
Next stepUse the “Recipient Type” filter to specify who the document was sent to—either a Business User or a Contact. This ensures your workflow only triggers based on actions taken by the intended recipient type.
Recipient Type Filter
Use the “Recipient Type” filter to specify who the document was sent to—either a Business User or a Contact. This ensures your workflow only triggers based on actions taken by the intended recipient type.
Recipient Type Filter (image 6 of 10)What this shows Use the “Recipient Type” filter to specify who the document was sent to—either a Business User or a Contact.What this showsIllustrates the "Recipient Type Filter" section of "Workflow Trigger - Documents & Contracts".This screenshot appears in the "Recipient Type Filter" section of "Workflow Trigger - Documents & Contracts". The text alongside this image reads: Use the “Recipient Type” filter to specify who the document was sent to—either a Business User or a Contact. This ensures your workflow only triggers based on actions taken by the intended recipient type. Immediately after, the guide continues: The “Status” filter lets you trigger workflows based on the stage of the document—such as when it’s Sent, Viewed, Signed/Accepted, or Completed. This allows you to tailor automation to specific actions taken on the document.Image 6 of 10What to fill inUse the “Recipient Type” filter to specify who the document was sent to—either a Business User or a Contact. This ensures your workflow only triggers based on actions taken by the intended recipient type.Next stepThe “Status” filter lets you trigger workflows based on the stage of the document—such as when it’s Sent, Viewed, Signed/Accepted, or Completed. This allows you to tailor automation to specific actions taken on the document.
Status Filter
The “Status” filter lets you trigger workflows based on the stage of the document—such as when it’s Sent, Viewed, Signed/Accepted, or Completed. This allows you to tailor automation to specific actions taken on the document.
Status Filter (image 7 of 10)What this shows The “Status” filter lets you trigger workflows based on the stage of the document—such as when it’s Sent, Viewed, Signed/Accepted, or Completed.What this showsIllustrates the "Status Filter" section of "Workflow Trigger - Documents & Contracts".This screenshot appears in the "Status Filter" section of "Workflow Trigger - Documents & Contracts". The text alongside this image reads: The “Status” filter lets you trigger workflows based on the stage of the document—such as when it’s Sent, Viewed, Signed/Accepted, or Completed. This allows you to tailor automation to specific actions taken on the document. Immediately after, the guide continues: The “Template” filter allows you to specify which document or contract template should trigger the workflow. This is useful when you want automations to run only for certain agreements, such as onboarding forms or service contracts.Image 7 of 10What this coversThe “Status” filter lets you trigger workflows based on the stage of the document—such as when it’s Sent, Viewed, Signed/Accepted, or Completed. This allows you to tailor automation to specific actions taken on the document.Next stepThe “Template” filter allows you to specify which document or contract template should trigger the workflow. This is useful when you want automations to run only for certain agreements, such as onboarding forms or service contracts.
Template Filter
The “Template” filter allows you to specify which document or contract template should trigger the workflow. This is useful when you want automations to run only for certain agreements, such as onboarding forms or service contracts.
Template Filter (image 8 of 10)What this shows The “Template” filter allows you to specify which document or contract template should trigger the workflow.What this showsIllustrates the "Template Filter" section of "Workflow Trigger - Documents & Contracts".This screenshot appears in the "Template Filter" section of "Workflow Trigger - Documents & Contracts". The text alongside this image reads: The “Template” filter allows you to specify which document or contract template should trigger the workflow. This is useful when you want automations to run only for certain agreements, such as onboarding forms or service contracts. Immediately after, the guide continues: The “Value” filter lets you trigger workflows based on the monetary amount or numerical value assigned to a document. You can apply operators like “Greater than” or “Equals to” to run automations only when documents meet specific value….Image 8 of 10What this coversThe “Template” filter allows you to specify which document or contract template should trigger the workflow. This is useful when you want automations to run only for certain agreements, such as onboarding forms or service contracts.Next stepThe “Value” filter lets you trigger workflows based on the monetary amount or numerical value assigned to a document. You can apply operators like “Greater than” or “Equals to” to run automations only when documents meet specific value conditions—ideal for contracts tied to budget thresholds or pricing tiers.
Value Filter
The “Value” filter lets you trigger workflows based on the monetary amount or numerical value assigned to a document. You can apply operators like “Greater than” or “Equals to” to run automations only when documents meet specific value conditions—ideal for contracts tied to budget thresholds or pricing tiers.
Value Filter (image 9 of 10)What this shows The “Value” filter lets you trigger workflows based on the monetary amount or numerical value assigned to a document.What this showsIllustrates the "Value Filter" section of "Workflow Trigger - Documents & Contracts".This screenshot appears in the "Value Filter" section of "Workflow Trigger - Documents & Contracts". The text alongside this image reads: The “Value” filter lets you trigger workflows based on the monetary amount or numerical value assigned to a document. You can apply operators like “Greater than” or “Equals to” to run automations only when documents meet specific value conditions—ideal for contracts tied to budget thresholds or…. Immediately after, the guide continues: Once your filters are set, click Save Trigger to apply the configuration. Your workflow will now automatically activate based on document events that match the criteria you’ve defined.Image 9 of 10What this coversThe “Value” filter lets you trigger workflows based on the monetary amount or numerical value assigned to a document. You can apply operators like “Greater than” or “Equals to” to run automations only when documents meet specific value conditions—ideal for contracts tied to budget thresholds or pricing tiers.Next stepOnce your filters are set, click Save Trigger to apply the configuration. Your workflow will now automatically activate based on document events that match the criteria you’ve defined.
Save Your Trigger
Once your filters are set, click Save Trigger to apply the configuration. Your workflow will now automatically activate based on document events that match the criteria you’ve defined.
Save Your Trigger (image 10 of 10)What this shows Once your filters are set, click Save Trigger to apply the configuration.What this showsIllustrates the "Save Your Trigger" section of "Workflow Trigger - Documents & Contracts".This screenshot appears in the "Save Your Trigger" section of "Workflow Trigger - Documents & Contracts". The text alongside this image reads: Once your filters are set, click Save Trigger to apply the configuration. Your workflow will now automatically activate based on document events that match the criteria you’ve defined. Immediately after, the guide continues: Q: Can I trigger different workflows based on whether a document was signed by a Contact versus a Business User?Image 10 of 10How to confirmOnce your filters are set, click Save Trigger to apply the configuration. Your workflow will now automatically activate based on document events that match the criteria you’ve defined.Next stepQ: Can I trigger different workflows based on whether a document was signed by a Contact versus a Business User?
Frequently Asked Questions
Q: Can I trigger different workflows based on whether a document was signed by a Contact versus a Business User?
Yes. Using the Recipient Type filter, you can choose whether the trigger applies to Contacts (external users like leads or clients) or Business Users (team members or staff). This is especially useful when you need to run separate workflows for client-facing agreements versus internal approvals. For example, you could send a client onboarding email if a Contact signs a proposal, but trigger an internal Slack alert if a Business User signs off on an internal review document.
Q: What happens if the same document is both viewed and signed—will the trigger fire twice?
Yes. Each status change (e.g., from “Viewed” to “Signed/Accepted”) is treated as a separate event and can independently activate the workflow if both statuses are configured as triggers. To avoid redundant automations, you should add conditional logic inside your workflow to check for tags or custom field values before executing actions. This prevents overlapping messages or updates.
Q: Can I use the “Value” filter to trigger workflows only for high-ticket contracts, like proposals above $5,000?
Absolutely. The Value filter allows you to apply operators such as “Greater than” or “Equals to.” You can configure your trigger to only activate when the contract’s value exceeds a specific threshold. This is particularly useful for sending different onboarding steps for high-value clients or notifying sales managers about large deals.
Q: How do I restrict workflows to only trigger for specific document templates (e.g., NDAs or service agreements)?
Use the Template filter to select which specific document templates should activate the workflow. This allows you to run unique automations tied to individual document types. For instance, you might send a welcome sequence for clients who signed a “Service Agreement” template, but a different sequence for those who completed a “NDA” template. This ensures workflows are context-specific and only trigger when the exact template is used.
