CRM
Flag HubSpot contact as MQL on inbound reply streak
Watches inbound replies in Front and, when a contact replies three or more times within a rolling window, marks them a marketing-qualified lead in HubSpot and alerts sales…
How it runs
The automated pipeline, trigger to output.
- TriggerInbound Front message receivedFront
- ActionRecord reply timestamp by senderPostgres
- LogicCount replies in rolling 14-day window
- LogicCrossed 3-reply threshold and not yet flagged?
- ActionSet HubSpot lifecycle to MQLHubSpot
- OutputAlert sales channel in SlackSlack
What it does
Detects sustained engagement from inbound Front replies and converts it into a HubSpot MQL flag. Instead of reacting to one message, it watches for a reply streak — a reliable signal that a contact is actively interested — and tags them accordingly.
When to use it
Use it when high-intent leads hide in your shared inbox because no single reply looks important, but the pattern of repeated replies does. It surfaces warming contacts before a rep notices manually.
How it works
- 1A Front webhook fires on every inbound message received.
- 2The flow extracts the sender's email and records the reply timestamp to a Postgres counter table.
- 3It computes how many inbound replies that email has sent in the last 14 days.
- 4A branch checks whether the count crossed the threshold of three (and hasn't already been flagged).
- 5If so, HubSpot updates the contact's lifecycle stage to marketing-qualified lead and sets an engagement-source property.
- 6A Slack alert tells the sales channel which contact warmed up and why.
Set it up
What you configure once, before turning it on.
- 1Connect FrontShared inbox, conversations.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect HubSpotCRM, deals, marketing, support.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More CRM workflows
Spin up a Monday handoff board for a departing rep's deals
When a rep is deactivated in Salesforce, this creates a Monday.com board with one item per open opportunity so the manager can manually triage and assign each handoff.
Dormant Account Check-In Call Scheduler
On the anniversary of an account's last touch, books a tentative check-in call on the owner's Google Calendar and emails the contact a scheduling invite.
Daily orphaned-opportunity sweep with manager Slack digest
Each morning this scans Salesforce for open opportunities owned by inactive users and posts a per-manager digest in Slack listing the orphaned deals that need a new owner.
Reassign a departed rep's open pipeline by territory
When a Salesforce user is deactivated, this finds all of their open opportunities and reassigns each one to the active rep who owns its territory, then logs the moves.
Escalate opportunities still owned by an inactive rep after grace period
Checks daily for open opportunities that have stayed with an inactive owner past a grace window and escalates each to the regional director by email and Slack with deal context.
AI-Personalized Dormant Account Win-Back
On a dormancy anniversary, an agent researches the account's history and recent public signals, drafts a genuinely personalized win-back email.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.