Skip to content

Insights · FRED

When HubSpot changes, the next task can begin.

AI illustration: A contact card, case folder and message connect to a central data hub.
AI illustration
Published

In short · 2 min read

  • How our event integration receives HubSpot changes, retrieves context and prepares the next stage of AI-assisted work.
  • Developed with AI and clear responsibilities.

Nobody should have to keep pressing refresh

A message arrives. A ticket changes state. If the next step starts only after someone copies the information, automation stops halfway.

We connected HubSpot events to FRED. An event signals that something has changed. The implemented workflow retrieves the related context and updates the information used for subsequent handling.

The notification is only the beginning

An event is not the entire customer record. Retrieval and association turn it into a useful basis for work.

Illustrative example: a new message adds information to an existing ticket. The system receives the change and takes the updated case into account. This describes the function, not an actual incoming message.

AI illustration: Two colleagues review the connection between a contact, a message and a case.
AI illustration: Two colleagues review the connection between a contact, a message and a case. Fictional illustrative scene, not a customer screenshot.

From event to current context

Step Purpose
Receive an event Detect a relevant change
Retrieve the context Understand the related case
Update information Give subsequent work the new position
Check the next action Perform only the permitted step

Receiving an event does not authorise sending a reply. A new response can supersede an earlier draft, so handling must account for the current state.

AI illustration: Two document versions are checked side by side, with a passage highlighted.
AI illustration: Two document versions are checked side by side, with a passage highlighted. Fictional illustrative scene, not a customer screenshot.

What we developed

AI contributed to linking event intake, retrieval and handling. Our implementation separates these steps so that a technical notification is not mistaken for a completed case.

The HubSpot integration overview explains the information involved. This article focuses on the trigger: how does the change reach AI in the first place? Enabled events and permitted actions depend on the particular setup.

Which change should start the next task in your organisation?

Sources.

  1. SolvraONE: own development and technical source reviewOwn source · As of
  2. HubSpot: webhook eventsVendor / primary · As of