Job Notifications¶

Notifications tell you about a saved Job run. They do not carry the geospatial output.

Source Destination Email or webhook notice

This is Job configuration. It is not a Canvas Destination. Sending the converted file to an HTTP endpoint is Send data to a Webhook.

You need to be signed in.

When notices are sent¶

Each channel can listen for:

Event	When
Failure	The Job run failed (recommended default)
Success	The Job run succeeded

Failure is on by default when you first enable a channel. Success is off, so frequent scheduled Jobs do not email every successful run unless you ask.

A skipped overlapping run (Cancelled) does not send a notice. Sync “no changes” is not a separate notification event.

A completed run emits each configured event once. Retrying a failed run is a new run and can notify again.

Email¶

On Jobs → create or edit, or Save as Job on the Canvas:

Check Email.
Keep Failure checked unless you also want Success.
Enter the recipient address.

Example failure mail:

Subject: GeoJibe Job failed: Neighborhood Import

Job: Neighborhood Import
Status: Failed
Time: 2026-08-28 14:02 UTC
Run ID: …
Error: Unable to connect to PostGIS destination.

Success uses subject GeoJibe Job completed: Neighborhood Import and the same concise fields without an error line.

Emails never attach datasets and never include passwords, tokens, connection strings, or HTTP Authorization headers.

Server SMTP¶

Recipients are per Job. SMTP is an installation setting, not something each user configures. The same SMTP configuration sends Shared verification email.

The administrator sets:

Variable	Purpose	Default
`ENCIVA_SMTP_HOST`	SMTP server	unset (email disabled)
`ENCIVA_SMTP_PORT`	Port	`587`
`ENCIVA_SMTP_USERNAME`	Login, if required	unset
`ENCIVA_SMTP_PASSWORD`	Password, if required	unset
`ENCIVA_SMTP_TLS`	`starttls`, `tls`, or `none`	`starttls`
`ENCIVA_SMTP_FROM`	From address	unset (required with host)
`ENCIVA_SMTP_FROM_NAME`	From display name	`GeoJibe`

Email is offered only when host and from are both set. See Configuration.

Notification webhook¶

A notification webhook receives JSON about the run, not the converted file. Save it separately from Webhook Destinations: Manage notification webhooks on the Job editor.

Check Webhook.
Choose Failure and/or Success.
Select a saved notification webhook.

Authentication matches other outbound HTTP in GeoJibe: None, Basic, Bearer, and optional custom secret headers.

JSON body¶

{
  "event": "job.failed",
  "job": {
    "id": "…",
    "name": "Neighborhood Import"
  },
  "run": {
    "id": "…",
    "status": "failed",
    "started_at": "2026-08-28T11:02:00Z",
    "finished_at": "2026-08-28T11:02:04Z"
  },
  "error": {
    "message": "Unable to connect to PostGIS destination.",
    "code": "…"
  }
}

Success uses "event": "job.succeeded" and omits error. Timestamps are UTC RFC 3339. IDs are GeoJibe's stored Job and run identifiers.

The request is POST with Content-Type: application/json and X-GeoJibe-Run-ID set to the run ID.

Signature¶

If signing is enabled on the saved notification webhook, GeoJibe also sends:

X-GeoJibe-Signature: sha256=<hex>

<hex> is HMAC-SHA256 of the exact request body bytes, keyed with the stored signing secret, then lowercase hex. Verify against the raw body, not a re-serialized copy.

The signing secret is stored encrypted and is shown only when it is first generated.

Delivery status¶

Notification delivery is separate from the Job result.

Pipeline	Notice
Job succeeded, email failed	Job status stays Succeeded. Run details show the email attempt failed.
Job failed, failure webhook failed	Job status stays Failed.

Open Runs → Details to see each attempt: channel, event, status, HTTP status when applicable, and a short sanitized error. Secrets are not stored there.