jpoehnelt / chrome-meet-webhook-extension Goto Github PK

Hi. Cool idea.

I was trying to get this working with Home Assistant incoming webhook (https://www.home-assistant.io/docs/automation/trigger/#webhook-trigger) and noticed that the webhook being sent is not actually of Content-Type: application/json (event though it is set that way): https://github.com/jpoehnelt/chrome-meet-webhook-extension/blob/master/src/webhook.ts#L37-L39. My POST requests are sent as text/html and Home Assistant doesn't use the body so my data is empty.

Upon closer debugging I found the fetch() API documentation calling out the headers limitation at https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch:

Note that mode: "no-cors" only allows a limited set of headers in the request:

Accept
Accept-Language
Content-Language
Content-Type with a value of application/x-www-form-urlencoded, multipart/form-data, or text/plain

It looks like POSTing JSON is at odds with the no-cors option. Are you actually using this in Chrome and successfully POSTing as JSON?

Due to #63 and cors issues around application/json value in content type headers, an option should be provided to send as application/x-www-form-urlencoded instead.

Capture an event when the meeting ends.

Hey man, this is an awesome plugin!

I'm trying to get it to talk to Homebridge-http-webhooks so I can run a webhook such as:
http://10.0.0.6:51828/?accessoryId=sensor1&state=true

However the current setup wraps it in a json payload.

Is there any way that I can run the above command changing the true/false at the end when the camera is active/inactive?

TIA!