Small sales and account teams often plan in Notion and report from HubSpot, which means typing the same contact or deal twice. FlowMattic sends new and updated Notion database items into HubSpot CRM as contacts, companies, deals, tickets or products, and can read a HubSpot deal back into the Notion item when you need the latest figures beside your notes.
2 triggers 32 actions 7 example workflows 1 ready-made template Unlimited runs
When this happens in Notion2 triggers
Do this in HubSpot CRM25 actions
1. TriggerNew Database Item2. ActionCreate ContactWhen Notion fires New Database Item, FlowMattic runs Create Contact in HubSpot CRM with the data from that event.
You build this in the FlowMattic workflow builder on your own site. See the setup steps
Each one uses only triggers and actions the two integrations ship today, plus FlowMattic's own tools. Where the library has a ready-made template, import it instead of building from scratch.
Ready-made templatePeople added to a Notion database of event contacts, partners or prospects become HubSpot contacts, so sales sees them in the CRM without a second round of typing.
New Database ItemCreate Contact
View the template Founders who track opportunities in Notion get the matching HubSpot company and deal created together, so forecasts and reports in HubSpot include every opportunity.
New Database ItemCreate CompanyCreate Deal
A Filter passes only items whose stage changed, such as to Won or Lost, and the HubSpot deal stored on the item is updated to match.
Updated Database ItemFilterUpdate Deal
Account managers log customer issues in a Notion database during calls. Each new item becomes a HubSpot ticket, so the support team works them in its own queue.
New Database ItemCreate Ticket
Tick a refresh box on a Notion item and the workflow reads the deal from HubSpot, then writes its amount and stage back to the item for account planning pages.
Updated Database ItemGet DealUpdate Database Item
Attendees tracked in a Notion event database are created as contacts and added to a static HubSpot list, ready for the follow-up email after the event.
New Database ItemCreate ContactAdd Contact To List
Product managers maintain the catalogue in Notion. Each new item creates a HubSpot product with its name and price, so sales can add it to deals as a line item.
New Database ItemCreate Product
When you finish, each item added to your Notion database creates a contact in HubSpot CRM.
Give the Notion database properties for first name, last name, email, company and phone, plus a text property for the HubSpot ID.
Add a Notion connection and a HubSpot CRM connection under Connects, making sure Notion can reach the database.
Create a workflow with the Notion New Database Item trigger, pick the database and add a test item so FlowMattic captures its properties.
Add a HubSpot CRM step with Create Contact and map each property to a contact field.
Add Notion Update Database Item to write the new HubSpot contact ID to the item, test the workflow and switch it on.
1. Trigger in Notion
New Database Item
2. Action in HubSpot CRM
Create Contact
Fields mapped from the earlier steps (a typical setup)
| From Notion | To HubSpot CRM |
|---|---|
| Name property | First and last name |
| Email property | |
| Company property | Company name |
| Phone property | Phone number |
A trigger starts a workflow. An action is something FlowMattic does in the app as a step.
Notion and HubSpot CRM connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.
Teams keep planning in Notion while HubSpot gets the contacts, deals and tickets it needs for pipelines and reporting.
Records travel from Notion to HubSpot through your own WordPress site rather than an outside automation account.
Runs are unlimited on every plan, so updating deals on every Notion edit adds no cost.
Not on their own, because HubSpot CRM has no triggers here. Start from a Notion update or a Schedule, read the record with Get Deal or Get Contact, then write it back with Update Database Item.
Store the HubSpot contact ID on the Notion item after the first run. A Router can then use Update Contact when the ID exists and Create Contact when it does not.
Yes. Add Create Contact and Create Deal one after the other, mapping the same item's properties into each, and store both IDs back on the item.
Yes. When an item is marked as closed or removed, Updated Database Item with a Filter can run Archive Contact, Archive Deal or Archive Ticket using the stored ID.
Any property the trigger returns, such as text, email, select and date. Check the captured test data and map each value to the HubSpot field it fits.
Did not find your answer? You can browse the help center or ask us directly.
Notion and Slack17 shared templates
Notion and AI Agents9 shared templates
Notion and Fluent Forms6 shared templates
Notion and Discord6 shared templates
Notion and Google Sheets5 shared templates
Notion and ClickUp3 shared templates
Notion and FluentCRM2 shared templates
Notion and Airtable2 shared templatesHubSpot CRM and Google Sheets7 shared templates
HubSpot CRM and Facebook Lead Ads5 shared templates
HubSpot CRM and Fluent Forms5 shared templates
HubSpot CRM and WooCommerce2 shared templates
HubSpot CRM and Airtable2 shared templates
HubSpot CRM and FluentCRM1 shared template
HubSpot CRM and Mailchimp1 shared template
HubSpot CRM and ClickUp1 shared templateInstall FlowMattic, connect both accounts and import a template. Every run stays on your own server.
30-day money-back guarantee Unlimited workflows and runs Self-hosted
Reviewed 23 Oct 2026. The example workflows are written with AI from the real triggers and actions of both integrations and checked against them. Notion integration 2.0.1, HubSpot CRM integration 1.3.0.