What Eru reads from HubSpot

Eru connects to HubSpot via OAuth and uses the CRM API to read your data. It discovers your specific configuration—custom properties, deal stages, lifecycle stages—rather than assuming a generic setup.

Companies

Company records with all standard and custom properties. Domain, industry, employee count, owner, lifecycle stage, and any custom fields you've added. Eru maps companies to customer entities in your other systems.

Contacts

Contact records associated with companies. Email, name, job title, and engagement data. Eru uses contacts to identify champions and key stakeholders within customer accounts.

Deals

Pipeline deals with stage, amount, close date, and associated contacts/companies. Eru maps deals to revenue in billing systems and tracks pipeline health against actual closed business.

Activities

Emails, calls, meetings, and notes logged against contacts and companies. Eru uses activity data to assess engagement levels and identify accounts going quiet.

Custom objects

If you've created custom objects in HubSpot, Eru discovers and maps them. Subscriptions, projects, tickets—whatever you're tracking gets included in the unified view.

How Eru maps HubSpot data

Eru doesn't assume your HubSpot matches a template. It learns your specific setup.

Entity mapping

When connected, Eru explores your HubSpot schema and samples data. It identifies which HubSpot objects correspond to which business entities. Your "Companies" might map to "Customers" or "Accounts" or "Organizations"—depending on how you use HubSpot and what your other systems call them.

Property discovery

Eru catalogs all properties—standard and custom—and infers their meaning. It notices that your custom "arr_amount" property tracks annual revenue, or that "csm_owner" identifies the customer success manager. These become part of the Truth Map.

Relationship inference

Eru maps how HubSpot entities relate to entities in other systems. It finds that HubSpot company domains match Stripe customer emails match database account identifiers. Cross-system relationships are documented with confidence scores.

Common use cases

CRM + Billing reconciliation

Compare deal amounts in HubSpot to actual revenue in Stripe. Catch discrepancies between what sales recorded and what customers actually pay.

Engagement tracking

Combine HubSpot activity data with product usage. Identify accounts where CRM engagement is high but product usage is declining—or vice versa.

Pipeline health

Cross-reference deals with support tickets and usage data. Surface deals where the prospect is having product issues that might derail the sale.

Customer 360

Build a complete view of each customer: CRM data, billing history, support interactions, product usage. All linked and queryable.

Setup

1. Connect via OAuth

Eru uses HubSpot's OAuth flow. You authorize read access to your CRM data. Credentials are stored encrypted and never sent to the AI.

2. Eru explores your schema

The agent scans your HubSpot configuration: objects, properties, pipelines, lifecycle stages. It samples data to understand patterns and relationships.

3. Review proposed mappings

Eru proposes how HubSpot entities map to your other systems. You review and approve. Mappings are versioned with full audit trail.

4. Continuous sync

Once mapped, Eru monitors for changes. New properties, schema updates, data drift—all tracked and surfaced when relevant.

Permissions required

Eru requests read-only access to:

Eru never writes to HubSpot. It reads data for analysis and mapping only.

Other integrations

Connect HubSpot to Eru

See how your CRM data maps to the rest of your stack.