Why This Matters
Automations reduce repetitive work by triggering actions when specific events or conditions occur in SubcontractorHub. You can use them to send emails or text messages, update fields, schedule appointments, create tasks, and manage other workflow actions.
Automation options depend on the selected module and job type. For Appointment automations, automated emails can also use proposal information through Proposal merge fields, allowing appointment communications to include relevant proposal details automatically.
Follow the steps below to create and configure an automation.
What You'll Need
Admin access or permission to manage Automations.
The module and job type for the automation.
The event or condition that should trigger the automation.
The action or actions that should occur.
A connected email or SMS service when using communication actions.
The email content, recipients, and applicable merge fields when using “Send Email”.
Step-by-Step Instructions
Step 1: Navigate to “Manage Database” and click “Database” from the main menu.
Step 2: Under “Additional,” click “Automation.”
Step 3: Click “Add New Automation.”
Step 4: Enter the “Title” of the automation.
Step 5: Select the module for the automation, then click “Next.”
Step 6: Select the applicable job type, then click “Start Now!”
Step 7: Click “Add Start Trigger” to define when the automation should run.
Step 8: Select the trigger for the automation.
Step 9: Click the “+” icon to add an action.
Step 10: Select the action you want the automation to perform. To send an automated email, select “Send Email.”
Step 11: Select the recipient from the “To” dropdown and any additional recipients from “CC.” Enter the subject and message, add any applicable merge fields, then click “Save.”
Note: When “Appointments” is selected as the automation module and “Send Email” is used as the action, Proposal merge fields are available along with Project, Lead, and Customer merge fields. Proposal merge fields can be used for Appointment automations across all job types.
Step 12: Click the “+” icon to add another action.
Step 13: Select “Send Text Message.”
Step 14: Select the recipient from the “To” dropdown and enter the message.
Step 15: Click the “+” icon to add another action.
Step 16: Select “Update Fields” to automatically update applicable fields.
Step 17: Select the applicable “Field” and “Field Stages,” then click “Save.”
Note: The “Stage Input” field can be left blank when saving the automation. To remove an existing Stage Input value, click the delete icon beside the field, then click “Save.”
Step 18: You can also select If/Else action from the list.
Step 19: You can choose from a list of conditions, fields, and operators.
Step 20: Click the “+” icon to set another action.
Note: If an automation fails, an email notification is sent to the organization administrator and the automation creator.
Note: When the Closed Won Document Sign field is selected, “Welcome Call Completed” is available as a trigger.
Note: We’ve enabled automation options for Finance Partner fields in both Projects and Proposals modules. This allows users to trigger specific actions based on the selection or update of finance partner information.
How to Use Finance Partner Fields in Automations
Finance Partner fields can be used in automations for the Projects and Proposals modules.
Step 1: After selecting the job type, choose “When Field Updated” as the trigger.
Step 2: Under “Select Field,” choose “Finance Partner.”
Step 3: Select the applicable finance partner from “Field Value.”
Step 4: Click “Save.”
Note: If you want to control when the automation should stop based on specific finance partner values, you can do so by setting conditions using the If/Else option.
Step 1: Under “Automation Ends Here,” select “If/Else.”
Step 2: Click “Add Condition.”
Step 3: Select “If Field Value,” then choose “Finance Partner” for the field.
Step 4: Set the operator to “Equal To” and select the applicable finance partner in “Field Value.”
Step 5: Click “Save” to apply the condition.
Note: The "When Change Order" trigger is specifically available for automations within the Proposals module. It allows you to create automated actions—such as alerts or notifications—when there’s a change in the order status.
Change Order Status supports:
Created – when a change order is initiated from scratch.
Completed – when it's finalized or closed.
Voided – when it's disabled or deleted.
For instance: You can set up an automation to send a notification to the user when a change order is marked as completed.
This update makes it easier to track progress and communicate change order updates without manual follow-ups.
Note: If the “Site Survey Photos Completed” or “Installation Photos Completed” triggers are set in an automation, checking them off in the public URL will automatically send a completion notification email to the assigned recipients.
Note: For the Project module, we’ve added an automation to trigger notifications When a Change Order is marked as completed. This ensures all stakeholders are promptly informed.
Step1: Select "When Change Order" as the trigger condition.
Step 2: Choose "Completed" from the status options and click “Save”.
Step 3: Under "Automation Ends Here", select the desired action (e.g., send email, send SMS, etc.).
Step 4: Choose your preferred notification method and complete the setup.
Note: Now you can send triggers for “When Message Received”. You have the option to either send an email or send an SMS if you have connected and enabled Google Services and Twilio, respectively. Follow the steps below to learn how to set up this trigger.
Step 1: Select the “When Message Received” trigger.
Step 2: Choose the mode of message, “SMS” or “Email,” and click “Save”.
How to Trigger Automations for “On-Hold” Projects
You can add an automation specific to “Project Module” that triggers specific actions when a project's status changes to "On-Hold." It helps to streamline project management and ensure consistent handling of projects placed on hold. Follow the steps below to configure this automation.
Step 1: After clicking on “Add Start Triggers,” click on “When Stage Changes To” to set up the automation.
Step 2: From the tab, select “On-Hold.”
Step 3: Click on “Save.”
Step 4: When you click on “Automation Ends Here,” you can choose the necessary follow-up actions to be executed automatically when a project is moved to On-Hold. For instance, you can send an Email, set up an SMS or any other automation of your desired choice.
Note: We’ve now added automation options for projects that are resumed after being On-Hold. When setting up a new automation, choose “When Stage Changes To” and select “Resumed (On-Hold)” from the tab. This allows you to trigger specific actions, such as notifying clients, updating team members, or resuming related workflows, using the same steps outlined above.
How to run test on automations
Before putting your automation into live use, it's important to run a test to ensure everything is configured correctly and triggers as expected. The update has been implemented for leads, proposals, projects, customers, and organizations; however, it is not currently supported for Proposal QC or Project Service. Follow the steps below to run a test on your automation and validate its functionality.
Step 1: Navigate to your automation dashboard where all existing automations are listed. Find the specific automation you want to test, and click “Edit” to open its configuration.
Step 2: From the dropdown menu, select “Edit”
Step 3: Once inside edit mode, locate the “Run Test” button in the top-right corner of the screen. This button initiates the test process.
Step 4: After clicking the button, a new tab or modal will appear that allows you to patch sample data into the automation. You can either select a test dataset from the dropdown or manually search for specific data records to run the test against.
Step 5: If the automation is configured correctly and the test runs successfully, the “Automation Ends Here” step will turn green, indicating that the automation completed its flow without any errors.
Step 6: If the automation is misconfigured and the test run fails, the “Automation Ends Here” step will be highlighted in red, indicating that errors occurred during the automation process.
How to set time intervals between actions for automations
Step 19: Click “Wait/Delay” to specify the duration of the automation’s waiting period.
Step 20: Enter the waiting period duration and click “Save”.
Step 21: Click the “+” icon to set another action.
Step 22: You can also schedule and manage an appointment here.
Step 23: To schedule the appointment, select the “Appointment Type”, add “Title”, select “Attendees” and “Tags”, and add the “Description”.
Step 24: Set the custom scheduling options such as the date, time, and duration of the appointment. Click “Save”.
Note: By default, only business days (Monday-Friday) are selected for scheduling purposes. If you want to include the weekends (Saturday and/or Sunday), click the checkboxes of the respective days.
Step 25: Click the “+” icon to set another action.
Step 26:Click “Create Task” to generate a task linked to this project.
Step 27: Enter the “Subject” and “Description”, and select "Assign To”, “Stage” and “Priority”.
Step 28: Set the number of days to set the task and click “Save”.
Note: By default, only business days (Monday-Friday) are selected for scheduling purposes. If you want to include the weekends (Saturday and/or Sunday), click the checkboxes of the respective days.
Step 29: Once the automation is set, click “Launch”.
Step 30: Click “Yes”.
Note: If you are creating an automation for any module, you can split the automation based on If/Else conditions.
Step 1: Click “If/Else”.
Step 2: Click “Add Condition” button.
Step 3: Select the “Condition” and “Field”, and click “Save”.
Step 4: Your automation is now split based on Conditions.
Note: You can set actions for both conditions “Yes” and “No”.
Note: A new Customer Language option is now available under the If/Else block. You can use it to trigger automations based on the customer’s selected language. Simply choose the desired language from the dropdown menu.
Note: The Perfect Packet field is now available in automations, allowing you to create triggers or actions based on its status.
Note: You can now trigger automations when finance milestones are updated. Currently, this applies to Lightreach and Solrite; whenever their status changes in a project, the automation will be triggered.
How to Trigger an Automation When a Project Tag Is Added
The “When Tag Added” trigger runs an automation when a selected tag is added to a project. This trigger is available for the Project module across all job types.
Note: “Enable tagging features” must be enabled under Project Settings for “When Tag Added” to appear as an automation trigger.
Step 1: Create or edit an automation for the Project module, then click “Add Start Trigger.”
Step 2: Select “When Tag Added.”
Step 3: Under “Select Field,” choose the project tag that should trigger the automation.
Step 4: Click “Save.”
How to Trigger an Automation When a Perfect Packet Question Is Answered
The “When Perfect Packet Question Answered” trigger runs an automation when a selected Perfect Packet question receives the configured answer. This trigger is available for the Proposal module across all job types.
Step 1: Create or edit an automation for the Proposal module, then click “Add Start Trigger.”
Step 2: Select “When Perfect Packet Question Answered.”
Step 3: Under “Select Field,” select the applicable Perfect Packet question.
Step 4: Under “Field Value,” enter the answer that should trigger the automation. Leave the field blank if any value should trigger the automation.
Step 5: Click “Save.”
Note: When a specific “Field Value” is entered, the automation runs only when the answer matches that value. If “Field Value” is left blank, any answer to the selected question can trigger the automation.
Real-World Example
A team creates an Appointment automation that sends an email when a customer appointment reaches the selected trigger. The email uses Customer merge fields for the recipient's information and Proposal merge fields for relevant proposal details. When the automation runs, SubcontractorHub fills those fields with information from the associated records instead of requiring the team to enter the same information manually for every appointment.
Pro Tips
Choose the module first: Available triggers, actions, and fields depend on the module selected when the automation is created.
Use merge fields where appropriate: Merge fields help keep automated emails personalized without manually entering record information.
Check the merge field category: For Appointment email automations, select the appropriate Project, Lead, Customer, or Proposal category based on the information you need.
Use If/Else for different outcomes: Add conditions when the same trigger should lead to different actions based on record information.
Run a test before launch: Use the available test workflow to check the automation before relying on it in live operations.
Review the full automation before launching: Confirm the trigger, conditions, recipients, and actions before activating the workflow.
Troubleshooting
Problem | Solution |
The automation does not run. | Confirm that the automation has been launched and that the configured trigger conditions have been met. |
Proposal merge fields do not appear in the email editor. | Confirm that “Appointments” is selected as the module and “Send Email” is selected as the action. |
A Proposal merge field does not populate in the email. | Confirm that the selected field contains information in the proposal associated with the appointment. |
An automated email or SMS is not sent. | Confirm that the applicable communication service is connected and enabled and that the recipient information is available. |
An Update Fields action will not save. | Review the selected field configuration. The “Stage Input” field may be left blank when it is not required. |
An On-Hold trigger does not appear. | Confirm that the automation is configured for the Project module. |
A Finance Partner field is not available. | Confirm that the automation is configured for the Projects or Proposals module. |
The automation test fails. | Review the step shown in the failed state, correct the configuration, and run the test again. |
The automation fails after launch. | Review the failure notification sent to the organization administrator and automation creator to identify the affected step. |








