reverse-etl

Design and implement reverse ETL pipelines that push warehouse data into operational tools.

1|1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/nrakow/ae-skills-dev --skill reverse-etl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reverse-etl
Source: https://github.com/nrakow/ae-skills-dev/tree/main/skills/reverse-etl
Command: npx skills add https://github.com/nrakow/ae-skills-dev --skill reverse-etl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reverse ETL pipelines move modeled warehouse data into operational tools such as Salesforce, HubSpot, and Intercom to empower go-to-customer teams.

Core Features & Use Cases

  • Activation layer design between marts and sync tools, one model per destination.
  • Explicit field mappings, stable natural keys, and idempotent upserts to prevent duplicates.
  • Governance and safety practices, including PII handling, runbooks, and audit logs.

Quick Start

Create an activation model under models/activation for your first destination and configure Census or Hightouch to run after your dbt activation runs.

Frequently Asked Questions about reverse-etl

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is reverse ETL and how does it sync warehouse data to Salesforce?

Reverse ETL is the process of pushing modeled warehouse data into operational tools like Salesforce. It creates an activation layer between dbt marts and sync tools to reliably update downstream systems with modeled metrics.

How do I set up an activation layer between dbt and Hightouch?

To set up an activation layer, create a dedicated model under models/activation for each specific destination. Configure Hightouch to execute the sync only after your dbt activation runs complete to ensure data freshness.

Can I use Census and dbt for audience activation without creating duplicates?

Yes, you can sync to Census without duplicates by using explicit field mappings, stable natural keys, and idempotent upserts. This ensures reliable batch-driven audience activation and prevents duplicate records in target platforms.

Does reverse ETL support PII controls and governance artifacts for HubSpot?

Reverse ETL pipelines include governance and safety practices for syncing to HubSpot, featuring PII handling controls, audit logs, and runbooks. These governance artifacts ensure compliant data activation across operational tools.

When should I design one model per destination in reverse ETL pipelines?

You should design one model per destination to maintain clear activation layer architecture between marts and sync tools. This practice ensures explicit field mappings and idempotent execution for targeted systems like ad platforms.