Why this matters
Polar handles merchant-of-record billing; ReachOut handles the campaigns that react to it. Relay subscription changes through an automation tool into ReachOut's project API so each contact carries its plan and subscription state, then target onboarding, renewal and win-back campaigns by segment.
What you get
- Relay Polar subscription events with the automation tool you already use.
- Customer email identifies the contact; plan and state become custom fields.
- Subscription state drives segments: trialing, active, past_due, canceled.
- Ask your AI agent to draft an upgrade campaign for a segment through MCP.
Setup in 4 steps
- Add custom fields.Studio → Contacts → Schema. Create fields such as plan and subscription_state.
- Relay Polar events.Point Polar subscription events at a Zapier, n8n or Make scenario that receives them.
- 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: for example subscription_state = past_due. Studio → Campaigns: send or schedule the matching campaign.