data-engineering-zoomcamp
Data Engineering Zoomcamp is a free 9-week course on building production-ready data pipelines. Join the course here 👇🏼
- 47k
- Jupyter Notebook
- 6 d ago
Data models for Fivetran's Intercom connector built using dbt.
Repo fivetran/dbt_intercom, read from GitHub 26 min ago. fivetran has not joined Take My Repo.
fivetran/dbt_intercom is a public repo on GitHub by fivetran. Data models for Fivetran's Intercom connector built using dbt. It declares the Apache-2.0 license on GitHub. It has 6 stars and last changed on 2026-11-20. Nobody has reviewed it on Take My Repo yet, which says nothing about its quality. Read from GitHub on 2026-11-22.
In the maintainer's words. Shown from GitHub; Take My Repo does not keep a copy.
This dbt package transforms data from Fivetran's Intercom connector into analytics-ready tables.
>=1.3.0, <3.0.0This package enables you to better understand the performance, responsiveness, and effectiveness of your team's conversations with customers via Intercom. It creates enriched models with metrics focused on conversation performance, admin performance, and customer engagement.
NOTE: Intercom V2.0 does not support API exposure to company-defined business hours. We therefore calculate all
time_tometrics in their entirety without subtracting business hours.
Final output tables are generated in the following target schema:
<your_database>.<connector/schema_name>_intercom
By default, this package materializes the following final tables:
| Table | Description |
|---|---|
| intercom__admin_metrics | Tracks individual admin performance by team including conversation volumes, customer satisfaction ratings, and response times to measure support efficiency at the admin-team level. Example Analytics Questions:
|
| intercom__article_enhanced | Provides insights into help center article performance with enriched data from collections, authors, and help centers to analyze content effectiveness and user engagement. Example Analytics Questions:
|
| intercom__company_enhanced | Provides a complete view of each company with contact counts, conversation metrics, tag associations, and plan information to analyze customer engagement and account health. Example Analytics Questions:
|
| intercom__company_metrics | Aggregates conversation metrics at the company level including total conversations, satisfaction ratings, and response times to understand company-level support needs and engagement patterns. Example Analytics Questions:
|
| intercom__contact_enhanced | Consolidates contact profiles with company associations, conversation history, tag assignments, and engagement metrics to understand individual customer relationships and support needs. Example Analytics Questions:
|
| intercom__conversation_enhanced | Tracks all customer conversations with participant details, response times, conversation state, and tag assignments to measure support efficiency and conversation resolution patterns. Example Analytics Questions:
|
| intercom__conversation_metrics | Aggregates conversation-level metrics including wait times, handling times, and assignment patterns to identify bottlenecks and measure overall support team performance. Example Analytics Questions:
|
¹ Each Quickstart transformation job run materializes these models if all components of this data model are enabled. This count includes all staging, intermediate, and final models materialized as view, table, or incremental.
To use this dbt package, you must have the following:
You can either add this dbt package in the Fivetran dashboard or import it into your dbt project:
Include the following intercom package version in your packages.yml file:
TIP: Check dbt Hub for the latest installation instructions or read the dbt docs for more information on installing packages.
packages:
- package: fivetran/intercom
version: [">=1.8.0", "<1.9.0"]
By default, this package runs using your destination and the intercom schema. If this is not where your Intercom data is (for example, if your Intercom schema is named intercom_fivetran), add the following configuration to your root dbt_project.yml file:
vars:
intercom_database: your_destination_name
intercom_schema: your_schema_name
If you have multiple Intercom connections in Fivetran and would like to use this package on all of them simultaneously, we have provided functionality to do so. For each source table, the package will union all of the data together and pass the unioned table into the transformations. The source_relation column in each model indicates the origin of each record.
To use this functionality, you will need to set the intercom_sources variable in your root dbt_project.yml file:
# dbt_project.yml
vars:
intercom:
intercom_sources:
- database: connection_1_destination_name # Required
schema: connection_1_schema_name # Required
name: connection_1_source_name # Required only if following the step in the following subsection
- database: connection_2_destination_name
schema: connection_2_schema_name
name: connection_2_source_name
If you use Fivetran Transformations for dbt Core™ and are unioning multiple Intercom connections, you can define your sources in a property .yml file, using this as a template. Set the variable has_defined_sources: true under the Intercom namespace in your dbt_project.yml. Otherwise, your Intercom connections won't appear in your DAG. See the union_connections macro documentation for full configuration details.
You can add additional columns to the intercom__article_enhanced, intercom__company_enhanced, intercom__contact_enhanced, and intercom__conversation_enhanced tables using our pass-through column variables. These variables allow for the pass-through fields to be aliased (alias) and casted (transform_sql) if desired, but not required. Datatype casting is configured via a sql snippet within the transform_sql key. You may add the desired sql while omitting the as field_name at the end and your custom pass-though fields will be casted accordingly. Use the below format for declaring the respective pass-through variables in your root dbt_project.yml.
vars:
intercom__company_history_pass_through_columns:
- name: company_history_custom_field
alias: new_name_for_this_field
transform_sql: "cast(new_name_for_this_field as int64)"
- name: "this_other_field"
transform_sql: "cast(this_other_field as string)"
- name: custom_monthly_spend
- name: custom_paid_subscriber
# a similar pattern can be applied to the rest of the following variables.
intercom__contact_history_pass_through_columns:
intercom__conversation_history_pass_through_columns:
intercom__article_history_pass_through_columns:
This package assumes that you use Intercom's help center functionality (article, collection_history, help_center_history) and mapping tables (company tag, contact tag, contact company, conversation tag, team, team admin). If you do not use these tables, add the configuration below to your dbt_project.yml. By default, these variables are set to True:
# dbt_project.yml
...
vars:
intercom__using_articles: False # This disables all help center functionality
intercom__using_collection_history: False # Also requires articles to be enabled
intercom__using_help_center_history: False # Also requires articles and collection_history to be enabled
intercom__using_contact_company: False
intercom__using_company_tags: False
intercom__using_contact_tags: False
intercom__using_conversation_tags: False
intercom__using_team: False
By default this package will build the Intercom staging models within a schema titled ( + _stg_intercom) and the Intercom final models with a schema titled ( + _intercom) in your target database. If this is not where you would like your modeled Intercom data to be written to, add the following configuration to your dbt_project.yml file:
models:
intercom:
+schema: my_new_schema_name # Leave +schema: blank to use the default target_schema.
staging:
+schema: my_new_schema_name # Leave +schema: blank to use the default target_schema.
If an individual source table has a different name than the package expects, add the table name as it appears in your destination to the respective variable:
IMPORTANT: See this project's
dbt_project.ymlvariable declarations to see the expected names.
vars:
intercom_<default_source_table_name>_identifier: your_table_name
By default, the package applies case-insensitive comparisons when resolving source_relation values. If your destination is case-sensitive and you want downstream transformations to respect the exact casing of your source database and schema names, set the following variable:
vars:
fivetran_using_source_casing: true
Fivetran offers the ability for you to orchestrate your dbt project through Fivetran Transformations for dbt Core™. Learn how to set up your project for orchestration through Fivetran in our Transformations for dbt Core setup guides.
This dbt package is dependent on the following dbt packages. These dependencies are installed by default within this package. For more information on the following packages, refer to the dbt hub site.
IMPORTANT: If you have any of these dependent packages in your own
packages.ymlfile, we highly recommend that you remove them from your rootpackages.ymlto avoid package version conflicts.
packages:
- package: fivetran/fivetran_utils
version: [">=0.4.0", "<0.5.0"]
- package: dbt-labs/dbt_utils
version: [">=1.0.0", "<2.0.0"]
The Fivetran team maintaining this package only maintains the latest version of the package. We highly recommend you stay consistent with the latest version of the package and refer to the CHANGELOG and release notes for more information on changes across versions.
A small team of analytics engineers at Fivetran develops these dbt packages. However, the packages are made better by community contributions.
We highly encourage and welcome contributions to this package. Learn how to contribute to a package in dbt's Contributing to an external dbt package article.
fivetran/dbt_intercom is a public repo on GitHub by fivetran. Data models for Fivetran's Intercom connector built using dbt.
It declares the Apache-2.0 license on GitHub.
Its maker has not tagged a system, so it is unknown here. Its README says what it needs.
Open "Take it" on its page: Take My Repo writes an install plan for your machine and hands it to your AI agent (Claude Code, Codex or Cursor), which asks you before each step. Take My Repo has not tested it on any machine.
Its last change on GitHub was on 2026-11-20. Take My Repo does not judge from that whether it is maintained.
Nobody has reviewed it on Take My Repo yet, which says nothing about its quality.

Data Engineering Zoomcamp is a free 9-week course on building production-ready data pipelines. Join the course here 👇🏼
The dbt-native data observability solution for data & analytics engineers. Monitor your data pipelines in minutes. Available as self-hosted or cloud service with premium features.
Open-source live-chat, email support, omni-channel desk. An alternative to Intercom, Zendesk, Salesforce Service Cloud etc. 🔥💬
🧙 Build, run, and manage data pipelines for integrating and transforming data.
Supplementary Materials for the The Complete dbt (Data Build Tool) Bootcamp Udemy course

Always know what to expect from your data.

Fivetran's ad reporting dbt package. Combine your Facebook, Google, Pinterest, LinkedIn, Twitter, Snapchat, Microsoft, TikTok, Reddit, Amazon, and Apple Search advertising metrics using this package.
Great Expectations Airflow operator
AI coding agent tools to build connectors using Fivetran Connector SDK