chaoscreater
Active member
Hi all,
I have the following Webhook URLs generated in MacroDroid:
When I put both of these URLs into Firefox, I get a response text on the page showing "OK". On my phone, I then get a notification to show me that "OncallStart" or "OncallEnd" has been triggered. Great.
I then set up a IFTTT rule, where the action is to do a POST on the Webhook URL. So far so good.
For the "OncallStart" webhook, this triggered just fine (via IFTTT) without any issues. I can receive the notification on my phone, no issues.
However, the "OncallEnd" webhook trigger didn't do anything on my phone. In IFTTT, I can see the logs showing that it has been triggered. But my phone doesn't respond to the webhook. I ran the webhook manually in Firefox, it triggers fine. I then tried the webhook URL in Edge and Chrome and they didn't trigger anything. Tried in an incognito window, same thing.
In a nutshell:
Firefox:
OncallStart - 'ok' response text and triggered notification on my phone
OncallEnd - 'ok' response text and triggered notification on my phone
Edge/Chrome:
OncallStart - 'ok' response text and triggered notification on my phone
OncallEnd - 'ok' response text and NOT triggering notification on my phone
IFTTT:
OncallStart - can't view the response but it did run the webhook POST and triggered notification on my phone
OncallEnd - can't view the response but it did run the webhook POST and did NOT trigger notification on my phone
Any ideas why this is the case?
UPDATE:
OK, I think I fixed it. I think what happened was that I initially created the "OncallStart" webhook. I then copied it and then changed the identifier to "OncallEnd". I think doing it this way means that there will be some metadata that are still linked to "OncallStart", because this is a copy of it. Not sure if this is a bug or not.
I ended up just re-creating a new webhook and tested in Edge/Chrome and it works fine now. Haven't verified in IFTTT, since the IF condition hasn't kicked in yet. But so far, both webhook URLs can be manually triggered in any browser, so I'm fairly certain that's fixed now.
It was just weird that previously, the "OncallEnd" webhook would still show an ok status in Edge and was obviously triggered in Firefox....
I have the following Webhook URLs generated in MacroDroid:
When I put both of these URLs into Firefox, I get a response text on the page showing "OK". On my phone, I then get a notification to show me that "OncallStart" or "OncallEnd" has been triggered. Great.
I then set up a IFTTT rule, where the action is to do a POST on the Webhook URL. So far so good.
For the "OncallStart" webhook, this triggered just fine (via IFTTT) without any issues. I can receive the notification on my phone, no issues.
However, the "OncallEnd" webhook trigger didn't do anything on my phone. In IFTTT, I can see the logs showing that it has been triggered. But my phone doesn't respond to the webhook. I ran the webhook manually in Firefox, it triggers fine. I then tried the webhook URL in Edge and Chrome and they didn't trigger anything. Tried in an incognito window, same thing.
In a nutshell:
Firefox:
OncallStart - 'ok' response text and triggered notification on my phone
OncallEnd - 'ok' response text and triggered notification on my phone
Edge/Chrome:
OncallStart - 'ok' response text and triggered notification on my phone
OncallEnd - 'ok' response text and NOT triggering notification on my phone
IFTTT:
OncallStart - can't view the response but it did run the webhook POST and triggered notification on my phone
OncallEnd - can't view the response but it did run the webhook POST and did NOT trigger notification on my phone
Any ideas why this is the case?
UPDATE:
OK, I think I fixed it. I think what happened was that I initially created the "OncallStart" webhook. I then copied it and then changed the identifier to "OncallEnd". I think doing it this way means that there will be some metadata that are still linked to "OncallStart", because this is a copy of it. Not sure if this is a bug or not.
I ended up just re-creating a new webhook and tested in Edge/Chrome and it works fine now. Haven't verified in IFTTT, since the IF condition hasn't kicked in yet. But so far, both webhook URLs can be manually triggered in any browser, so I'm fairly certain that's fixed now.
It was just weird that previously, the "OncallEnd" webhook would still show an ok status in Edge and was obviously triggered in Firefox....
Last edited:
