1. Difficulty in deciphering customer service from 40 different API documentations. 2. Salesforce's numerous unique data fields, hindering the creation of a generic integration solution. 3. Each customer's unique field configurations necessitated the creation of a unified schema, requiring intense data analysis and meticulous mapping.
This process was time-consuming, spanning three weeks, and it wasn't a one-off setup. Every new customer onboarding necessitated at least a day to comprehend their custom fields and align the data with the unified schema.
I've come across some unified API products which aim to address this issue, but they seem to only scratch the surface, providing a unified API at a superficial level.
We're trying to build Poozle that could potentially offer a deeper, more effective resolution.
I'd love to hear your experiences with similar integration complexities. Have you found a comprehensive solution that truly addresses this challenge?
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 to 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