Turn Polar billing events into emails
Sign in to Polar from Loops and customers become contacts. Paid orders and subscription changes can each start a workflow, with no webhook code.
order.paidcustomer.createdsubscription.canceledsubscription.past_due+ 6 moreThanks, Sam
Your payment went through. Everything is ready for you in Acme.
Open AcmeSend a welcome email when someone becomes a Polar customer, starting from the New Customer template.
Follow up when an order is paid, starting from the Payment Successful template.
Email customers when a subscription starts, is canceled or uncanceled, or goes past due.
Click Sign in to Polar in your Loops settings and pick your organization. Loops adds the webhook.
Turn on the customer, order, and subscription events you want. Loops ignores the rest.
Do I need to write webhook code?
No. Signing in to Polar from Loops creates a webhook endpoint in Polar with the supported events turned on. You choose which events start workflows in Loops.
How are Polar customers matched to contacts?
By email address. If no contact has that email, Loops creates one. First and last name and the Polar external ID can sync too, so you can link contacts to users in your app.
Which Polar events does Loops accept?
Ten: customer.created, customer.updated, customer.deleted, order.paid, and six subscription events (created, active, canceled, uncanceled, past_due, and revoked). Loops ignores other events.
What does Polar send when someone subscribes?
Four events: subscription.created, subscription.active, customer.created, and order.paid. Keep that in mind when you choose the event that starts each workflow.
What happens when a customer is deleted in Polar?
Turn on customer.deleted and choose whether Loops unsubscribes or deletes the matching contact.
Is there a free plan?
Yes. The free plan includes unlimited contacts and up to 4,000 emails to your first 1,000 contacts in any rolling 30-day window, marketing and transactional combined. Upgrade to send to more subscribed contacts.