Stripe New Customer Onboarding

Overview

This flow turns the creation of a new Stripe customer into a structured, governed onboarding journey. When Stripe reports a new customer, the flow retrieves the full customer record, derives a business segment, assigns a Customer Success Manager (CSM), provisions a CRM account in Dataverse, generates a set of onboarding tasks, emails the customer a welcome message, and notifies the sales channel — all idempotently, so an existing customer is never re-onboarded.

Why it matters: New customers need a fast, consistent start. Automating provisioning, ownership assignment, and the welcome sequence improves activation and retention while giving sales and CS a single governed record of every new account.

Status: Built. Ships Off (demo). Flow Checker: 0 errors / 0 warnings.

Use Case

A business wants every new Stripe customer to enter a standard onboarding flow automatically, rather than relying on manual CRM entry and ad-hoc welcome emails. This flow is the integration backbone: it listens for new Stripe customers, records them in Dataverse, routes ownership by segment, seeds onboarding tasks with due dates, and keeps both the customer and the sales team informed.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Stripe	shared_stripe	OnNewCustomer GetCustomer
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords CreateRecord
Office 365 Outlook	shared_office365	SendEmailV2

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.

Welcome drip

Extend Send Welcome Email into a multi-step series by adding Delay + additional SendEmailV2 actions, or hand off to a marketing platform.

Segmentation logic

Initialize Segment classifies on account_balance. To segment on plan/amount, call the Stripe REST API (GET /v1/customers/{id} exposes metadata) via an HTTP action and read metadata.plan, then keep the same SegmentCsmMap lookup. Add a third tier by replacing the binary if() with a nested expression.

Task set

Edit flowlibs_OnboardingTasks JSON to change task titles/offsets; no flow edit needed.

CSM routing

Edit flowlibs_SegmentCsmMap JSON to change ownership by segment.

Sales notification

Repoint flowlibs_SalesChannelEmail, or swap Notify Sales Channel for a Teams PostMessageToConversation if a Teams channel is preferred.

30-day health check

The 30-day health check task is already seeded; wire a scheduled companion flow to act on Due On.

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.

coalesce(triggerOutputs()?['body/description'], triggerOutputs()?['body/email'], 'New Customer')

if(greaterOrEquals(abs(coalesce(triggerOutputs()?['body/account_balance'],0)), variables('varEnterpriseThreshold')), 'enterprise', variables('varDefaultSegment'))

coalesce(json(variables('varSegmentCsmMap'))?[variables('varSegment')], json(variables('varSegmentCsmMap'))?[variables('varDefaultSegment')])

equals(length(outputs('Check_If_Customer_Already_Onboarded')?['body/value']), 0)

addDays(utcNow(), items('Create_Onboarding_Tasks')?['offsetDays'])

replace(replace(variables('varWelcomeTemplate'), '{name}', variables('varCustomerName')), '{csm}', variables('varAssignedCsm'))

Customize & download