<story><title>Show HN: Poozle – open-source Plaid for LLMs</title><url>https://github.com/poozlehq/poozle</url><text>Hi HN, We’re Harshith, Manoj, and Manik&lt;p&gt;Poozle (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;poozlehq&amp;#x2F;poozle&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;poozlehq&amp;#x2F;poozle&lt;/a&gt;) 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).&lt;p&gt;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?&lt;p&gt;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 Unified 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.&lt;p&gt;Currently, we support Unified API for 3 categories - Ticketing, Documentation and Email. You can watch a demo of Poozle (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.loom.com&amp;#x2F;share&amp;#x2F;30650e4d1fac41e3a7debc212b1c7c2d)l&quot; rel=&quot;nofollow noreferrer&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.loom.com&amp;#x2F;share&amp;#x2F;30650e4d1fac41e3a7debc212b1c7c2d)...&lt;/a&gt;&lt;p&gt;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 : )</text></story><parent_chain></parent_chain><comment><author>haxton</author><text>Definitely a difficult problem you&amp;#x27;re taking on here, but I don&amp;#x27;t see anything specific to LLMs here? How or why are you marketing towards LLMs?&lt;p&gt;How do you compare to the larger players here already Nango[0] and Merge[1] ?&lt;p&gt;I&amp;#x27;m curious how you&amp;#x27;re thinking about data access &amp;#x2F; staleness? It&amp;#x27;s great that you&amp;#x27;re handling the oauth dance, but does that mean every end user of the product has to auth every product they interface with or are you handling this all at the super admin &amp;#x2F; enterprise level?&lt;p&gt;Right now I think there&amp;#x27;s too much emphasis on the &amp;quot;data loading&amp;quot; aspect of LLMs. I expect to see a swing back into using 3rd party API&amp;#x27;s SDKs. Interested to hear your thoughts on the Google API, it&amp;#x27;s absolutely massive and trying to shoehorn that into a unified API scares me.&lt;p&gt;The only real player that I could see to launch something like this and be successful is Okta.&lt;p&gt;[0] - &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;NangoHQ&amp;#x2F;nango&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;NangoHQ&amp;#x2F;nango&lt;/a&gt;
[1] - &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;merge.dev&amp;#x2F;&quot; rel=&quot;nofollow noreferrer&quot;&gt;https:&amp;#x2F;&amp;#x2F;merge.dev&amp;#x2F;&lt;/a&gt;</text></comment>
<story><title>Show HN: Poozle – open-source Plaid for LLMs</title><url>https://github.com/poozlehq/poozle</url><text>Hi HN, We’re Harshith, Manoj, and Manik&lt;p&gt;Poozle (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;poozlehq&amp;#x2F;poozle&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;poozlehq&amp;#x2F;poozle&lt;/a&gt;) 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).&lt;p&gt;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?&lt;p&gt;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 Unified 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.&lt;p&gt;Currently, we support Unified API for 3 categories - Ticketing, Documentation and Email. You can watch a demo of Poozle (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.loom.com&amp;#x2F;share&amp;#x2F;30650e4d1fac41e3a7debc212b1c7c2d)l&quot; rel=&quot;nofollow noreferrer&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.loom.com&amp;#x2F;share&amp;#x2F;30650e4d1fac41e3a7debc212b1c7c2d)...&lt;/a&gt;&lt;p&gt;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 : )</text></story><parent_chain></parent_chain><comment><author>tuckerconnelly</author><text>This is a very difficult problem. How do you deal with losing data fidelity? If one service&amp;#x27;s entity has X field, but all the others don&amp;#x27;t, do you include it or not?&lt;p&gt;How do you deal with subtle differences in usage of terminology? If one service uses the word &amp;quot;ticket&amp;quot; slightly differently than others, how do you deal with that?</text></comment>