HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
poozlehq
poozle
TypeScript2023–2023
poozlehq / poozle

poozle

A single API for product integrations

5Distinct people
10Mentions
0Explicit recommenders
606GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A single API for product integrations

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week10 dated mentions

Observed mentions: 2023-04-11 14:59:51 UTC to 2023-08-18 20:41:46 UTC. Weeks start Monday, UTC.

01232023-04-10 00:00:00 UTC to 2023-04-17 00:00:00 UTC (exclusive): 3 mentions; 3 submissions, 0 commentsApr 102023-04-17 00:00:00 UTC to 2023-04-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-24 00:00:00 UTC to 2023-05-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023-05-01 00:00:00 UTC to 2023-05-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-08 00:00:00 UTC to 2023-05-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-15 00:00:00 UTC to 2023-05-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-22 00:00:00 UTC to 2023-05-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-29 00:00:00 UTC to 2023-06-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-05 00:00:00 UTC to 2023-06-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-12 00:00:00 UTC to 2023-06-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 122023-06-19 00:00:00 UTC to 2023-06-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-26 00:00:00 UTC to 2023-07-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-07-03 00:00:00 UTC to 2023-07-10 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2023-07-10 00:00:00 UTC to 2023-07-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-07-17 00:00:00 UTC to 2023-07-24 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023-07-24 00:00:00 UTC to 2023-07-31 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023-07-31 00:00:00 UTC to 2023-08-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-08-07 00:00:00 UTC to 2023-08-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-08-14 00:00:00 UTC to 2023-08-21 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsAug 14

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Apr 102023-04-10 00:00:00 UTC2023-04-17 00:00:00 UTC330
Apr 172023-04-17 00:00:00 UTC2023-04-24 00:00:00 UTC000
Apr 242023-04-24 00:00:00 UTC2023-05-01 00:00:00 UTC110
May 12023-05-01 00:00:00 UTC2023-05-08 00:00:00 UTC000
May 82023-05-08 00:00:00 UTC2023-05-15 00:00:00 UTC000
May 152023-05-15 00:00:00 UTC2023-05-22 00:00:00 UTC000
May 222023-05-22 00:00:00 UTC2023-05-29 00:00:00 UTC000
May 292023-05-29 00:00:00 UTC2023-06-05 00:00:00 UTC000
Jun 52023-06-05 00:00:00 UTC2023-06-12 00:00:00 UTC000
Jun 122023-06-12 00:00:00 UTC2023-06-19 00:00:00 UTC000
Jun 192023-06-19 00:00:00 UTC2023-06-26 00:00:00 UTC000
Jun 262023-06-26 00:00:00 UTC2023-07-03 00:00:00 UTC000
Jul 32023-07-03 00:00:00 UTC2023-07-10 00:00:00 UTC211
Jul 102023-07-10 00:00:00 UTC2023-07-17 00:00:00 UTC000
Jul 172023-07-17 00:00:00 UTC2023-07-24 00:00:00 UTC110
Jul 242023-07-24 00:00:00 UTC2023-07-31 00:00:00 UTC110
Jul 312023-07-31 00:00:00 UTC2023-08-07 00:00:00 UTC000
Aug 72023-08-07 00:00:00 UTC2023-08-14 00:00:00 UTC000
Aug 142023-08-14 00:00:00 UTC2023-08-21 00:00:00 UTC211

What Hacker News says

