Custom Integrations is live - connect any API to Databox, no code required
Hey PH! 👋
We just launched Custom Integrations - and it's live on the leaderboard today.
https://www.producthunt.com/products/databox?launch=custom-integrations-by-databox
The problem it solves: your data is out there, but it's not in Databox. You submit an integration request, it goes into the backlog, and you wait. Sometimes for months. Sometimes it never comes.
Custom Integrations flips that. Connect any JSON API yourself - OAuth2, pagination, dynamic date handling all covered. Turn the response into a structured dataset and start analyzing it with Genie or any MCP-compatible AI tool. No code, no engineering ticket, no waiting.
A few things I'm curious to hear from this community: What's the first API you'd connect if you could do it in under 10 minutes?
We're in the comments all day - questions, feedback, and pushback all welcome.
Replies
Breaks
Congrats on the launch!
To answer your question: Stripe. Or honestly, our internal buggy CRM endpoint that'll never see an official integration.
Quick one: have you seen anyone hook up an API with OAuth2 + refresh tokens yet? That's usually where these things break.
@gjinprelvukaj I’ve been waiting for something like this. Personally, I’d connect my product analytics API first. If I can skip engineering tickets and just plug it in myself, that’s a huge shift in how I work.
Databox
@lara_bishop Skipping the engineering ticket is exactly the shift - and product analytics APIs are a perfect fit for this. The data is usually well-structured, the API is accessible, and the questions you want to ask are immediate. Would love to hear how it goes if you try it.
Databox
@gjinprelvukaj Stripe actually has a native Databox integration, so you might not need Custom Integrations for that one - worth checking if it covers what you need first. The internal buggy CRM endpoint though, that's exactly the use case this was built for.
On the OAuth2 + refresh token question: token refresh is handled as part of the OAuth2 flow - that's typically where things broke with older approaches, so it was a priority to get right. If you run into edge cases with a specific provider, worth flagging so we can look at it.