Why this matters
Stripe knows who paid, on which plan, and whose charge failed. Relay those events through an automation tool into ReachOut's project API and every contact carries the fields your campaigns need: onboarding for new customers, reminders for failed payments, upgrade pitches by plan.
What you get
- Uses the Stripe triggers already available in Zapier, n8n and Make — no ReachOut-side Stripe setup.
- The Stripe customer email identifies the contact in ReachOut.
- Plan and payment status land in custom fields you can segment on.
- Segments and campaigns stay in Studio, or in your AI agent through MCP.
Setup in 4 steps
- Add custom fields.Studio → Contacts → Schema. Create fields such as plan and payment_status.
- Pick a Stripe trigger.In Zapier, n8n or Make, start from a Stripe event such as a completed checkout, a new subscription or a failed invoice payment.
- Upsert the contact.In Zapier, n8n or Make, POST /api/projects/YOUR_PROJECT_ID/contacts/search to find the contact by email. PATCH /api/projects/YOUR_PROJECT_ID/contacts/:contactId with the new customFields when it exists; otherwise POST /api/projects/YOUR_PROJECT_ID/contacts.
- Segment and send.Studio → Segments: build a segment on plan or payment_status. Studio → Campaigns: send or schedule a campaign to that segment.