Skip to main content

Automation Triggers for Transaction Management in REsimpli

Transaction triggers, including why initial entry counts as a Status Change here and nowhere else.

Written by Anthony Estrada

Overview

A transaction begins when a property moves to Under Contract in the Acquisition pipeline and enters Transaction Management. Selling activity for that property is managed in the Dispo tab.

Trigger type

Available

New Record

No

Status Change

Yes

Activity Trigger

No

Other Triggers

Yes — six options

Manual Assignment

Yes

For how triggers, enrollment, and timing work generally, see Understanding Automation Triggers in REsimpli.

Status Change

Triggers when a property enters or moves to a selected status within a Transaction Management pipeline.

Initial entry behaves differently here

Transaction Management is the exception to the usual rule.

In Inventory and Rentals, the status a record has when it first arrives does not count as a Status Change. In Transaction Management it does.


When a property moves to Under Contract in the Acquisition pipeline, it enters

Transaction Management — and that initial entry can trigger the Status Change automation for the status it lands in.


Other Triggers

Tags

Triggers when any of the selected tags are added to a property in the Transaction Management pipeline.

Buyer Added

Triggers when a buyer is added in the Dispo tab.


Agent Added

Triggers when an agent is added in the Dispo tab.


Multiple Dispo Offers Received

Triggers when multiple offers exist and a qualifying additional offer is added in the Dispo tab. Offers from both Buyers and Agents count.


The first trigger happens when the second offer is added.


Re-enrollment behaviour:

  • If the automation is still running and another qualifying offer arrives, the existing automation continues — it does not restart, and a second instance does not begin

  • If the automation has already finished and another qualifying offer arrives, the property can enter again

Worked example:

  1. Offer 1 added — no trigger

  2. Offer 2 added — the automation starts

  3. Offer 3 arrives while it is still running — the existing automation continues

  4. The automation finishes

  5. Offer 4 added later — the property can enter the automation again

Expected Profit Changed

Triggers when the Expected Profit value is updated for a property in the Transaction Management pipeline.

Scheduled Closing Date Changed

Triggers when the Scheduled Closing Date is updated.


Manual Assignment

Lets a property in Transaction Management be added to an automation by hand.

Only Manual Assignment automations can be bulk assigned, and the account-wide limit is 100 records per day.

Things to Watch

  • There is no Activity Trigger for transactions. Communication-based automations belong on the Lead, Buyer, Agent, or Vendor record instead.

  • Initial entry counts as a Status Change here and nowhere else. If you are used to Inventory behaviour, this will surprise you.

  • Multiple Dispo Offers Received does not restart mid-run. A property receiving offers in quick succession enters once, not repeatedly.

  • Buyer Added and Agent Added are Dispo tab events. Adding a buyer elsewhere does not fire them.

Full Trigger List

Status Change

Other Triggers — Tags · Buyer Added · Agent Added · Multiple Dispo Offers Received · Expected Profit Changed · Scheduled Closing Date Changed

Manual Assignment

Did this answer your question?