File
| Schemes | file:// |
| Cargo feature | service-file |
| Body formats | text, html, markdown (first is the default) |
| Attachments | yes |
| Title length | 250 characters |
| Body length | 32,768 characters |
| Body lines | unlimited |
| Request throttle | none |
| Vendor URLs accepted | no |
URL formats
{schema}://{path}
{schema} is one of file://.
URL tokens
| Token | Meaning | Type | Required | Default | Notes |
|---|---|---|---|---|---|
{path} | File Path | string | yes |
Query parameters
No service-specific parameters.
Prefixed parameters:
:name=value: Payload Extras
The common URL parameters (format, overflow, verify, redirect, cto, rto, retry, wait, store, tag, tz, user, password, port, optional, emojis) apply as well.
Notes
File (file://): appends each notification to a local file as one JSON line (JSON Lines).
Each line is exactly the body json:// would post (attachments included, :key=value payload entries applied). file:///var/log/alerts.jsonl is an absolute path, file:///C:/logs/alerts.jsonl a Windows one, file://alerts.jsonl a path relative to the working directory. The file is created when missing; its directory must exist. Each line is written in one append, so concurrent writers do not interleave lines.