Skip to main content
Postmark provides email inbound for maintenance reports. Body and metadata work; image attachment rendering is deferred.

​
Current Role

Postmark currently sends inbound email events to: 
/webhooks/maintenance
Development webhook: 
https://api-dev.hellolucia.ai/webhooks/maintenance?provider=postmark&source_channel=email&webhook_kind=postmark_inbound

​
Current Working State

Postmark inbound currently supports: 
subject
sender
body
headers
attachment metadata
This is enough for basic maintenance intake.

​
Current Limitation

Postmark webhook payloads currently provide attachment metadata but not usable binary attachment content for Lucia’s rendering pipeline. Observed result: 
Attachment received
file metadata visible
no renderable image

​
Deferred Upgrade

Planned fix: 
Postmark API retrieval path
Expected flow:
Webhook receives MessageIDEngine calls Postmark APIfetches full message / attachment contentuploads attachment to Bunnyrenders via Bunny CDN
Reference: 
https://postmarkapp.com/developer/api/servers-api#edit-server

​
Current Status

Email body → working
Email metadata → working
Email attachment rendering → deferred

​
Product Decision

This limitation does not block the current live transition because SMS/MMS and WhatsApp already provide image-capable maintenance intake.

​
See Also