v1.52.0

Added

• Webhooks can now send to any REST API, not just JSON, ntfy and Discord. Pick the new Custom format and you get three extra fields: custom headers (for APIs that authenticate with a token header), a body template you write yourself, and the HTTP method. That covers SMS gateways, ticketing systems and most anything else with a REST endpoint.
  • Write the body in the shape your target expects, e.g. {"to":["+48123456789"],"text":"{{summary}}"}, using the same variables as custom messages. Placeholders work in the URL too, for older APIs that take everything as query parameters.
  • Header values are encrypted the same way device passwords are, and are never sent back to your browser — the form shows the header name and keeps the stored value unless you type a new one.
  • Quotes and special characters in device names or error text are escaped for you, so a router named CHR "lab" won't break the request.
  • Existing webhooks are unaffected.

Fixed

• A webhook test could report success while nothing was actually sent. Some APIs answer 200 OK but put an error such as "Invalid access token" in the response text. That counted as a pass. The test now shows the status code and what the server actually replied, so a misconfigured token is visible immediately.