The CLI runs inside your AI assistant, which means Landbase becomes one capability among all the others you have connected there. That setup lets you move past building lists and into running a motion, with the agent searching, enriching, and then handing results straight to the tools where you work. This lesson shows how to connect those tools and chain the steps together into something that runs for you.
Build a list of in-market accounts, dedupe it against my CRM, and write the new ones backBecause the CLI runs inside your assistant, Landbase sits alongside the other tools you have already connected there. That lets you move past building one list at a time and into running a motion, where the agent searches, enriches, and passes results onward in a single flow.
Connect another tool, such as your CRM, so the agent can read from it and write to it directly alongside Landbase. With the tools in one place, the agent can compare a new list against what you already have and add only what is missing.
Several steps can be combined into one workflow that runs end to end, such as build a list, enrich it, dedupe it against your CRM, and write the result back. Rather than running each step by hand, you describe the sequence once.
Once the workflow is defined, hand it to the agent and let it carry out the steps in order. This is the shift from doing the work to directing it, where you set the goal and the agent executes the steps.
Automated work stays under your control through permissions and guardrails. You decide what the agent can read and write, and you can review what it did before you rely on the result. Start with read access and a review step, then widen control as you build trust.