here are some tips to differentiate:
1. focus on automating integration provisioning ... ie, dev still have to go through the various third parties they want to integrate with and that is a PITA
2. focus on something other than oauth... api tokens are actually way more straight forward to developers than oauth in terms of setting up
Show HN: Revert – Open-source unified API for product integrations
51–55 of 55 posts
Re: Show HN: Revert – Open-source unified API for product integrations
#52Is this supposed to be like Zapier but embedded in the product more tightly?
Re: Show HN: Revert – Open-source unified API for product integrations
#53Earlier quoted context omitted.
I love these kinds of products, and welcome any competition in the space. But, this comparison to Nango doesn't seem accurate, so I feel inclined to comment. Please correct me if I'm wrong, but you say... > Even though [Nango] seem to have more integrations Nango has north of 100 integrations, Revert seems to have 4 atm? > our integration support is better than them in terms of the depth of use-cases allowed (more st…
Hi! Thanks for your comment. > Even though [Nango] seem to have more integrations We agree Nango has more integrations and we love OSS software so I'm with you on this. Credit where credit is due and we don't want to make false claims at all. We never claimed to have more integrations than them. I'm not sure how what I posted came off as dishonest. > but seemingly only for picking out response key if they're strings,…
Yeah, sorry, I just got caught up in your wording. Since you asked: "Nango seems to have more integrations" feels disingenuous, when you're comparing 4 to 100+. You'll likely be asked to compare yourself with Nango a lot, so it's not a bad idea to know what you're up against.
In any case, I wish you the best of luck with the "one model per resource type" concept you're trying. It's a tricky one, since you're usually stuck with the lower common denominator.
I expect many, if not most users will need additional custom mapping (so if "field A" -> "field B" mapping is the only option for now, expect to run into lots of feature requests that need to pick from objects/compute multiple values into one field. DX around this will be important)
Re: Show HN: Revert – Open-source unified API for product integrations
#54Is this supposed to be like Zapier but embedded in the product more tightly?
Yes. It’s like Zapier that connects various APIs together but instead of no-code blocks that marketing/sales/product teams use, we are an API itself that developers can use to build integrations that are natively coupled into your product. This way your users don’t really know that you’re using Revert
Re: Show HN: Revert – Open-source unified API for product integrations
#55here are some tips to differentiate: 1. focus on automating integration provisioning ... ie, dev still have to go through the various third parties they want to integrate with and that is a PITA 2. focus on something other than oauth... api tokens are actually way more straight forward to developers than oauth in terms of setting up
Excellent suggestions. Thanks so much!
1. Agreed on this! We plan to offer this as a service along side our API offering at some point.
2. We’d be adding more authentication mechanisms soon so API tokens will be supported alongside OAuth.