10 sources
gotcha. We do the ETL in the background and ensure that the model is completed irrespective of the 1-1 or different entity. You would also be doing the same if you manage the ETL. You could check (https://github.com/poozlehq/poozle/tree/main/integrations/ti...) our ticketing integrations, would love to take some feedback there. 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.
In Show HN: Poozle – open-source Plaid for LLMs

Show HN: Poozle – open-source Plaid for LLMs

Hi HN, We’re Harshith, Manoj, and Manik Poozle (https://github.com/poozlehq/poozle) provides a single API that helps businesses achieve accurate LLM responses by providing real-time customer data from different SAAS tools (e.g Notion, Salesforce, Jira, Shopify, Google Ads etc). Why we built Poozle: As we were talking to more AI companies who need to integrate with their customers’ data we realised managing all SAAS tools data and keeping them up-to-date is a huge infra of ETL, Auth management, Webhooks and many more things before you take it to production. It struck us – why not streamline this process and allow companies to prioritise their core product? How it works: Poozle makes user authorization seamless using our drop-in component (Poozle Link) and handles both API Key and OAuth dance. Post-authentication developers can use our Uni
Read the rest
fied model to fetch data to their LLMs (no need to sync data separately and then normalise at your end). Poozle keeps data updated in real time while giving you options to choose sync intervals. Even if the source doesn’t support webhooks, we’ve got you covered. Currently, we support Unified API for 3 categories - Ticketing, Documentation and Email. You can watch a demo of Poozle (https://www.loom.com/share/30650e4d1fac41e3a7debc212b1c7c2d)... We just got started a month ago and we’re eager to get feedback and keep building. Let us know what you think in the comments : )
132 points · Open discussion
Manik_agg·Jul 29, 2023Submission

Ask HN: Is creating an OAuth app frustrating, time-consuming, and shit?

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. 2. Scopes: Suggests scopes based on your use case and helps you understand them better. Let me know your thoughts in comments, let me know if you folks want to try it out, I will reach out to you.(https://forms.gle/cgsyEpTG5M9BhAHE6).
14 points · Open discussion
Manoj58·Jul 19, 2023Submission

Show HN: Open-Source Plaid for Ticketing SaaS Tools

About Poozle: Poozle (https://github.com/poozlehq/engine) is an open-source integration platform which provides pre-built OAuth flows, Unified Data Models and Webhooks to build deep and custom integrations. Why we built Poozle: At our previous company, we did many integrations and built an in-house integration infrastructure. As we delved deeper, we realized that companies either spend a lot of time and valuable development resources building integrations themselves or end up using expensive and closed IPAAS solutions. Upon speaking with multiple developers using existing Unified API solutions, we discovered that current Unified API providers offer a limited Unified model, leaving developers to spend considerable time handling custom use cases. Current Status: We are currently focused on developing Ticketing SAAS tools and are committed t
Read the rest
o providing complete solutions. We currently support Github, JIRA and Asana integrations, and adding a new integration is easy so anyone can contribute. Beyond our horror story of integrations, we have also heard stories from other engineers. We would like to hear from you about your story. We welcome your feedback and stories on Poozle! Repo: https://github.com/poozlehq/engine Website: https://www.poozle.dev
4 points · Open discussion

Show HN: Poozle – Integrate SaaS APIs 10x Faster with GraphQL

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 believ
Read the rest
e 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. Also do support us by starring our repo [https://github.com/poozlehq/engine]
1 points · Open discussion

Show HN: Integrate third party APIs with ease using GraphQL

We built Poozle (an open source platform) to simplify API integrations. Instead of dealing with multiple providers with different syntax and requirements, our platform offers a standardised interface through GraphQL. Why we built this: 1. In our previous jobs, we did many integrations and found no standardisation to the process. 2. Existing Unified API solutions lack customizability and only work for integrating multiple integrations from one vertical. Our beta version includes: 1. Plug n Play Integrations: Choose an integration from our pre-built list and start using it. 2. Playground: Write a GraphQL query to retrieve a response from the API. The playground includes API documentation for easy discovery and testing. 3. Integrate with your codebase: Seamlessly talk to all the APIs from your codebase using a unique URL provided by Poozle.
Read the rest
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 Product Demo: https://www.loom.com/share/1d93d082e97f4ef0be5035644e9823dc
9 points · Open discussion

Show HN: Open-source platform to Standardise API Integrations using GraphQL

Founder here, Poozle integrates different APIs [Gmail, JIRA, Github, Salesforce, Pipedrive, Slack etc.] and provides a single GraphQL layer to integrate third party APIs and perform CRUD operations. In our previous jobs, we did many integrations, but we found that there is no standardization to the process. We had to write separate authentication code for each application, and for some applications, we had to integrate via APIs because the SDKs were stale. We also found that some integrations were completed quickly, while others took longer. Started working full time on this idea from Jan’23 but the real progress have happened in the last 7 weeks.I strongly believe open source is the only way to create standardisation for API integrations.
6 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.