QueryFlow's native HubSpot connector is on the roadmap (vote at queryflow.featurebase.app/roadmap). Until then, there are three clean patterns for moving HubSpot data on Mac: CSV export, Operations Hub Calculated Properties + manual export, and Flow Books with the HubSpot API.
Quick answer: Three approaches to HubSpot data sync from Mac with QueryFlow: (1) HubSpot's built-in CSV export + QueryFlow CSV pipeline (simplest), (2) HubSpot Operations Hub + scheduled exports + QueryFlow ingest, (3) Flow Book with Python calling HubSpot API (maximum flexibility). Native HubSpot connector on the public roadmap.
Same as Stripe data, but for marketing/sales: HubSpot's analytics are good for operational use but limited for cross-source analytics. Moving HubSpot data to your warehouse enables joining with product database, computing multi-channel attribution, building executive dashboards, and storing for compliance/historical analysis. The most common destination is Snowflake or Postgres, paired with related data from Salesforce, your application, and product analytics.
HubSpot supports CSV export from contacts, deals, companies, tickets, etc. Manual workflow: HubSpot UI → export the data you want → QueryFlow pipeline (CSV source → Snowflake/Postgres destination). Good for one-off analyses or low-frequency refreshes.
If you have HubSpot Operations Hub (the paid product analytics tier), you can configure exports to S3 on a schedule. QueryFlow then runs a pipeline: S3 source → warehouse destination, scheduled to follow the HubSpot export. Closer to production-grade than manual CSV but requires Operations Hub subscription.
For real-time control or custom data shapes, write Python in a Flow Book that calls the HubSpot API directly. Use the hubspot-api-client library, query contacts/deals/companies with appropriate filters, transform with pandas, write to warehouse. Schedule the Flow Book on cron. More code, maximum flexibility, no subscription beyond HubSpot's standard API access.
Approach 1 (manual CSV): one-off analyses, monthly reporting, low engineering capacity. Approach 2 (Ops Hub + S3): production-grade if you're already paying for Operations Hub. Approach 3 (Flow Book + API): when you need fine-grained control, custom transformations, or aren't paying for Ops Hub but want automated sync.
HubSpot's data has many custom properties per object (companies have hundreds of fields by default before customization). The typical pattern: store core fields as columns, store all custom properties as a Snowflake VARIANT or Postgres JSONB column with the full property map. Query specific custom properties later via PATH expressions when needed.
Daily HubSpot sync to Snowflake at 4 AM: Flow Book pulls yesterday's deals + contacts + companies via HubSpot API, transforms with pandas, writes to Snowflake. Mac mini hardware, $25/month tooling cost. Equivalent Fivetran HubSpot connector: $200-500/month depending on data volumes.
Some teams use HubSpot for marketing and Salesforce for sales, needing to sync data between them. Pattern: HubSpot API → Flow Book → Postgres staging table (or directly to Salesforce). For real-time sync, native HubSpot-Salesforce integration is often the right tool. For batch sync with custom logic, QueryFlow approach 3 works well.
On the public roadmap with active demand. Vote and comment at queryflow.featurebase.app/roadmap. Timeline depends on community prioritization. Approaches 1-3 above cover most real workflows in the meantime.
Via Approach 3 with Flow Book + HubSpot API, yes — the API supports creating/updating contacts, triggering workflows, etc. Not a no-code feature yet; requires Python in a Flow Book.
HubSpot has burst and daily API limits depending on your plan. The hubspot-api-client library has built-in rate-limit handling. For large daily syncs, structure your Flow Book to respect the limits — typically not an issue for batch syncs of standard volumes.
Via API calls in Flow Books, yes — the HubSpot API exposes associations explicitly. Native connector when shipped will handle this with proper relationship modeling.
Yes via Flow Book pattern: HubSpot API → in-memory data → Salesforce destination. For complex bidirectional sync, dedicated HubSpot-Salesforce native integration is often simpler. For batch one-way sync with custom logic, QueryFlow works well.
14-day free trial. Start with the CSV approach today, upgrade to Flow Book sync when you need automation.