---
title: Markin + HubSpot
url: https://markin.ai/integrations/hubspot
category: Engagement and CRM
description: Connect Markin to HubSpot: write next-best-action decisions to contact properties and let existing workflows execute them.
---

# Markin + HubSpot

> Contact properties that drive existing workflows.

**Job:** Drive existing HubSpot workflows from a decided action.

A Markin and HubSpot setup writes the decided action onto the contact record as a property, so the workflows your team already built fire on a decision instead of a hand-written rule. Nothing about your workflow structure changes.

Small integration surface, immediate effect: a property change is all an existing workflow needs to start doing something better than it did yesterday.

## What can you ask Markin to do in HubSpot?

- How do I trigger HubSpot workflows from a churn risk score?
- Can I write a next best action to a HubSpot contact property?
- How do I prioritise which customers the team should contact this week?
- How do I connect product usage data to HubSpot without an integration build?

## What Markin does in HubSpot

- Read contact, company and deal properties.
- Read email engagement and workflow enrolment history.
- Write the chosen action, reason and expiry as contact properties.
- Write an expected-value score the team can sort a view by.
- Enrol contacts into an existing workflow through a property change.
- Suppress holdout contacts from enrolment automatically.
- Read closed revenue back against the decision.
- Report which decided actions produced pipeline and which did not.

## The growth work behind HubSpot

### Read the estate

- Read consent, subscription and channel eligibility state before anything else.
- Read contact history so past sends count as pressure on the customer.

### Find where revenue is leaking

- Spot onboarding steps where activation falls off and revenue never starts.
- Spot pricing and packaging mismatch between what people buy and what they use.

### Explain why

- Rank drivers by how much of the movement each one accounts for.
- Check whether the same driver is present in comparable segments.

### Write hypotheses worth funding

- Rank the portfolio by expected value, not by seniority.
- Drop hypotheses that a past experiment already answered.

### Decide per customer

- Choose the next best action for each customer, for each moment.
- Arbitrate between every action competing for that same customer.

### Execute in the tools you already run

- Leave the estate exactly as it was if Markin stops writing.
- Write decisions into the CRM, engagement and warehouse systems already in production.

### Prove it caused the revenue

- Hold back a randomised control group on every decision, not one global holdout.
- Read uplift in revenue per customer against that control.

### Retire, govern and hand over

- Re-test assumptions that decay, such as price sensitivity and seasonality.
- Log every read, decision and write with its reason for audit.

Full catalogue: [Everything a growth team does, running every day.](https://markin.ai/growth-work)

## Activation patterns

- **Attribute write-back.** Markin writes the decision onto the customer profile; your existing journeys read it as an entry condition. Latency is the platform's sync interval.
- **Triggered event.** Markin emits an event that starts or advances a journey. Near-immediate, and the channel keeps its own governance.

## What Markin reads from HubSpot

- Contact and deal properties
- Email engagement history

## What Markin writes back

- Contact properties with the action and its reason
- Custom events for workflow enrolment

## Used together with

- [stripe](https://markin.ai/integrations/stripe)
- [snowflake](https://markin.ai/integrations/snowflake)
- [amplitude](https://markin.ai/integrations/amplitude)
- [segment](https://markin.ai/integrations/segment)
- [intercom](https://markin.ai/integrations/intercom)
- [census](https://markin.ai/integrations/census)

## Related

- [Solution: lifecycle-automation](https://markin.ai/solutions/lifecycle-automation)

## FAQ

**How does Markin connect to HubSpot?**

Attribute write-back, Triggered event. Markin writes the decision onto the customer profile; your existing journeys read it as an entry condition. Latency is the platform's sync interval.

**What does Markin read from HubSpot?**

Contact and deal properties; Email engagement history.

**What does Markin write back into HubSpot?**

Contact properties with the action and its reason Custom events for workflow enrolment

**Do we have to move our data to Markin?**

No. Markin reads from your warehouse, product events and operational systems in place, on your compute, under the access rules your data team already set. Nothing is copied into a separate customer base and there is no vendor-side profile store to migrate off later.

**Does Markin replace our engagement platform or CDP?**

No, and it should not. Your engagement platform keeps the channel, the templates, the deliverability and the governance. Your CDP keeps identity and consent. Markin adds the layer neither has: deciding which action deserves to exist for each customer, and proving it against a holdout.

**What if the system we use is not listed?**

The four activation patterns cover almost everything: attribute write-back, triggered event, decision API and direct surface rendering. Any system that exposes an API, accepts a table, or can read a warehouse column can receive decisions. New connectors are built during deployment, typically in days.

Source: https://markin.ai/integrations/hubspot