3 ms·
could be interesting if you added the option to also integrate their API with API aggregators -- write their integromate, zapier, pathfix, other blocks -- or at
by aghilmort 5y ago
could be interesting if you added the option to also integrate their API with API aggregators -- write their integromate, zapier, pathfix, other blocks -- or at least give templates -- even templates would be good organic content:
- how to add your API to Zapier
- how to add your API to Integromat or whatever their new name (?) is
- rinse & repeat for all the other fabrics - pathfix, mulesoft, etc.
- asommer12 5y agoAmazing idea, and actually something we're actively developing. Soon you'll be able to connect Kable to any of your other data sources through Segment. Then, if your application is hooked up to services like Zapier, Amplitude, Mixpanel, etc, you'll be able to funnel data into Kable for billing purposes with no additional code. Our goal here is to make it super easy to use Kable for billing no matter what your existing stack looks like
- aghilmort 5y agoyes, my core thought was: 1. your current value prop is help users build API 2. value add is help them get distro for same API by abstracting away having their team deal with writing Zapier blocks, get into app stores for same, etc. 3. doing (2) is a long road, so could kickstart that with organic content for now, since a natural question after build API is ok, how do I get our block on their app store, same for integromat, mulesoft, etc.