SALES
Generate an objection-handling Loom script from demo notes after stage change
When a HubSpot deal advances past demo, an agent reads the demo notes, identifies the buyer's specific objections, drafts a tailored Loom talking-points script.
How it runs
The automated pipeline, trigger to output.
- TriggerHubSpot deal advances past demo stageHubSpot
- ActionFetch deal, notes, and transcriptHubSpot
- ActionAgent extracts objections and drafts Loom scriptOpenAI
- LogicRoute standard recap vs objection-handling path
- ActionCreate Loom seeded with agent scriptLoom
- OutputEmail video to buyer and log script to dealGmail
What it does
This agent-driven workflow does the thinking before the rep hits record. When a deal advances past the demo stage in HubSpot, an AI agent reads the demo notes and call transcript, isolates the buyer's actual objections and buying signals, and writes a tailored Loom script that addresses each concern in order — so the follow-up video directly answers what's blocking the deal.
When to use it
Use it when reps record generic recaps that ignore the real friction surfaced in the demo. This ensures every follow-up Loom is built around the specific objections that matter to that buyer.
How it works
- 1A HubSpot deal stage change past demo fires the trigger.
- 2The flow fetches the deal, contact, demo notes, and any transcript from HubSpot.
- 3An agent analyzes the notes to extract objections, priorities, and a recommended framing.
- 4A logic step routes deals with no clear objections to a standard recap path versus a custom objection-handling path.
- 5It creates a Loom recording seeded with the agent's script, then Gmail sends the buyer the finished video and logs the script to the deal.
Set it up
What you configure once, before turning it on.
- 1Connect HubSpotCRM, deals, marketing, support.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LoomVideo transcripts, libraries.
- 4Connect GmailRead, draft, send, label.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Sales workflows
API-Usage Surge PQL Router
When an account's API call volume surges past a rolling baseline in the product DB, it qualifies the account as a product-qualified expansion lead.
Seat-Limit Approaching Upsell Alert
Fires the moment an account's active-seat count crosses 90% of its contracted limit in the product database.
Enrich new MAP steps with Salesforce deal context on creation
When a new card is added to the mutual action plan Trello board, it looks up the linked Salesforce opportunity and writes deal owner, amount, and close date onto the card…
Power-Feature Adoption Expansion Digest
Each Monday, finds accounts that started heavily using a premium or add-on feature in BigQuery, ranks them by expansion potential.
Send buyers a weekly mutual action plan health recap
Each week it reads the MAP Trello board, computes completed, on-track, and overdue steps, and emails the buyer champion a clean recap of progress and what is due next.
Escalate to the deal team when the buyer side of a MAP stalls
Detects when buyer-owned mutual action plan steps have been idle past their due date and escalates with a Slack alert to the AE plus an email summary to the account executive's…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.