Markin + HubSpot integration
Contact properties that drive existing workflows.
What is a HubSpot AI agent?
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 Markin reads
- Contact and deal properties
- Email engagement history
What Markin writes back
- Contact properties with the action and its reason
- Custom events for workflow enrolment
How the connection works
| Pattern | What it means here |
|---|---|
| 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 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
- 01Read contact, company and deal properties.
- 02Read email engagement and workflow enrolment history.
- 03Write the chosen action, reason and expiry as contact properties.
- 04Write an expected-value score the team can sort a view by.
- 05Enrol contacts into an existing workflow through a property change.
- 06Suppress holdout contacts from enrolment automatically.
- 07Read closed revenue back against the decision.
- 08Report which decided actions produced pipeline and which did not.
Scope of work
The growth work behind HubSpot
The list above is what Markin touches in HubSpot. A connector is only the surface. Below is the work itself: what an analyst, a lifecycle manager, a data scientist and an experimentation lead would do between them, running continuously against your own data.
Read the estate
Normally a data engineer, once, then never refreshed.
- 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
Normally a quarterly analyst deep dive.
- 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
Normally a two-week investigation pulled off the roadmap.
- 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
Normally a workshop, limited to the ideas in the room.
- Rank the portfolio by expected value, not by seniority.
- Drop hypotheses that a past experiment already answered.
Decide per customer
Normally segment rules refreshed when someone has time.
- 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
Normally a ticket, then a slot in next month's calendar.
- 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
Normally argued about, rarely measured.
- 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
Normally nobody's job, so nothing is ever switched off.
- Re-test assumptions that decay, such as price sensitivity and seasonality.
- Log every read, decision and write with its reason for audit.
HubSpot questions
- 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.