Steps
Steps do the work of an automation. Learn the step types, the actions, and how to put a contact's or deal's details in your text.
Step types
| Step | What it does |
|---|---|
| Action | Does one thing, for example adds a tag or sends an email |
| If/else | Checks a condition, then takes the Yes path or the No path |
| Wait | Waits for a time, for example 3 days |
| Wait until | Waits until a condition is true. After a time limit, it takes the other path. |
| Split test | Sends some contacts or deals on path A and the rest on path B |
| Goal | When the goal is met, anyone still before it jumps to it |
| Go to | Jumps to another step, even an earlier one |
| End | Ends the automation for this contact or deal |
Each contact or deal can go through up to 1,000 steps. This stops an endless loop.
Add a step
Select + where the step goes. The list shows the steps that fit what the automation works on. The start triggers decide this. Read Triggers.
Actions
| Action | Works on |
|---|---|
| Set a field | Contacts, deals |
| Add to a number | Contacts, deals |
| Add a tag, Remove a tag | Contacts, deals. In a deal automation, the deal, its primary contact or a person in a role on the deal. |
| Assign an owner | Contacts, deals |
| Move to a stage | Deals. In a contact automation, their most recent deal. |
| Mark won or lost | Deals. In a contact automation, their most recent deal. |
| Create a deal | Contacts |
| Create a task | All |
| Add a note | Contacts, deals |
| Add to a list, Remove from a list | Contacts |
| Send an email | Contacts. In a deal automation, the primary contact. |
| Send a text | Contacts. Read Texting. |
| Prepare a saved response | Contacts. Makes an email for the agent to edit and approve. |
| Send a message | Contacts, deals. A dated email from the owner or coordinator. Use your own words or a saved response. Read Messages. |
| Notify the team | All. The email goes to your team, never to the contact. |
| Send a webhook | All. Sends data to another app. Some automations can use the RESO format. See Send a webhook. |
| Start an automation, Stop automations | Contacts, deals |
| Run a connected app | All |
| Ask the Assistant | All. Read Assistant steps. |
| Create a CMA | Contacts, deals. Starts a CMA of the client's home for the contact's or deal's owner. The home is their latest closed purchase, or else their mailing address. One per client each year. A task made in a later step links to the CMA and the home. A later Send a message step can use the CMA's price range and the client's link to it. It needs an MLS that allows CMAs. Until then, Berchtold skips the step. It also skips a home that is listed, or sold in the last 12 months. Read CMA presentations. |
| Send a Handwrytten card | Contacts, deals. Mails a handwritten card through your Handwrytten account. Choose the card, the handwriting, the return address, the message and the sign-off. You can put a gift card in the card. Approve paid sending before you publish. Read Choose the card. |
Create a task
A task step makes a task. Set its title, due day, priority and assignee. You can also add:
- Description: what to do. It can include details of the contact or deal.
- Tags: words that group tasks. A Task is done trigger can start on a tag.
- Done when: a fact about the workspace, such as Google Analytics is connected. The task is done on its own when this becomes true. People can still mark it done.
If no one has the assignee's role, such as the deal owner, the task goes to the default person. If there is no default person, the task waits and shows Needs: Deal owner. See Choose default people.
On a deal, a task can also have work that Berchtold does. Choose it in What Berchtold does, for example Introduction emails. Berchtold then does that work on the task, and the task's person sends the email. To give it to the deal's coordinator, choose The deal's coordinator (or the owner if there is none). See Built-in work on deal tasks.
Choose the card
A Send a Handwrytten card step shows the chosen card's front, name and price. Select it to choose a card.
- Your custom cards come first. These are the designs you made in Handwrytten (My Custom Cards there).
- Then come Handwrytten's cards, by category, such as Birthday and Thank You. Each category shows its first cards. Select See all to show the rest, or choose a category in the list.
- Type in the search box to find a card by its name.
- Each card shows its front, its name and its base price. The chosen card says Chosen.
- With a keyboard, use the arrow keys to move between cards. Press Enter to choose one.
A card you made in Handwrytten shows here within about five minutes. The base price does not include postage, tax or other fees. When you choose another card, approve paid sending again before you publish.
Put a gift card in the card
Under Gift card, choose a gift card and its amount, such as a $20 Starbucks gift card. Each amount shows what Handwrytten charges for it. Choose No gift card to send the card alone.
If the gift card's price goes up after you publish, the step stops before it orders. Review the step and publish it again. When Handwrytten no longer offers the gift card, choose another one.
The Assistant and connected AI tools can find your cards and gift cards too. Ask, for example, "Find my custom Handwrytten cards."
Send a webhook
A webhook step sends data to a web address that you choose. Use it to send contacts or other details to another app, such as a partner's. This section is for the developer who sets up that app.
- Address: a public web address that starts with
https://. - Format: Standard or RESO. Read about each one below.
- Body (optional): with Standard, you can write your own JSON. It can include values such as
{{contact.email}}.
Standard and RESO
| Format | What it sends | Automations that can use it |
|---|---|---|
| Standard | Berchtold's JSON. It has the automation, the run, the contact or deal, the trigger's data and the results of earlier steps. Or it sends the body you write. | All |
| RESO | One record in RESO Common Format (Data Dictionary 2.0), with @reso.context. A contact automation sends the contact. A workspace automation sends the member who joined. | Contact automations. Workspace automations whose only trigger is A member joins. |
RESO is the standard data format of the real estate industry. A RESO webhook sends one contact, or the new member.
Deals have no RESO format, so deal automations use Standard. Other workspace automations aren't about one contact, so they use Standard too. In those automations, RESO is off, and the step says why.
With RESO, Berchtold writes the body, so you can't write your own. RESO never sends MLS listings or personal data, such as marital status.
Berchtold checks the data against RESO's rules before it sends it. If the data fails the checks, Berchtold doesn't send it, and the step fails. The automation's History shows the reason.
If you change the start triggers, a RESO step may no longer fit. It then shows under Before you publish. Choose Standard, or change the triggers back.
Headers that prove a request came from Berchtold
| Header | What it holds |
|---|---|
X-Berchtold-Signature | t=…,v1=…. v1 is an HMAC-SHA256, in hex, of {t}.{body}: the time, a full stop and the raw body. |
X-Berchtold-Timestamp | The same time as t, in Unix seconds. |
X-Berchtold-Delivery | The ID of the delivery. A retry has the same ID, so your receiver can drop a repeat. |
Your app works out the signature again and compares it with v1. Refuse a request with an old time.
Retries and the delivery log
When the address does not answer, or it answers with a server error or 429, Berchtold tries again. It tries a few times, with a longer wait each time. Then the step fails. Other answers, such as 400 or 404, fail the step at once. Retries are always on.
The delivery log keeps each recent delivery for 30 days. It shows the address's host, the format, the status, the number of tries and the last answer. A workspace admin can ask a connected AI tool, such as Claude, to show the delivery log. See Connect Claude, ChatGPT or Muse to Berchtold.
Steps for the deal's people or the contact's deal
A deal automation can work on the deal's primary contact. The picker shows these steps with "(primary contact)".
A deal automation can also work on a person in a role on the deal, such as the referrer. Under Runs on, choose A person in a role on the deal, then choose the role. A deal with no one in the role skips the step and goes on. The template Thank the referrer when the deal closes uses this. It tags the referrer at once. When the deal closes, it mails them your Handwrytten card, with a gift card if you chose one. A referrer added to a deal that closed more than 30 days ago gets the tag but no card.
A contact automation can work on the contact's most recent open deal. The picker shows these steps with "(their most recent deal)". A contact with no open deal skips the step and goes on.
Some steps fit both contacts and deals. Examples are Set a field, Add a tag, Create a task and Add a note. Open the step and choose which one under Runs on.
Tag the deal or its people
Deals and contacts use the same tags. In a deal automation, Add a tag and Remove a tag work on the deal itself. The step says "to the deal", for example Add tag “Relocation” to the deal.
To tag a person on the deal, open the step. Under Runs on, choose The deal's primary contact or A person in a role on the deal. In a contact automation, choose Their most recent open deal to tag the contact's deal. See Find deals by tag.
When the start triggers change
A new start trigger can change what the automation works on. For example, you add a deal trigger to an automation with contact steps. The steps stay. The steps that do not fit show Needs a fix and go on the list Before you publish. Change them or delete them.
Put details in your text
A task title, a note or an email to the team can include details of the contact, the deal or the automation. Type the field name in double braces:
{{contact.first_name}}for the first name of the contact.{{deal.title}}for the title of the deal.{{agent.name}}for the owner of the contact or deal.{{trigger.answers.message}}for an answer from a form.{{steps.summary_step.summary}}for the result of an Assistant step.
Add text to use when the field is empty: {{contact.first_name|there}}.
Email and consent
An email step sends a published email template. It goes only to people who may get email from the list you choose. A person who unsubscribes from all email can leave the automation. You choose this in the automation's settings.
Prepare a saved response makes a personal email from the subject and message you write. It fills in the contact's and property's details. Then it waits for the contact's agent. They find it in Approvals and in the contact's Messages, where they can edit it.
Every email waits until the agent selects Send. If they select Don't send, or decide nothing for seven days, the email does not go. The contact's email settings still apply when the agent sends it.