How to automate a custom object with workflows
Go to Automation › Workflows › Create Workflow and choose the workflow based on your object (e.g. Property). Use the "Property Created" or "Property Changed" triggers (filtered, e.g. Status = Sold) and actions like Update Associated Record, Clear Fields, Add Note or Webhook. Publish.
Updated on
Before you start
- The object already exists, with its fields and associations set up: the workflow only sees what's already defined.
- Decide when it should fire (record created or record changed) and what should happen next.
- Object workflows run "on" the object record (the property, the policy), not on the contact. To message the linked contact, use the associated-record actions or a contact workflow.
Where to find it
Automation › Workflows › Create Workflow › (object-based workflow, e.g. Property)
Step by step
Create the object workflow
- Open Automation › Workflows and click Create Workflow.
- Choose the workflow type based on your object (e.g. Property, Vehicle, Policy) instead of the contact workflow.
- Give the workflow a clear name (e.g. "Property sold – close out").
Choose the trigger
- Click Add Trigger.
- Pick one of the object's triggers:
- (Object) Created — e.g. Property Created: fires when a new record comes in (by hand, through a form or an import).
- (Object) Changed — e.g. Property Changed: fires when a record is updated.
- Inbound Webhook: fires when another system sends data.
- Under Filters, narrow the trigger to what matters, for example Status is "Sold". Without a filter, any change fires the workflow.
- Save the trigger.
Add the actions
- Click the + below the trigger and choose an action:
- Create (Object) or Associated Record: creates another record (e.g. an opportunity linked to the property).
- Update (Object) or Associated Record: changes fields on the record itself or on a linked record (e.g. mark the "Buyer" contact as a customer).
- Clear fields of (Object) or Associated Record: wipes values from temporary fields.
- Associate Records: links the record to a contact found by email, phone or another field.
- Add Note: logs a note on the record.
- Custom Webhook and Google Sheets: send the record's data out (e.g. one row per sale in a sheet).
- Combine with the usual tools: If/Else, Wait, Go To, date/number/text formatters, Add To Workflow / Remove From Workflow.
- Save each action.
Publish and test
- Switch the toggle to Published and save.
- Change a test record (e.g. set its status to "Sold") and check in Execution Logs that the workflow ran and the actions happened.
Tips
- Real estate example: trigger Property Changed filtered by Status = "Sold"; actions: update the associated "Agent" contact, add a row to Google Sheets with the sale details, and clear the "Internal notes" fields.
- To run a workflow on records that already exist (e.g. all policies about to renew), select them in the object's list and use the Trigger Automation bulk action; the workflow must be published.
- After a bulk import, the (Object) Created trigger fires for every imported record; use it to link each record to the right contact.
Common problems
- I don't see my object's triggers → You created a contact workflow. Create a new one and pick the object-based type right at the start.
- The workflow fires on every change → The trigger has no filter. Edit the trigger and add the condition (e.g. Status is "Sold").
- The workflow doesn't fire when I change the record → Check it's Published and that the filter value is spelled exactly as in the field (dropdowns distinguish options).
- "Update Associated Record" can't find the contact → There's no association between the record and the contact, or you picked a different label. Check the record's Related Objects section.
- I want to email the linked contact → Messaging actions aren't in object workflows. Use a contact workflow, or select the records in the list and use the Send email bulk action to associated contacts.
Frequently asked questions
Can I send the object's data to another system?
Yes. Use the Custom Webhook action to send the record's fields to an external endpoint, or Google Sheets to log them in a spreadsheet.
Does the object have to exist before the workflow?
Yes. Create the object, its fields and associations first; only then do they appear in triggers and actions.
Was this helpful?
Thanks for your feedback.
