WebhookHQ
Automate your incoming webhook
Visit Website
March 31, 2019
Action
The core feature for the whole hookeepr 2.0, output your webhook to different channel.
March 28, 2019
a more visual way to add filter
I find out not many of user using the filter feature, doing a short gif this round for the v2
March 18, 2019
Version 2.0 WIP
Setup trello as public roadmap, might share some public stats there as well.
November 16, 2018
Brainstorm for v2
Having some ideas for version 2, if you have any feedback please share with me !
2 Comments
Hey @knight, I like your service and think the rebranding is good!
Had a client who could have benefited from something similar a year ago. They would have pumped a lot of webhook events into the service to have an api for that data.
Not sure what your target customer looks like, but seems close to this client of mine. Any reason data isn't persisted indefinitely?
Also, what are actions?
Good idea btw!
Hi,
Yeah, it seems like that is my target customer.
I m actually still consider how long should the data been kept, trying to find the sweet spot for each plan, one of the important points is to keep minumum resources usages for free tier users.
One of the major features for version 2.0 is actually called Action which was renamed to "Channel", this added support to of output of the Webhooks. When an incoming webhook trigger, other than saving it and retrieve by API, it can trigger a channel output immediately. Currently, there are 2 "Channel" supported, Slack & Webhook.
Actions now represent usages on WebhookHQ, every incoming webhooks and outgoing channel consider actions, the system charge users based on numbers of actions.
I hope this clear, let me know if there are any more doubts.