(I’m not sure whether to post this in Reddit, or here, or talk to @sliemeobn privately. So here goes…)
Let me start with a concrete example:
I would like GitHub on the creation of a new Issue to trigger a Pushcut Notification - that then results in an OmniFocus task being created. (The shortcut to do this works fine, extracting the issue number and title and a URL to the issue.)
Here’s the problem:
The webhook URL format that GitHub uses is not in the form Pushcut can use:
- Yes, it has the secret.
- Yes, it routes through PushCut.
- No, the payload is not in a form PushCut can extract meaning from.
The payload is some JSON and there is no flexibility in its format. This is not the format PushCut needs.
My current solution - which works quite well - is to run a “protocol converter” on a Raspberry Pi. This is some Apache / PHP code I wrote for the purpose. It rewrites the JSON. But
- It required me to expose my Pi to the web which most people won’t do.
- It requires writing web server code which most people won’t do.
- It adds an “always on” hardware requirement.
(My first stab at this used IFTTT’s GitHub integration - which is very unreliable. Hence my “build it myself” second stab.)
I emphasised “which most people won’t do” because this post is actually about widening the applicability of PushCut.
I’d like to discuss how PushCut might accept more flexible input - and hence be even more useful.