Overview
Flint doesn't have a native HubSpot integration yet, but many customers automatically create personalized pages from HubSpot contact and company records. The most common patterns are:
- •HubSpot Workflows - Use a native HubSpot workflow with a webhook action to call the Flint API whenever a contact or company meets certain criteria
- •Zapier - Trigger a Zap from a HubSpot list enrollment or property change, then call the Flint API
- •n8n - Build an automation that listens for HubSpot events and creates Flint pages on demand
The result is the same in all cases: whenever a new record enters a HubSpot dynamic list (or any other trigger), Flint automatically generates a personalized landing page for that account.
Common use case: dynamic list auto-populating pages
A popular pattern is to pair a HubSpot dynamic list with Flint page generation. For example:
- 1.You have a dynamic list in HubSpot called "High-fit accounts in Series B+"
- 2.When a company gets added to that list, a HubSpot workflow fires automatically
- 3.The workflow sends the company's name, industry, and key contact details to the Flint API via a webhook
- 4.Flint generates a personalized ABM landing page for that account
- 5.The page URL is written back to the HubSpot company record as a property
- 6.Your reps can see the page URL directly in HubSpot and include it in outreach
What you need
- •A Flint account with API access (sign up at flint.com)
- •A HubSpot account (Professional or Enterprise for Workflows)
- •An ABM page template already created in Flint
- •Your Flint Site ID and API Key from https://app.tryflint.com/app/team
Option 1: HubSpot native Workflows
HubSpot's Workflows feature (available on Professional and Enterprise plans) supports webhook actions that can call the Flint API directly.
- 1.Go to Automation > Workflows in HubSpot
- 2.Create a new Company-based workflow
- 3.Set the trigger to your dynamic list enrollment (or any property change that indicates a high-fit account)
- 4.Add a Send a webhook action
- 5.Set the method to POST and the webhook URL to
https://api.tryflint.com/v1/pages - 6.Add a header:
Authorization: Bearer YOUR_API_KEY - 7.In the request body, include your Site ID, template page slug, and the HubSpot properties you want to pass as context (company name, industry, website, etc.)
- 8.Optionally, add a second action to write the returned page URL back to a HubSpot property on the company record
For reference on the Flint API request format, see the API documentation.
Option 2: Zapier
Zapier makes it easy to connect HubSpot and Flint without any code.
- 1.Create a new Zap with HubSpot as the trigger app
- 2.Choose a trigger event such as New Company, New Contact in List, or Company Property Changed
- 3.Add a Webhooks by Zapier action step
- 4.Set the method to POST and the URL to
https://api.tryflint.com/v1/pages - 5.Add your API key as a Bearer token in the headers
- 6.Map HubSpot fields (company name, industry, website, etc.) to the Flint API request body
- 7.Test the Zap to confirm a Flint page is generated
- 8.Optionally add a second step to update the HubSpot company record with the returned page URL
Option 3: n8n
n8n is a self-hostable automation tool that works well for teams who want more control over their data flow.
- 1.Create a new workflow in n8n
- 2.Add a HubSpot trigger node configured for your desired event (new contact, list membership change, etc.)
- 3.Add an HTTP Request node set to POST
- 4.Configure the URL as
https://api.tryflint.com/v1/pageswith your API key in the Authorization header - 5.Map the HubSpot data to the Flint API request body
- 6.Optionally add a HubSpot node at the end to write the page URL back to the contact or company record
Alternative: Relay.app
Relay.app is another tool that works well for this use case. It supports HubSpot as a trigger and includes AI enrichment steps built in. See the Relay.app + Flint guide for a full walkthrough.
Tips for better results
- •Pass as much HubSpot context as possible in the API request - company size, industry, HubSpot lifecycle stage, and recent activity all improve page quality
- •Write the generated page URL back to a HubSpot property so your reps can find it without leaving HubSpot
- •Set up a filter in your workflow so only high-fit accounts trigger page generation, preventing wasted credits on low-priority records
- •Create a HubSpot view or report that shows which accounts have a Flint page URL populated, so your team knows which prospects have personalized pages ready
