Postmark#
Connect Postmark with server and account API tokens. The source writes 5 fixed tables under titan.postmark.
select
id,
name,
description
from titan.postmark.message_streams
limit 10Connect Postmark#
Open Apps, choose Connect app, and select Postmark.
Enter server and account API tokens.
Review the tables, then save the source.
Watch Sync history until the first run completes.
Credentials are stored as secrets. They never become lake columns or appear in query results.
Sync behavior#
Message streams, outbound messages, bounces, templates, and sender signatures sync together.
A new source syncs when you connect it and then follows its schedule. The default recurring interval is 4 hours. An interrupted run keeps its completed progress and retries safely.
Every lake table also has the system columns _synced_at and _deleted; the column reference below lists source columns only.
Table reference#
message_streams#
titan.postmark.message_streams has 6 source columns.
Source field id.
Source field name.
Source field description.
Source field messageStreamType.
Source field createdAt.
Source field updatedAt.
outbound_messages#
titan.postmark.outbound_messages has 8 source columns.
Source field messageID.
Source field to.
Source field from.
Source field subject.
Source field status.
Source field receivedAt.
Source field tag.
Source field messageStream.
bounces#
titan.postmark.bounces has 8 source columns.
Source field id.
Source field type.
Source field messageID.
Source field description.
Source field bouncedAt.
Source field email.
Source field subject.
Source field messageStream.
templates#
titan.postmark.templates has 5 source columns.
Source field templateId.
Source field name.
Source field subject.
Source field active.
Source field templateType.
sender_signatures#
titan.postmark.sender_signatures has 5 source columns.
Source field id.
Source field domain.
Source field emailAddress.
Source field confirmed.
Source field createdAt.
Deletes and history#
Rows are merged by their source key. When the source can prove that a row was deleted, Supernova keeps the row and sets _deleted so queries can choose whether to include history. Filter current-state queries with where not _deleted.