feat: refresh hubspot project

[aaronsteers]

Summary by CodeRabbit

• New Features

  • Introduced numerous new data transforms for HubSpot entities, including contacts, deals, email events, engagements, tickets, owners, teams, and roles.
  • Expanded schema coverage with new fields for feedback surveys, SMS metadata, engagement properties, and pipeline details.
  • Added detailed documentation and mapping evaluations for schema transforms and data model alignment.

• Enhancements

  • Improved field mappings and confidence scores in existing transforms, increasing data accuracy and completeness.
  • Updated SQL models to provide more complete and accurate field selections.
  • Refined metadata, descriptions, and evaluation annotations for better transparency.

• Bug Fixes

  • Corrected field references and naming inconsistencies in several transforms and SQL models.

• Documentation

  • Added comprehensive README and mapping documentation, including accepted and rejected schema mappings.

• Chores

  • Updated configuration files and removed obsolete or redundant example and requirements files to streamline the project structure.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This update introduces a major overhaul and expansion of HubSpot data transformation and interoperability infrastructure. The changes migrate transformation logic, configuration, and schema mapping from a Fivetran-centric approach to an Airbyte-oriented domain. Numerous new YAML transform configurations are added for HubSpot entities, each mapping source fields to target schemas with detailed metadata and evaluation annotations. Many SQL models are introduced or updated to align with the new mappings, while documentation is significantly expanded with mapping confidence and rationale. Simultaneously, legacy Fivetran interop files, configurations, and example projects are removed. Schema definitions and requirements are updated to reflect new fields and improved structure, and .gitignore is updated to exclude dbt_packages.

Changes

Files/Paths (Grouped)	Change Summary
.gitignore	Added dbt_packages to ignore list.
build/hubspot/airbyte-catalog.json, build/hubspot/erd/source-schema-erd.dbml, build/hubspot/erd/target-schema-erd.dbml, build/hubspot/requirements/airbyte-interop/src_dbt_requirements.yml, build/hubspot/src_airbyte_raw_hubspot.yml	Schema and catalog expanded with new fields for feedback, SMS, engagement, pipelines, and more; stream renames and corrections applied.
catalog/hubspot/README.md, catalog/hubspot/rejected-mappings.md	Added comprehensive documentation on field mappings, confidence, and rejected mappings.
catalog/hubspot/airbyte-interop-dbt-project/models/*.sql	Added and updated numerous dbt SQL models for HubSpot entities to match new Airbyte-centric transforms.
catalog/hubspot/airbyte-interop-dbt-project/profiles/profiles.yml	Updated DuckDB profile path.
catalog/hubspot/examples/dbt_fivetran_compat/*	Removed legacy Fivetran compatibility example project, configs, and dependencies.
catalog/hubspot/requirements/fivetran-interop/src_dbt_requirements.dbml	Removed Fivetran schema requirements.
catalog/hubspot/src/fivetran-interop/*	Deleted Fivetran interop transforms and configuration files.
src/morph/utils/dbt/mapping_to_dbt_models.py	Updated autogenerated SQL comment to standard syntax and Airbyte branding.
src/transforms/hubspot/transforms/*.yml	Added and/or migrated a large set of YAML transform configurations for HubSpot entities to Airbyte-centric domain, with field mappings, descriptions, and evaluation metadata.
src/transforms/hubspot/transforms/* (new files)	Introduced new transform scaffolds for entities like calendar events, deals, teams, roles, property options, and more, with placeholder expressions and documentation.
src/transforms/hubspot/transforms/* (updated files)	Migrated, corrected, and enhanced field mappings, descriptions, and evaluation scores from Fivetran to Airbyte domain; improved mapping completeness and clarity.

Sequence Diagram(s)

sequenceDiagram
    participant Source (Airbyte/HubSpot)
    participant Transform (YAML/SQL)
    participant Target Schema (dbt/Fivetran-like)

    Source->>Transform: Extract raw HubSpot data streams
    Transform->>Transform: Map and transform fields (YAML config)
    Transform->>Target Schema: Output standardized tables (SQL models)

Loading

sequenceDiagram
    participant Developer
    participant Mapping Docs
    participant dbt Project

    Developer->>Mapping Docs: Review mapping confidence and rationale
    Developer->>dbt Project: Update or add SQL/YAML transform
    dbt Project->>Mapping Docs: Auto-generate mapping documentation

Loading

Poem

In the land where data hops and leaps,
A rabbit mapped fields in burrows deep.
Airbyte now leads, Fivetran takes a bow,
With YAML and SQL, we transform it now!
New docs and models, old configs swept,
The schema garden blooms—neatly kept.
🐇✨ Data flows where the mappings grow!

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 SQLFluff (3.3.0)

catalog/hubspot/airbyte-interop-dbt-project/models/company.sql

User Error: No dialect was specified. You must configure a dialect or specify one on the command line using --dialect after the command. Available dialects:
ansi, athena, bigquery, clickhouse, databricks, db2, duckdb, exasol, greenplum, hive, impala, mariadb, materialize, mysql, oracle, postgres, redshift, snowflake, soql, sparksql, sqlite, starrocks, teradata, trino, tsql, vertica

catalog/hubspot/airbyte-interop-dbt-project/models/company_property_history.sql

User Error: No dialect was specified. You must configure a dialect or specify one on the command line using --dialect after the command. Available dialects:
ansi, athena, bigquery, clickhouse, databricks, db2, duckdb, exasol, greenplum, hive, impala, mariadb, materialize, mysql, oracle, postgres, redshift, snowflake, soql, sparksql, sqlite, starrocks, teradata, trino, tsql, vertica

catalog/hubspot/airbyte-interop-dbt-project/models/contact_form_submission.sql

User Error: No dialect was specified. You must configure a dialect or specify one on the command line using --dialect after the command. Available dialects:
ansi, athena, bigquery, clickhouse, databricks, db2, duckdb, exasol, greenplum, hive, impala, mariadb, materialize, mysql, oracle, postgres, redshift, snowflake, soql, sparksql, sqlite, starrocks, teradata, trino, tsql, vertica

• 28 others

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.