Every automation has two parts:

The trigger decides when a record enters the automation

The steps decide what happens after it does

This article explains the trigger types, the activity triggers shared across modules, and the enrollment rules that govern when records enter, re-enter, and continue through your automations.

For the triggers available in a specific module, see the article for that module — Leads, Transactions, Inventory, Sold, Rentals, Buyers, Agents, Vendors, or List Stacking.

The triggers available depend on the module. Not every trigger type exists everywhere.

Starts an automation when a qualifying record is newly created or enters the applicable area.
​

Examples: New Lead Created, New Inventory Added, New Sold Property, New Rental Property, New Buyer Contact, New Agent Contact, New Vendor Contact.

​New Record automations only respond to future events. Existing records are not enrolled simply because they already meet the criteria.

Records created manually or through the REsimpli Open API can trigger these automations. Some record types may also be created through supported forms or workflows.

Starts an automation when an existing record is moved to a selected status.
​

A status change triggers the automation when it is made:

A status change does not trigger the automation when it comes from:

Status changes cannot currently be performed through the Open API or Zapier.

Activity Triggers start automations based on communication or other activity. Where they are available, the same six options are used across every module.
​

Triggers based on the AI-detected intent of an incoming message. Available intents: Interested, Not Interested, Spam, Other.

Use Other when the intent cannot be confidently categorised.

​Example: start an automation when an incoming SMS is classified as Interested, creating immediate follow-up actions for the assigned team member.

Triggers based on the AI-detected intent of an incoming call, determined from the call transcript. Same four intents.

Triggers on direct mail campaign activity. Conditions: Delivered, QR Code Scanned, Not Delivered.

​Example: trigger an automation when a recipient scans the QR code on a mail piece.

Triggers when a selected outgoing call outcome is recorded. Outcomes are customizable in your account, so automations can be built around the outcomes your team actually uses.

​Example: if you have an outcome called Follow Up Later, start a follow-up automation whenever it is selected.
​

Triggers on the delivery status of an outgoing SMS. Conditions: Delivered, Not Delivered.

Triggers on the outcome of an appointment. Outcomes: Kept, Not Kept.

Example: begin a follow-up sequence when a seller appointment is marked Not Kept.

Incoming SMS and Incoming Call use AI to detect intent, and this is a paid feature after your trial.

Without an active Full AI Team subscription, automations using these two triggers stop firing. The other four activity triggers are unaffected.

Conditions specific to the record type. For example:

See the module articles for the full list in each area.

Manual Assignment automations do not start on their own. A user assigns the record.

Available for List Stacking records, Leads, Transactions, Inventory, Sold, Rentals, Buyers, Agents, and Vendors. Records can be assigned individually or through supported bulk actions.

Only Manual Assignment automations can be used for bulk assignment. Trigger-based automations cannot be selected.

A maximum of 100 records per day can be added to automations this way, across your entire account. It is not 100 per module.

​Example: 40 List Stacking records + 30 Leads + 20 Buyers + 10 Vendors = the 100-record limit reached.

When you activate an automation, REsimpli starts listening for qualifying events from that point on. Records that already met the condition are not enrolled.

​Example: you create an automation with the trigger Tag = Hot Lead. Fifty existing leads already have that tag. None of them enter the automation. The tag has to be added again, after the automation is active.

A lead could simultaneously be in a Status Change automation, an Activity Trigger automation, and a Manual Assignment automation. Entering one does not prevent it entering another.

It can, but the trigger has to occur again.
​

Example: an automation triggers when the tag Hot Lead is added. The tag is added, the lead enters, the tag is removed, the tag is added again — the automation can trigger again.

Once a record has entered, changing the thing that triggered it does not pull it back out. The automation keeps running.

​Example: a Buyer automation starts when Target State = Florida. Florida is later removed from that buyer's target locations. The buyer stays in the automation and continues through the steps.

These look similar and are not.

Inventory example: a property is added directly into Under Rehab. New Inventory Added fires. Status Change to Under Rehab does not — that was its initial status. When it later moves to Ready for Sale, Status Change fires.

​Transactions are the exception. 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 enters.

An automation can perform an action that changes a record's status, and that change can meet another automation's trigger condition.

​Example: Automation A moves a lead to Follow Up. Automation B triggers on leads moving to Follow Up. B begins automatically.

Because records can be in several automations at once, these workflows do not operate in isolation. Review connected automations before activating.

Where the option is available, an automation can stop other automations as part of its workflow — any number of them, including all. This lets a new workflow replace ones no longer appropriate for that record.

Steps can be scheduled using delays or specific days.
​

When weekend and holiday handling is enabled:

When it is not enabled, the automation follows the configured dates without adjustment.
​

REsimpli validates step timing so steps cannot be scheduled out of order — a step must be no earlier than the one before it, and a chosen date and time must be the same as or before the next step.

Target County, Target City, Target State, and Target ZIP are available on Buyer, Agent, and Vendor automations.

The trigger fires when a target location is added or updated and matches your condition. Existing target locations do not enrol a contact — a new qualifying event must occur after activation.

Last Offer Amount, Under Contract Price, Expected Profit Changed, Actual Profit, Sold Price, and Expected Profit vs Actual Profit are all evaluated when the value is updated. REsimpli then checks whether the new value satisfies your condition.

Several New Record automations let you choose which marketing campaigns trigger them — one campaign, several, or all. This is how you give different marketing sources different workflows.

Use trigger-based automations when REsimpli should start the workflow automatically — a new lead is created, a lead changes status, a seller responds Interested, a buyer target state is added, a transaction receives a second dispo offer.

​Use Manual Assignment when a person should decide which records go in — a selected group of List Stacking records for a special campaign, specific leads into a nurture sequence, chosen buyers into a communication workflow.

Only Manual Assignment automations can be bulk assigned.

Can the same record be in multiple automations at once? Yes.

​Can the same record enter the same automation again? Yes, if a new qualifying trigger event occurs.

​Will activating an automation enrol records that already meet its conditions? No. Automations respond to future events only.

​What happens if a record stops matching the trigger after it enters? It continues through the automation. Removing the condition does not remove the record.

​Can I pause an automation? There is currently no Pause option.

​Can one automation trigger another? Yes — if it performs an action, such as a status change, that meets another automation's trigger condition.

​Can a bulk status change trigger an automation? No.

​Can importing records trigger a Status Change automation? No.

​Can changing status through the Open API or Zapier trigger an automation? Status changes are not currently available through the Open API or Zapier.

​Can I bulk-add records to any automation? No. Only Manual Assignment automations.

​How many records can I bulk-add? Up to 100 per day, shared across the whole platform.

​Do AI intent triggers cost extra? They are included during your trial — 14 days for new accounts, 30 days after upgrading to 6.0 for existing ones. After that, Incoming SMS and Incoming Call intent triggers require a Full AI Team subscription.

​What happens to those automations when my trial ends? Without a Full AI Team subscription, automations using those two triggers stop firing.

An automation's trigger decides when a record enters it. REsimpli offers New Record, Status Change, Activity, Other, and Manual Assignment triggers, with availability depending on the module.
​

Enrollment is forward-looking: automations respond to events after activation, records can sit in several automations at once, can re-enter when a trigger recurs, and stay enrolled even if the original condition changes.