We’re using Softr for our SaaS subscriber portal, with the Stripe integration so our users can update their subscriptions in Stripe portal.
We also use Churnkey.co in our service to help recover lapsed renewal payments.
I want to integrate Churnkey’s unsubscribe flows into my Softr portal, so that my users will see a dedicated ‘Cancel’ button, that will launch the Churnkey functionality.
Churnkey install details are here: https://docs.churnkey.co/installing-churnkey
It wants a server-side auth hash to be generated, then it wants that auth hash plus the current user subscription ID to be passed to Churnkey on the button click event.
Is that possible inside Softr?
thanks for this idea - we happen to already be Make users, and we’ll look into his approach. Cheers
Hi David - I’m Rob, the CTO at Churnkey - thanks for exploring our docs and providing a path for implementing our cancel flow through Softr.
If you’re up for it, I’d be happy to work with you on a direct Softr-Churnkey integration so everyone with membership accounts could get instant access to Churnkey. We’ve done similar integrations with other platforms who handle billing on behalf of their users.
Hi Rob, thanks for the offer! But just to be clear, I don’t work at Softr, and wouldn’t this require changes in the Softr server?
Ah I saw the cap and figured you worked there! This would indeed require a change on the Softr server
@rob haven’t had a chance to checkout churnkey in details but happy to chat. Pls DM.
@foxyloxy to add what David suggested, also if you have your data in Airtable then airtable automation could also be used to generate HMAC token and then returned back to UI…
Thanks for these ideas @artur and @rob .
We use all of Softr, Churnkey, Make and Airtable, so we may well be able to find a way forward here
If you guys can develop a direct Softr-Churnkey integration, then so much the better for others interested in putting these capabilities together!
Hi @artur and @foxyloxy
We are working on an email based cancel flow - so instead of needing to generate the HMAC token yourself, the cancel flow would ask the user for their email and Churnkey would automatically send them a verification code for authentication.
Practically speaking, this means that as long as you use Stripe and can add a JS snippet to connect a “Cancel” button to triggering the Churnkey script, you’ll be good to go.
@rob @artur Our users are already signed in / verified in our Softr portal via an email validation code, so we would not want to use a method that requires an additional Churnkey email & code.
I think that will mean we need to use the HMAC approach to avoid a double-validation scenario for our users?