Mailchimp High-Intent Click to Sales Alert

Overview

This flow turns Mailchimp email engagement into immediate sales action. On a schedule it inspects the most recent campaign's click activity, and for any subscriber who clicked a high-intent link (pricing, demo, contact-sales, quote, buy, trial) it matches them to a Dataverse marketing lead, bumps the lead score, alerts the assigned rep in Teams with full context, and logs a follow-up signal.

Why it matters: A pricing-page click from an email is one of the hottest buying signals. Acting on it within minutes dramatically improves conversion. This build is the architecturally-complete reference implementation — it ships Off; going live requires only connection authorization and env-var configuration.

> Build note — trigger reality: The Mailchimp connector (shared_mailchimp) exposes no link-click trigger and no click/activity action (its only triggers are OnMemberSubscribed and OnCreateList; its actions are campaign/list/member CRUD). So the flow polls on a Recurrence schedule, uses the connector's GetCampaigns action for campaign data, and pulls click-level data from the Mailchimp Marketing Reports API via a built-in HTTP action — a legitimate connector-gap fallback (verified against the live connector swagger). All credentials are bound to flowlibs_ environment variables; nothing is inlined.

Use Case

Sales wants to be alerted the moment a known lead clicks a high-intent link in a marketing campaign, with the lead automatically scored up and a follow-up activity recorded — no manual CRM data entry.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Mailchimp	shared_mailchimp	GetCampaigns
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords UpdateRecord CreateRecord
Microsoft Teams	shared_teams	PostMessageToConversation

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Intent keywords

Edit flowlibs_HighIntentKeywords (matched against URL path segments, so pricing, demo, contact-sales etc.). No flow edit needed.

Score weighting

Change flowlibs_LeadScoreIncrement; or branch on keyword to weight pricing higher than demo.

Routing

The alert currently posts to one Teams channel; extend to route by flowlibs_assignedrep (e.g. an @mention or a per-rep channel map).

Cadence

Tighten the Recurrence interval for faster reaction, or switch the source to a real Mailchimp webhook if you stand up an HTTP-trigger receiver.

Lead source

flowlibs_marketinglead is the demo lead store; in a real tenant, point List Matching Lead at your contact/lead table and map the score column.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@and(equals(item()?['action'], 'click'), not(empty(intersection(split(toLower(coalesce(item()?['url'],'')), '/'), split(toLower(variables('varHighIntentKeywords')), ',')))))

@first(intersection(split(toLower(outputs('Compose_Clicked_Link_Url')),'/'), split(toLower(variables('varHighIntentKeywords')),',')))

@add(coalesce(first(outputs('List_Matching_Lead')?['body/value'])?['flowlibs_leadscore'],0), variables('varLeadScoreIncrement'))

Basic @{base64(concat('flowlibs:', variables('varMailchimpApiKey')))}

https://@{variables('varServerPrefix')}.api.mailchimp.com/3.0/reports/@{outputs('Compose_Campaign_Id')}/email-activity?count=200

Customize & download