Outseta Integration with WeWeb and Xano

Ask us anything
1

I really like Outseta’s value proposition. It integrates payments, auth, CRM and email all together. It looks like it would work well with other types of websites that need to add payment and community functions.

BUT I’m having a bear of a time to get WeWeb, Xano and Outseta to work together. I’ve followed documentation, used the plugins, and a couple of approaches. Each way I get it 80% working between embeds, auth, displaying profile, etc. Outseta’s support is responsive, but they are limited in addressing how the 3 systems work together. I’m seeing others in the WeWeb Community and at StateChange that have had the same issues. It doesn’t appear hard, but I haven’t been able to crack the nut. Issues relate to WeWeb being a single page application and rendering embeds properly based on the Outseta script. Auth is being handled by the Outseta plugin in Xano.

Two questions:

  1. Are there any users with prior experience integrating these three that I could hire to get mine working?

  2. I don’t want to stitch payments, email, CRM together more than I have to, but is there a different stack I should look at?

Thanks.

2

We use Outseta, WeWeb + Xano - BUT we use the POP UPs for login & signup vs. embeds. So … I can’t really help with embeds w/Outseta vs POP UPs. If you have any issues outside of embeds - happy to help.

2 Likes
3

I haven’t integrated Outseta personally, but I’ve integrated a ton of other things into WeWeb. If you’d like to try cracking your problems on a call, I do consulting, it might help, or it might not, there is only one way to find out :slight_smile: Very often I have calls where we find out some missing pieces that unblock people with their issues. Consult with Broberto – Broberto

1 Like
4

Thank you! I’ve read some of your previous posts/questions on this, they helped me along. I am trying to do the embeds.

1 Like
5

Thank you, Broberto. I have another ticket in with Outseta and if that doesn’t fix it I may ping you. Right now the register/login embed is working but the profile does not, so I suspect I’m close.

1 Like
6

Happy to help here too! :slight_smile:

1 Like
7

I had a good call with Outseta today. Essentially:

  • Hard returns in my header script tag caused errors in WeWeb. This error allowed the login page to work but not the profile page. So I had been looking for errors in the wrong place. Hard returns that would normally work in simpler web pages (and are included in the general embed code I copied from Outseta) had to be removed.

  • My current setup: Outseta is being called for registration, login, profile, and logout. Upon login, I have a workflow on a post-login page that receives the Outseta token, exchanges it for a Xano token, gets user, and navigates to a new page. I am using WeWeb’s Xano auth.

  • Outseta is considering the WeWeb/Xano/Outseta integration and may make some improvements in code for this stack and/or documentation.

3 Likes
8

Great news!

I think Outseta is really great - but sadly - I think we will be migrating to CLERK (https://clerk.com) because of their best-in-class AUTH features for enterprise - they set the bar.

Clerk doesn’t have the Stripe management layer that Outseta has - and that layer is HIGHLY valuable when launching an app because it is so fast an easy to change plans/ pricing / referrals / etc - so … people always talk about how well documented STRIPE sdk is - and how easy it is to directly embed stripe checkouts etc - but I can assure you - it’s still a time suck post-launch when you need to change / test things quickly - and with Outseta it’s instant. HIGHLY recommend Outseta for GTM.

1 Like