Skip to content

Querying HubSpot

Daeda AI lets your AI app investigate the HubSpot data you selected during portal connection. Ask in plain English, include the portal and time period, and request the fields or evidence you need to verify the answer.

  • Which deals moved backwards or had their close date changed this month?
  • Which workflows update this property?
  • Why did this contact’s lifecycle stage change?
  • Which active workflows have no recent enrolments?
  • Which owners have the oldest open deals?
  • What does this workflow do in plain English?
  • Which forms, lists, or reports depend on this property?

The available answers depend on the data categories selected for the connected portal and whether that data is ready.

Include four things:

  1. Portal: name the customer or HubSpot portal.
  2. Question: state the business question rather than only asking for a data export.
  3. Scope: include a date range, pipeline, team, owner, or other useful boundary.
  4. Evidence: ask for the records and fields used in the answer.

Example:

In the Demo portal, identify deals whose close date moved by more than 30 days during the last calendar month. Show deal name, owner, stage, previous close date, current close date, and the date of the change. Do not make any changes.

Before acting on an answer, confirm:

  • The assistant used the intended portal.
  • The date range and filters match your question.
  • The relevant HubSpot data is READY rather than still building.
  • The answer distinguishes facts from interpretation.
  • Important claims include the underlying records or configuration.

For high-impact decisions, open a sample of the reported records or assets in HubSpot.

Daeda AI prepares a controlled, queryable copy of the HubSpot data you selected. This is called the portal mirror. It allows the assistant to investigate larger questions without repeatedly retrieving every record from HubSpot.

The connected portal card shows whether the mirror is building, ready, partial, or failed. Active data is refreshed automatically, and the assistant can request a refresh when a question needs newer information.

Some less common information is retrieved only when it is needed. You can normally describe the business question and let the assistant choose the appropriate read-only method.

Anything included in the portal mirror can be used in an answer and may be sent to the AI provider connected to your workspace. Choose data categories and filters deliberately during portal setup.

Use Security And Data Handling for the customer-facing summary. Administrators and security reviewers can read Portal Mirror Construction for the underlying refresh and storage architecture.

The optional Daeda Bridge adds HubSpot information that is not available through the normal API, such as certain configuration and sales assets. If the Bridge is disconnected, Daeda AI skips those Bridge-only data sources instead of retrieving them another way.

After a successful investigation, you can ask the AI app to prepare a reviewed HubSpot change. Continue to Requesting Good Plans or Review And Execute Write Plans.