3 ms·
This looks really cool. I'm keen to try it. It looks like it might play well with my current logging system of choice, Seq [0]. Do you support inbound webhoo
by tailspin2019 5y ago
This looks really cool. I'm keen to try it.
It looks like it might play well with my current logging system of choice, Seq [0].
Do you support inbound webhooks? I can see webhooks as a destination but not as a source?
[0] https://datalust.co/seq https://datalust.co/seq
- vklmn 5y agoYou can hack almost anything using inbound Event API (https://jitsu.com/docs/sending-data/api https://jitsu.com/docs/sending-data/api) and JavaScript transformations (https://jitsu.com/blog/javascript-transform https://jitsu.com/blog/javascript-transform)
- tailspin2019 5y agoOk cool. As a bit of feedback, I highly suggest adding Webhooks as a source on your marketing site. The first thing I did is navigate to the Sources page and searched for "webhook" which brought up no results. I then searched your docs which only mention Webhooks in the context of being a destination rather than a source. I realise now that you have quite a flexible ingestion API, but it took quite a while (and your confirmation above) to understand this! The product looks awesome though! Good luck with the launch.
- vklmn 5y agoThanks for observation! We will add it. A fresh look to marketing materials is always appreciated!
- tomnipotent 5y agoA standard webhook source abstraction would be very useful, that captures the URI, POST payload and HTTP headers. This way I can setup my source in Jitsu, get a unique URL, and then paste that URL into the tool generating webhook events (e.g. Shopify). A normalized schema based on the JSON payload doesn't need to be created for this to be useful.