HubSpot’s Amazon Redshift connector lets Data Studio sync warehouse data into HubSpot automatically every five minutes, faster than any other native warehouse connector. It’s currently in beta, so a Super Admin has to opt the account in before it appears, and setup requires creating an AWS role and updating permissions in both AWS and Redshift, not just clicking through HubSpot’s interface. It requires a Data Hub Enterprise subscription.

That’s the short version. Here’s what the beta actually involves, step by step, and who should bother turning it on right now.

Why Redshift Is Different From the Other Connectors

We covered how HubSpot’s warehouse connectors compare and how to decide which one fits your business in earlier posts. Redshift deserves its own walkthrough for two reasons.

First, it’s not generally available yet. It sits behind a beta flag that only a Super Admin can enable, which means it’s easy to miss entirely if you’re not the one managing HubSpot’s account settings.

Second, once it is enabled, it behaves differently from Snowflake, BigQuery, or Databricks. Data refreshes automatically every five minutes, which is meaningfully faster than the scheduled syncs on the other connectors. That kind of near-real-time visibility matters for some use cases and is complete overkill for others, worth knowing before you invest the setup time.

Who Should Actually Set This Up Right Now

Before walking through setup, it’s worth being honest about who this is for today:

• Teams already running Amazon Redshift as their warehouse — this isn’t a reason to migrate to Redshift, it’s a reason to connect the one you already have.
• Teams with a Data Hub Enterprise subscription, since that’s required for any native warehouse connector.
• Teams comfortable working in the AWS console, since setup isn’t fully self-contained inside HubSpot.
• Use cases where five-minute freshness actually matters — live inventory, usage-based billing triggers, fast-moving churn signals. If a daily sync would do, the beta’s speed isn’t a reason to prioritize this over a more mature connector.

If that doesn’t sound like you yet, bookmark this one for when the feature moves to general availability.

Step 1: Opt Into the Data Studio Beta

Redshift’s connector lives behind a beta flag. A Super Admin on the account needs to opt in before Amazon Redshift appears as an option under Add external data source in Data Studio. If you’re not a Super Admin, this is the first thing to hand off internally before anything else on this list will work.

Step 2: Connect Your AWS Account

From Data Studio, click Add external data source, search for Amazon Redshift, and select it. To connect, you’ll need to create an AWS role tied to your HubSpot account and grant it access to your AWS account. HubSpot gives you a code snippet you can paste directly into your AWS console to speed this up, or you can build the role manually if your AWS setup requires it.

Once the role exists, paste its ARN into HubSpot and click Connect to Amazon Redshift.

Step 3: Update AWS Permissions

This step looks slightly different depending on your Redshift setup.

If you’re on a provisioned cluster:

• Locate your cluster identifier, AWS region, account ID, and database name.
• Construct your Cluster ARN and DB ARN using that information.
• Update the permission policy with those details and attach it to the role you created in Step 2.

If you’re on a serverless Redshift workgroup:

• Locate your workgroup’s detail page in the AWS Redshift console.
• Copy the Workgroup ARN.
• Update the permission policy and attach it to the same role.

Either way, once permissions are set, paste the endpoint string from your AWS console back into HubSpot.

Step 4: Update Redshift Database Permissions

Back in your Redshift query editor, you’ll run a SQL script that grants the role you created access to the specific database, schema, and objects you want to sync, swapping in your own values for the bracketed placeholders HubSpot provides. This is the step that actually gives HubSpot read access at the database level, separate from the AWS-level permissions in Step 3.

Step 5: Select Your Columns

On the Columns screen, preview your data, check the columns you want to sync, and assign a data type to each one (text, number, and so on). If you make changes, use Refresh table to confirm your selections before finalizing. Click Add data source once you’re satisfied.

Step 6: Use and Monitor the Connection

Once connected, your Redshift source lives under Source library > Warehouses in Data Studio. From there you can check sync health, see how many records and properties are syncing, and confirm the last refresh time. Redshift data refreshes automatically every five minutes, no manual trigger needed.

From this same screen, click Use to build dataset to start combining your Redshift data with other HubSpot sources.

What This Costs You (Beyond the Subscription)

Simply syncing a single Redshift source into HubSpot doesn’t consume HubSpot Credits. But if you prepare that data further inside Data Studio, creating calculated fields, joining it with other sources, those actions do draw on Credits. Worth factoring in if you’re planning anything beyond a straight sync.

Frequently Asked Questions

Is the Amazon Redshift connector available to everyone in HubSpot? Not yet. It’s in beta, and a Super Admin must opt the account into the Data Studio beta before it appears as a connector option.

How often does Redshift data refresh once connected? Automatically, every five minutes, faster than HubSpot’s other native warehouse connectors.

Do I need to write SQL to set this up? Yes, at least once. You’ll run a SQL script in your Redshift query editor to grant the correct database-level permissions. Everything after that is configured through HubSpot’s interface.

What subscription do I need? Data Hub Enterprise. Warehouse connectors in Data Studio, including Redshift, aren’t available on lower tiers.

Does connecting Redshift cost HubSpot Credits? Syncing the source itself doesn’t. Building calculated fields or joining it with other datasets inside Data Studio does.

The Bottom Line

The Redshift connector is a genuinely useful addition for teams already on Redshift who need faster-than-daily visibility into warehouse data, but it’s not yet a one-click experience, and it’s not generally available. If you’re evaluating whether Redshift, or a different connector entirely, is the right fit for your business, our decision framework for choosing a HubSpot warehouse connector is the better place to start. If you’ve already made that call and landed on Redshift, the steps above are what setup actually looks like today.

Working through a Redshift setup, or not sure it’s the right connector yet? Talk to FSM about your HubSpot data strategy.