Sales
Every Sunday Aestus lists the open HubSpot deals with no activity for 60 days and asks one question: close these as lost?
One question on Sunday
Coming soonWeekly pipeline cleanup is built, but not ready yet, so it cannot be turned on today. In Aestus you can ask to be told when it is ready.
A pipeline fills up with deals nobody is working. The call that never came back, the pilot that went quiet, the renewal someone meant to chase. They stay open, and the forecast keeps counting them.
This asks about them once a week. On Sunday it reads your open HubSpot deals and lists the ones with no logged activity for 60 days and nothing scheduled next. On Monday you see one question: close these as lost? Each row has the deal, its amount and how long it has been idle.
You decide. Close them all, pick which, or skip this week. Nothing changes in HubSpot before you answer, and each deal is read again just before it is written, so a deal somebody picked up in the meantime stays open.
It changes two things on a deal, the stage and the lost reason. It cannot create, archive, delete or merge a record, because those tools are not in the session. And every week leaves one ticket with what was closed and what was left open, so the answer to "who closed that deal" is written down.
The artifact this use case produces, in the product view you would read it in.
Worked example
Not published yet
This workflow is not seeded yet, so there is no real output to show. We would rather leave this empty than print one we made up.
Each step is one node in the workflow graph the interpreter runs. Nothing here is a prompt chain hidden in a route handler.
Workflow steps
A step that can only read lists your open deals and each pipeline's stages. A deal is stale when nobody has logged activity on it for 60 days (you choose the number) and no next activity is scheduled.
Every deal has to have come back from a read this run made, and every date has to be the one HubSpot returned. A list that fails is retried once; a second failure ends the run with nothing written.
Close these deals as lost? Each row shows the deal, its amount and how many days it has been idle. The run waits for you, keeps its place, and costs nothing while it waits.
Close writes the deals you picked. Skip this week writes nothing and ends the run; next Sunday asks again.
A deal somebody worked since the list was made is skipped and reported, never closed. The rest move to their pipeline's closed-lost stage with the lost reason you set.
The same job, on either side.
By hand
Someone scrolls the pipeline on Monday and guesses which deals are dead.
On Aestus
The list is built from each deal's last logged activity, with the date on every row.
By hand
Dead deals stay open, and the forecast counts them.
On Aestus
Once a week you are asked about them, and one tap closes the ones you pick.
By hand
A deal gets closed the morning a rep finally calls back.
On Aestus
Each deal is read again just before it is written, and a deal with new activity is left open.
By hand
A bulk edit touches fields nobody meant to change.
On Aestus
It changes two properties on a deal, the stage and the lost reason, and nothing else.
By hand
Nobody remembers who closed what, or why.
On Aestus
Every week leaves one ticket with the list, what was closed, and what was left open and why.
Every run is auditable after the fact, which is what makes handing the job over survivable.
One ticket per week with the list you were shown, the deals that were closed, and the ones left open with the reason.
Tokens, time, cost and a classified failure code when something breaks, on the same ledger as every other run in the workspace.
The reviewing model's pass or fail reason for each attempt, stored with the run.
Only the tools this workflow actually uses. Each one has a setup guide.
No. The step that can change a deal is reachable only through your answer, and that answer carries the customer-record permission the runtime checks for. An automation whose changing step has no approval in front of it cannot be saved.
An open deal with no logged activity for at least the number of days you set (60 by default) and no next activity scheduled. A deal that never had activity counts from the day it was created.
No. The reviewed HubSpot tool list has no create, archive, delete or merge tool. It moves a deal to its pipeline's closed-lost stage and writes the lost reason, and that is all.
The run waits for you with its list. You answer when you are back, and each deal is read again before anything is written.
Sources