engine VS poozle

At Poozle (https://github.com/poozlehq/engine), I have created over 40+ OAuth apps and have dreaded every time we had to build them. Everything with Oauth is shit! You have to fill out numerous application details and finding the right scopes is a nightmare. Once you submit an application, there is often too much back-and-forth before the app is finally approved.

Possible Solution: I am considering to build an AI-powered browser extension for myself that automates the Oauth process with the following features:

1. *Auto-Fill:* Pre-fills 80% of the information required to create your app.

Hey, we are more than happy to pick. We already have an issue created https://github.com/poozlehq/engine/issues/125. Could you upvote here?

Hey r/TypeScript! Introducing Poozle, the open-source API integration platform built entirely in TypeScript. Say goodbye to glue code and simplify your API integration process. Customize with TypeScript extensions, and be part of our thriving community. Join us on GitHub https://github.com/poozlehq/engine and unleash the potential of TypeScript in API integration. Let's code together!

Hey, folks we are building an open-source unified API integration infrastructure platform. You can check us out here https://github.com/poozlehq/engine (https://poozle.dev). Do check us out.

We just launched Poozle (https://github.com/poozlehq/engine) which manages Oauth for different integrations and also provide unified data model.

Would love to get your feedback on the same.

Hey HN,

We are Manik, Harshith, and Manoj, the founders of Poozle (https://www.poozle.dev). Poozle is a single integration layer that brings together various SAAS APIs.

We provide a single GraphQL endpoint for all SAAS APIs, regardless of their protocols. Poozle makes it easy to build integrations for your app into services like GitHub, Jira, Salesforce, Pipedrive, Hubspot, and Gmail. To integrate any API, you typically need to read its documentation, implement its specific authentication, and make very specific calls to its servers. Although this may seem normal, it adds up and becomes time-consuming.

The three of us have done numerous integrations into these services for various startups over the years. As a result, we know how painful it can be, particularly when you need to coordinate data from multiple services.

Why GraphQL

We believe that GraphQL is a query language suitable for all APIs. We can express our data requirements succinctly, even between services, and let a single execution engine determine how to translate those requirements into specific API calls.

We have built a GraphQL service that knows how to communicate with each backend API we support, retrieving the exact data you need. Here is the link of out product demo:

[https://www.youtube.com/watch?v=uGIssARKYec&t]

We’d really appreciate your feedback on Poozle. We have a lot we want to improve on, and would love to hear where you want us to go next.

4. Observability: Our monitoring dashboard tracks API usage, latency, and error rates for quick incident detection.

We're still early, so we would love your feedback and opinion. Also, let us know if you need a specific API integrated.

Main Website: https://www.poozle.dev

We do the ETL in the background and ensure that the model is completed irrespective of the 1-1 or different entity. Anyways you would also be doing the same.

Also if you need more customization you can write on top of the integration we have already (https://github.com/poozlehq/poozle/tree/main/integrations/ti...) and plug it into the platform.