Send Emails from Custom Object and Company Workflows

TL;DR

Workflows now send emails from custom objects and company records, targeting associated contacts and including custom data. Enable the Email Action in Labs to use it.

Who this affects

This affects users leveraging custom objects and company records in their HighLevel accounts. If you don't use custom objects or company records for detailed client or project management, this update may not be relevant to you.

What changed

• Workflows can now send emails directly from custom object records.
• Workflows can now send emails directly from company records.
• Users can email contacts associated with custom objects, such as projects, jobs, or cars.
• Users can choose which associated contacts should receive an email.
• Association labels can be used to target specific contacts for email delivery.
• Custom object data can be included directly in these emails.
• Emails can be sent automatically when a custom object is created or changed.
• The Email Action must be enabled in Labs to access this functionality.
• Triggers and actions specific to custom object workflows are available.
• Filters can be added to triggers to refine when emails are sent.
• HighLevel has not confirmed who is affected, where in the product this is located, what it replaces or breaks, what limits or plan gating apply, or its rollout status.

Where to find it

HighLevel has not confirmed the exact location yet. Based on the description, this functionality will be found within the workflow builder, specifically when setting up workflows for custom objects or company records. You will likely find new email actions or expanded options for existing email actions once the 'Email Action' is enabled in the 'Labs' section of your account settings.

How agencies will use this

An agency managing client projects using custom objects could automate communication. For example, when a custom object representing a 'Project' is created or its 'Status' field changes to 'In Progress', a workflow can trigger. This workflow could then send an email directly from that 'Project' custom object. The email could be sent to specific associated contacts, perhaps the client contact with the label 'Primary Project Contact', including details from the custom object like the 'Project Name' or 'Project Manager'. If the 'Project' reaches the 'Completed' status, another automated email could be sent to the assigned internal team members or the client, leveraging custom object data to summarize the project's outcome or request feedback. This removes manual email sending and ensures relevant stakeholders are always informed based on custom object lifecycle events.

Our take

This is a solid, practical improvement for agencies and SaaS users heavily relying on custom objects and company records. Automating email communication directly from these records, especially with the ability to use association labels and custom data, streamlines operations. It adds useful functionality for those who need it, but if custom objects aren't a core part of your setup, it's not a major update you need to act on immediately.