Who This Is For / When to Use
This feature is for users who use Custom Objects (such as Homes, Orders, Products, or Properties) and need automation to run when those object records are created or updated.
Use Custom Object workflows when:
Automation should start from a Custom Object instead of a contact.
Business logic is tied to object lifecycle events (created or changed).
You need precise, object-driven automation instead of contact-based triggers.
What Are Custom Object Workflows
Custom Object workflows are workflows that:
Use a Custom Object as the trigger source.
Run when a Custom Object record is created or changed.
Can execute actions such as updating records, clearing fields, sending data, or syncing with external systems.
These workflows are object-centric, not contact-centric.
Creating a Custom Object Workflow
Step 1: Open the Workflow Builder
Navigate to Automation > Workflows.
Click Create Workflow.
Choose Start from Scratch.
Step 2: Select a Custom Object Trigger
In the trigger selection panel, locate Custom Object.
Choose the Custom Object you want to automate (for example, Home).
Select the trigger event:
Object Created
Object Changed
Available Custom Object Triggers
Custom Object workflows currently support these trigger types:
Custom Object Created
Triggers when a new record is created.Custom Object Changed
Triggers when any field value on an existing record changes.
Each trigger runs independently and evaluates the Custom Object record directly.
Adding Actions to a Custom Object Workflow
After selecting a trigger, define what happens next.
Supported Action Types
Custom Object workflows support the same core workflow actions, including:
Create or update records
Clear fields
Send data via webhook
Google Sheets logging
Conditional logic (If/Else)
Wait steps
Goal events
Splits
Customizing Workflow Logic
You can enhance Custom Object workflows with internal logic steps, such as:
If / Else – Run actions only when object conditions are met.
Wait – Delay actions based on time or conditions.
Split – Send records down multiple paths.
Goal Event – Jump records forward when a goal is achieved.
This allows advanced automation tied directly to object state changes.
Saving, Testing, and Publishing
Click Save to store your workflow.
Use Test Workflow to validate behavior with sample data.
Toggle from Draft to Publish to activate the workflow.
Once published, the workflow runs automatically whenever the Custom Object trigger conditions are met.
Use Case Example
A real estate team uses a Home Custom Object to track listings.
Trigger
Home object changed
Field: Home Status → Closed
Actions
Update associated agent records
Log the sale to Google Sheets
Clear internal notes fields that are no longer needed
This ensures records stay accurate without manual updates.
Common Issues and Fixes
Workflow not triggering
Confirm the workflow trigger is set to a Custom Object, not a contact.
Verify the correct Custom Object and trigger event are selected.
Actions not updating expected records
Ensure field mappings reference the Custom Object fields, not contact fields.
Confirm associations exist when updating related records.
Multiple triggers firing unexpectedly
Add If/Else conditions to narrow when the workflow should run.
FAQ
What triggers are available for Custom Object workflows?
You can trigger workflows when a Custom Object record is created or when any field on the record changes.
Can I update associated records when a Custom Object changes?
Yes. You can update or clear fields on associated records as part of the workflow actions.
Can I send Custom Object data to external systems?
Yes. You can use Webhooks or Google Sheets actions to send Custom Object data externally.
Can one workflow handle multiple Custom Objects?
A single workflow is tied to one Custom Object trigger. You can use conditions or create multiple workflows for different objects.
Can I use conditional logic in Custom Object workflows?
Yes. You can add If/Else conditions, waits, splits, and goal events to fully customize the workflow behavior.