What a start trigger does
A start trigger is what starts an automation, for example a form someone sends. An automation can have up to five start triggers. Any one of them starts it.
An automation can also have no start trigger. Then people add contacts to it by hand. Another automation can also start it, with the Start an automation step.
Who goes through
The start triggers decide what the automation works on. The builder shows it under the triggers:
- Each contact goes through on its own. The triggers are about contacts, for example a form or a tag.
- Each deal goes through on its own. The triggers are about deals, for example a stage or a deadline.
- Runs once each time it starts. The triggers are for the whole workspace, for example a schedule.
All the start triggers of one automation must be for the same thing. After the first trigger, the list shows only triggers of the same type. A line at the top of the list tells you why.
Every workspace has automations. Without the CRM, a workspace has only the workspace triggers: schedules, a person starts it, webhooks, new members and tasks.
To work on both contacts and deals, make two automations. A step in one can start the other.
An automation can have one schedule, or several date triggers, and one webhook trigger.
Add, change or remove a trigger
- Select Add a start trigger. Choose the trigger. Then set its options, for example the tag.
- Select a trigger to open it. Select Change the trigger to choose another one.
- Select Remove the trigger, or the X on the trigger.
Start settings
Select Start settings below the triggers. These settings are for all the start triggers:
- Start conditions make the triggers narrower, for example "only buyers". Use List subscription to start only contacts who are subscribed to one of the lists you choose.
- Run again sets if a contact or deal can go through again after it finishes.
- Tick May start from another automation's change to let a change made by another automation start it.
Contacts and lists
| Trigger | It starts when |
|---|---|
| A contact is created | Someone adds a new contact |
| A contact field changes | The field you choose gets a new value |
| A tag is added | The tag you choose is added |
| A tag is removed | The tag you choose is taken off |
| Status changes | A client's status changes: Lead, Active client or Past client. Their deals set it. |
| A role is added | A contact gets a role, such as Co-op agent or Loan officer. Choose a role, or a group such as Clients. |
| A role is removed | A role is taken off a contact |
| A contact gets a new owner | Someone gives the contact to another agent |
| Someone joins or leaves a list | A contact joins or leaves an email list |
| Consent changes | A contact gives or takes back consent |
| An account is linked to a contact | Someone links the contact to an account |
| An account is unlinked from a contact | Someone removes the link to an account |
| A contact's record health changes | The contact's health check changes |
Forms, email and your website
| Trigger | It starts when |
|---|---|
| A form is sent | Someone sends one of your forms, or the form you choose |
| A lead ad form is sent | Someone sends a Facebook or Instagram lead ad form: any form, one Page's, or one form. A new lead waits for Accept first |
| An email is opened | A contact opens an email from a campaign or an automation |
| A link in an email is clicked | A contact clicks a link. You can give part of the link's address. |
| An email bounces | An email from Berchtold can't reach a contact. You can choose a campaign or a template. |
| A contact replies to an email | The contact answers an earlier email |
| The website records an event | Your website sends an event, for example "Saved a home" |
| A known visitor views a page | A known visitor opens a page that matches the address |
| A known visitor clicks | A known visitor clicks a link or a button on your website. You can give the link, for example tel:* for phone numbers, and the click's name, for example cta_click. |
A form trigger passes the form's answers to the steps. A condition can check an answer, for example the price range.
Each email that bounces starts the automation once. A condition can check the bounce type: permanent is a hard bounce, and temporary is a soft bounce. After a hard bounce, Berchtold sends no more email to that address.
A reply starts the automation when Berchtold saves it on the contact:
- Your connected email saves the replies that the contact sends to your emails. To connect your email, open Settings › Integrations. Under Your connections, turn on Gmail on the Google card.
- A person can add a reply to the contact by hand. Log an incoming email with the outcome Replied.
Automatic replies, for example out-of-office emails, do not start it. Email from before you connected does not start it either.
Website visits start it only for people Berchtold knows. Read Connect your website.
Appointments and events
| Trigger | It starts when |
|---|---|
| An appointment is booked | Someone books an appointment with a contact, in Berchtold or in Calendly |
| An appointment is rescheduled | An appointment moves to a new date or time |
| An appointment is canceled | An appointment is canceled, in Berchtold or in Calendly |
| A guest says they are going | A contact answers Going to a campaign's invitation |
| A guest comes to an event | The host checks in a contact, or a visitor signs in at an open house |
An appointment trigger is for the contact the appointment is with. A condition can check the appointment type, for example "Listing appointment".
Calendly bookings from before you connected Calendly do not start it.
Deals and pipeline
| Trigger | It starts when |
|---|---|
| A deal is created | Someone adds a new deal |
| A deal field changes | The field you choose gets a new value. Under Starts when, choose The field gets a value it did not have to start only when the field was empty. A new deal that already has a value starts it too. |
| The deal moves to a stage | The deal moves to the stage you choose, or to any stage |
| The deal enters a phase | The deal moves to a stage with that phase, in any pipeline |
| The deal moves to another pipeline | Someone moves the deal to another pipeline |
| The deal is won, lost or opened again | The deal's status changes |
| A deal gets a new owner | Someone gives the deal to another agent |
| A contact is linked to a deal | Someone adds a contact to the deal |
| A contact is unlinked from a deal | Someone removes a contact from the deal |
| A party is added to a deal | Someone adds a party, for example a lender or an inspector |
| A party is removed from a deal | Someone removes a party from the deal |
| Contract deadlines are added | The deal gets its first contract deadlines |
| A deadline changes | A deadline is done, waived or missed, or its date moves |
| An account is linked to a deal | Someone links the deal to an account |
| An account is unlinked from a deal | Someone removes the link to an account |
| A deal's record health changes | The deal's health check changes, for example it needs review |
| Signature request sent | Someone sends documents for signature from the deal |
| Signatures completed | Everyone signed. The signed copy is saved to the deal. |
| Signature request declined | A signer declined to sign |
| Signature request voided | Someone canceled the request. Nobody can sign it now. |
Dates and schedules
| Trigger | It starts |
|---|---|
| A contact date comes | On a contact's date, such as a birthday or home anniversary, or some days before or after it. Once or every year. |
| A deal date comes | Some days before or after a deadline, the contract date or the close date |
| On a schedule, for each contact who matches | At a time you set, once or every few days |
| On a schedule, for each deal that matches | At a time you set, once or every few days |
| On a schedule, once | At a time you set. It runs once for the whole workspace each time. |
Team and tasks
| Trigger | It starts when |
|---|---|
| A member joins | A person accepts an invitation to the workspace |
| A task is done | A task with no contact or deal is done |
| A deal's task is done | A task on a deal is done |
| A contact's task is done | A task on a contact is done |
A task trigger can start only on the tasks that one automation made, or on the tasks with a tag. Use it to start the next tasks when one is done.
An automation never starts again from its own tasks. This stops it from going in a loop.
In a task step, Assign to can be The person who started the automation. This is the member who joined, or the person who did the task.
Webhooks and people
| Trigger | It starts when |
|---|---|
| A webhook arrives | Another app sends data to the automation's web address |
| A person adds deals | A person or another automation adds a deal to it |
| A person starts it, once | A person starts it. It runs once for the whole workspace. |
A webhook finds the contact by the email in the data, or adds a new contact. To start it without a contact, open the trigger and choose With no contact. You can do this only when it is the only trigger.
To make the key for the webhook, save the automation. Then open the trigger and select Create key. Copy the key right away. It shows only once.

