Updated
Go to Automations in the sidebar and select New Automation.
Theo builds an automation from a plain English description. You chat with Theo on the left of the screen while the automation appears on a canvas on the right, with its trigger and every step joined up. Theo can also change an automation you already have.
AI is only used while you build. Theo never adds an AI step, so a saved automation runs its normal steps and uses no AI credits when it runs. Nothing is saved until you select Save, so you can try ideas freely.
Before you start
- You need the Manage Automations permission, or Manage Own Automations for automations that run on your own deals. If you can't open New Automation, ask an admin to grant one under Settings > Roles & Permissions.
- Build with Theo may not be turned on for your workspace yet. If you don't see Build with Theo on Create Automation, it isn't available to you yet.
- Each message you send Theo uses AI credits from your workspace's monthly pool. See Using the Lend1 AI copilot.
- A new automation counts towards your plan's automation limit. At the limit, Theo won't start a new automation and Continue your Theo draft is hidden. You can still change automations you already have.
- Build with Theo is hidden while you're signed in as another user. The one exception is changing an existing automation when you can manage every automation in your firm.
Build a new automation with Theo
Step 1: Open Build with Theo
- On Create Automation, select Build with Theo above Automation Details. If you chose an Owner on the form first, Theo starts with that choice.
- If you started a draft earlier, select Continue your Theo draft beside it to pick up where you left off.
Step 2: Describe the automation
- Under What should this automation do?, say what starts it and what should happen next. Type it into Describe the automation you want, or select a starter to fill the box so you can edit it before sending: Welcome email on a new deal, Text on each stage change, Ask for documents or Overdue task alert.
- Theo drafts the automation's name, trigger and steps, and the canvas shows them.
Step 3: Choose who it's for
- When you can build for other people, Who it's for sits under the buttons at the top. Pick from the list: Team automations run for everyone in your firm, and an automation for one broker runs only on that broker's deals.
- Changing it after Theo has drafted re-checks every step for the new choice. If a step doesn't fit, for example a stage that isn't on that broker's board, the change is refused with the reasons. Ask Theo to change the steps, or select Start over.
Step 4: Refine it in the chat
- Type a change in the Ask for a change box, for example "wait two days, not one" or "send it from the firm instead".
- Each reply comes with a card listing what changed: the trigger, and each step marked Added, Changed or Removed.
- When a reply ends with a Theo assumed list, open it and select Change this beside an assumption to start a message that corrects it.
Change an existing automation with Theo
- Open the automation and select Build with Theo in the toolbar at the top. Any unsaved changes on the canvas are saved first, so Theo starts from what you see.
- Under What would you like to change?, ask for the change in the chat, exactly as for a new automation. Theo changes only what you ask for and leaves every other step and its wording as it is.
- Theo can also change what starts the automation, which the normal builder can't.
- If you have an open Theo chat for this automation, you go back to it. When the automation was changed since, the draft is brought up to date with the saved automation first.
Look at the draft on the canvas
The canvas on the right is read only. The banner at the top says Read only. Save to edit the steps by hand. You can't drag, join or delete steps there, and you can't change a step's settings.
- Select any step, or the Trigger, to open its settings in the panel on the right and check what Theo set. The fields are shown but can't be changed.
- To change a step, ask Theo in the chat. Name the step and what you want, for example "change the reminder email's subject to Your documents".
- To make a change by hand, select Save. The automation opens in the normal builder, where you edit it as usual. Select Build with Theo in the toolbar to carry on with Theo afterwards: it picks up your hand edits.
On a phone, switch between Chat and Automation at the top of the screen.
Test it before you save
Select Test at the top of the screen. Dry Run Results lists each step and flags any marked Skipped or Would fail. A dry run sends nothing: "Nothing was sent or changed. Merge fields appear blank because a dry run has no deal attached."
Test results stay on your screen. They aren't added to the chat or sent to Theo, so describe any problem to Theo in your own words.
Undo or start over
- Undo steps back one change at a time.
- Start over clears the chat. For a new automation it clears the draft too. For an existing automation it takes the draft back to the automation as it is saved. Your saved automations aren't changed until you save.
Save the automation
- Select Save. A new automation is saved switched off, as a Draft, and opens in the builder. Theo never turns an automation on: check it, then select Activate when you're ready.
- Saving changes to an automation that is switched on asks Save changes to a live automation? first. Select Save changes and your changes apply from its next run.
- Saving changes never renames the automation, switches it on or off, or changes who it's for. Change those in the builder.
- If the automation was changed somewhere else while you worked with Theo, the screen says This automation changed since Theo loaded it. Select Reload to bring the draft up to date with the saved automation, then save again. Nothing is overwritten. Undo can still take you back to Theo's last draft.
- If Save can't go ahead, a banner reads This automation can't be saved yet: and lists every reason. Ask Theo to fix them.
Congratulations! Your automation is built, tested and saved, ready to switch on.
What Theo can and can't do
Theo builds from the same triggers and steps as the normal builder, with a few exceptions.
- Triggers: every trigger on Create Automation except Webhook.
- Steps: every step in the Node Palette except API Call, Sync Integration and AI Action. Theo never adds those three.
- Recipients: Theo picks who an email or text goes to from fixed choices: the client, the deal's broker, the people in a role on the deal, or a team member. A notification goes to the assigned user, all admins or team members you name. Theo never types an email address or phone number. If you give it one, it uses the closest choice and tells you to add the address or number by hand in the builder.
- Client details: an Update Contact step from Theo never changes the client's email, phone or name.
- Steps set up by hand: a step Theo can't set up itself is kept exactly as it is, and Theo tells you so if you ask it to change one. That includes an API Call, an AI Action, an email or text to an address or number typed in by hand, and any setting Theo doesn't offer. Change those in the normal builder.
- Not yet: no step can read documents, summarise a deal, make a decision with AI each time it runs, or call another system. When you ask for one of these, Theo tells you it can't build it, builds the parts that still work on their own, and lists what it left out.
AI credits and when AI is off
- The meter at the top right shows how much of this month's AI credits your workspace has used. When credits run low, a notice above the chat says how much is used.
- When credits run out, the message box is replaced with "Your AI credits for this month have run out." You can still build the automation by hand, and anyone who manages billing sees Go to Billing. Saving and testing the current draft don't use credits.
- If AI is switched off for your firm, the message box is greyed out with "AI is switched off for your firm, so Theo can't build automations right now. You can still build one by hand."
Tips for good results
- Say what starts it. Name the trigger: a new deal, a stage change, a document uploaded, an overdue task.
- Say who it's for. The client, the deal's broker, the people in a role, or a named team member.
- Be specific about timing and stages. "Three days after", "only when the deal moves to Settlement".
- Ask for one change at a time once the draft is close. Each change gets its own card and its own Undo.
- Test before you switch it on. Run Test, read Dry Run Results, then save and select Activate.
Requests that work well:
- "When a new deal is created, email the client a welcome from their broker saying what happens next."
- "Text the client each time their deal moves to a new stage, saying which stage it is at now."
- "When a deal is created, request the client's documents, then email a reminder 3 days later."
- "Text the broker when one of their tasks becomes overdue."