CONTENT CREATION

Route blog excerpts into re-engagement vs. power-user newsletters from CRM activity

When a blog post publishes, pulls subscriber engagement tiers from HubSpot, generates a punchy win-back edition for cold contacts and a deep-dive edition for active ones.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNotion post moves to "Published"NotionNotion
  • ActionPull contact engagement scores from HubSpotHubSpotHubSpot
  • LogicBucket contacts into cold vs. active cohorts
  • ActionWrite win-back and deep-dive editions with OpenAIOpenAI
  • OutputSend each edition to its cohort via GmailGmailGmail

What it does

Uses live CRM engagement data to decide who gets which version of a newsletter. Cold or lapsing contacts receive a short, curiosity-driven re-engagement edition; highly active subscribers get a longer, technical deep dive. Both are derived from the same source post.

When to use it

Use it when your list has clearly different engagement tiers and a one-size newsletter underperforms. Good for teams that already track open/click activity in HubSpot and want tone to follow behavior, not guesswork.

How it works

  1. 1A new Notion post hitting "Published" fires the trigger.
  2. 2The flow reads the post and pulls contact engagement scores from HubSpot.
  3. 3A logic step buckets contacts into cold versus active cohorts by recent activity.
  4. 4OpenAI writes two distinct editions: a brief win-back angle for cold contacts and an in-depth angle for active ones.
  5. 5Each edition sends to its cohort through Gmail, and send results are logged back to HubSpot for the next cycle.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect NotionPages, databases, comments.
  2. 2
    Connect HubSpotCRM, deals, marketing, support.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Connect GmailRead, draft, send, label.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.