Renewal Radar adds approved Agent Tools for HubSpot renewal workflows

From product direction to approved tools

Sighub has confirmed that HubSpot has approved Renewal Radar’s four Agent Tools. The company’s new Agent Tools page describes support for account prioritisation, company-level risk explanations, alert snoozing and recording renewal outcomes. The approval is a concrete development from the decision-layer direction DailyRevOps covered earlier in September: customers with the required access can now add the tools from the existing Renewal Radar app to a HubSpot agent.

The integration connects conversational agent requests to Renewal Radar’s existing decision process. A user can ask which accounts need attention, inspect the evidence for one company and, when appropriate, request a supported action. Sighub confirmed the approval to DailyRevOps on 10 September 2026. Its public product page and setup documentation also identify the four tools as approved.

Sources: Renewal Radar Agent Tools announcement and overview

What the decision layer supplies

Renewal Radar applies deterministic rules to supported HubSpot evidence and returns a decision with the information behind it. Sighub describes the division of work as business logic in Renewal Radar and conversation in the agent. With the same evidence and rule version, the underlying decision should remain consistent; the agent’s explanation may use different wording. That makes the returned evidence, timing source and confidence useful parts of the answer.

An agent lookup reads an existing decision. It does not trigger a complete live scan of the CRM, and Sighub’s setup guide says Team scans run approximately daily. For a RevOps operator, this means the answer has a data-freshness boundary. If an account changed after the last scan, the team should reconcile the returned decision with that change before relying on it for a consequential action.

Sources: Sighub setup documentation and scan behaviour

Two tools retrieve account decisions

List Renewal Radar at-risk renewals provides a portfolio view with severity, renewal timing, value at risk and ownership. Its default response contains ten results, with a maximum of 25 per call. A count larger than the returned list should therefore be treated as a sign that more accounts exist, rather than evidence that the agent has already reviewed the whole portfolio.

Get Renewal Radar company risk provides the detailed explanation for a single company. The documented output includes the decision, supporting evidence, timing source, confidence, next step, owner and existing follow-up task when available. Lookup accepts a HubSpot Company ID or a unique exact company name. Where names are ambiguous, the operationally useful response is to resolve the account identity before continuing. Missing dates or values should remain visible as missing information.

Sources: The four tools and their inputs

Two actions change the renewal workflow

Snooze Renewal Radar company risk pauses an existing alert for 14 days following an explicit request. An optional reason is retained within Renewal Radar. According to Sighub, snoozing leaves CRM properties unchanged and does not record a renewal outcome. An alert can return after the pause if it still meets the relevant conditions, so a snooze is a temporary workflow control.

Record a Renewal Radar outcome handles an explicitly confirmed renewed or churned result and completes the open follow-up task. A renewed outcome keeps the account healthy in Renewal Radar for 90 days; a churned outcome removes it from further renewal monitoring. These are meaningful changes to monitoring and task state. A meeting, reply or encouraging conversation should not be interpreted by the agent as confirmation of a commercial outcome.

Sources: Sighub’s documented action effects

How to connect the tools to an agent

Start with the existing Renewal Radar installation in the same HubSpot account where the agent will run. Sighub requires an active Team or Partner plan, monitoring enabled and a completed first scan. Its free scan does not include Agent Tools. HubSpot agent access, permissions, subscription requirements and credits apply separately, so an app subscription alone does not establish that every portal user can configure or run an agent.

In Sighub’s documented Agent Hub flow, open or create an agent, choose Add action and find Renewal Radar in the HubSpot tab. Attach the two read tools first, then add the snooze and outcome tools if those actions belong in the workflow. For accounts using Breeze Studio, the guide describes the Configure and Add tool route. Add the supplied usage instructions, test with a real Company ID and publish the agent once its responses are correct.

Sources: Step-by-step Renewal Radar setup · HubSpot agent builder requirements and publishing

A useful first test for a renewal team

A bounded starting point is an account-review assistant. Ask it to list accounts needing attention, then inspect one known company and compare the returned renewal date, evidence, owner and next step with Renewal Radar. Include a company with incomplete timing and a name that could match more than one record. These cases reveal whether the agent preserves uncertainty and account identity when the answer is less straightforward.

Test an action only on an account whose alert or outcome the team intends to change. Confirm the target Company ID, the explicit request and the resulting monitoring or task state. HubSpot’s developer guidance separately recommends testing both tool logic and agent behaviour, including input handling and tool selection. A read-only review assistant can retain only the two lookup tools if changing state is outside its purpose.

Sources: Renewal Radar first-result checks · HubSpot Agent Tools testing guidance

What the approval establishes

The announcement establishes approved support for these four documented functions. It gives HubSpot teams a way to bring Renewal Radar’s account decisions into an agent workflow while continuing to use the app’s existing interface and monitoring. HubSpot’s developer documentation still labels the broader Agent Tools capability beta, and account-level access remains an implementation consideration.

Approval alone does not establish lower churn, improved retention or a particular return on investment. Those outcomes require evidence from the team’s own operating process. The immediate question is more specific: does the agent retrieve the right company, preserve the evidence and uncertainty, and carry out only the supported action the user requested? The new product page and setup guide provide the starting point for evaluating that workflow.

Sources: Explore Renewal Radar’s HubSpot Agent Tools · Open the setup guide

Disclosure

DailyRevOps and Sighub share ownership. This report uses Sighub’s public documentation and direct confirmation of approval, with HubSpot documentation for platform context; it is not an independent performance review.