On: {{ join_events(item.on) }}
Presets: {{ join_presets(item.presets) }}
{{ item.request.headers.map(h => h.key).join(', ') }}
| Targets | Actions |
|---|---|
|
{{ item.request.method.toUpperCase() }}({{ ucFirst(item.request.type) }}) @
On: {{ join_events(item.on) }}
Presets: {{ join_presets(item.presets) }}
|
|
On: {{ join_events(item.on) }}
Presets: {{ join_presets(item.presets) }}
{{ item.request.headers.map(h => h.key).join(', ') }}
{{ filterItem(item) }}Authorization header key by default,
However this might not be enough to remove credentials from the exported data. it's your responsibility
to ensure that the exported data does not contain any sensitive information for sharing.
Form, the event data will be JSON encoded and sent as
...&data_key=json_string, only the data field will be JSON encoded.
The other keys id, event and created_at will be sent as they are.
X-Event-ID and X-Event with the request.Apprise URLs is in beta and subject to many changes to come, currently the
message field fallback to JSON encoded string of the event if no custom message set by us for that
particular event.default preset and selected ALL events, only events that reference the
default preset will be sent to that target. Like wise, if you have limited both events and
presets, then ONLY events that satisfy both conditions will be sent to that target. Only the
test events can bypass these conditions.