ceven

Postmark

Sends transactional emails based on system triggers, monitors delivery failures in real time, and manages recipient lists to keep your inbox health high.

Try Postmark in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Postmark integration

    • Describe the outcome and Ceven picks the right Postmark calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Postmark data, across all 46 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Postmark access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Postmark, when, and on whose behalf.
    • The agent pauses and asks when Postmark is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Postmark.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Postmark action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Postmark, and when to use it.

Send email
Use this to push a transactional message to a specific recipient. Define the template, tags, and metadata for tracking.
Get delivery stats
Pull open rates, click rates, and delivery times for a specific message ID to verify receipt.
Create template
Upload a new HTML or text template to a server. Use this when launching new product onboarding flows.
Update template
Modify existing email copy or layout without changing the template ID in your code.
List templates
Pull all available templates for a server to audit current customer communications.
Add to bounce list
Manually add an email address to the suppression list to prevent further sending attempts.
Remove from bounce list
Clear a recipient from the suppression list after they have verified a new email address.
Get server details
Pull configuration and health status for a specific sending server.
List servers
Retrieve a list of all sending servers configured in the account.
Search message history
Find specific emails sent to a user by querying the message archive.
Get recipient status
Check if a specific email address is currently blocked or suppressed.
Delete template
Remove an old or deprecated template from the server to clean up the library.

12 actions · scroll to see them all

Frequently asked questions

Ceven listens for Postmark webhooks that signal a hard bounce or a spam complaint. When these events fire, the agent does not just log the error but executes a predefined recovery workflow. For a hard bounce, the agent can automatically mark the user as inactive in your database and notify the account owner. For spam complaints, it can trigger a review process to see if the content was misclassified. This ensures your sender reputation remains high by immediately stopping sends to invalid addresses without requiring a human to manually export bounce reports from the Postmark dashboard every week.
Yes. Postmark encourages separating transactional mail from broadcast mail to protect deliverability. Ceven supports this by allowing you to map specific workflows to specific server tokens. You can route password resets and order confirmations through your transactional server while routing newsletters or product updates through a separate broadcast server. The agent tracks which server is being used for each action, ensuring that a spike in marketing volume never delays a critical password reset email, which is a core architectural requirement for maintaining high priority delivery speeds.
Ceven stores your Postmark API tokens encrypted at rest using AES 256 encryption. These tokens are only ever accessed by the execution engine at the exact moment a request is sent to the Postmark API. We do not log the tokens in plain text or expose them to the model prompts. You can rotate your tokens within the Postmark dashboard at any time and update them in the Ceven connection settings. This ensures that your sending authority is protected and that you maintain full control over who can trigger emails from your domain.
Postmark enforces strict sending limits based on your account tier and history. If the API returns a rate limit error, Ceven implements an exponential backoff strategy. The agent will pause the workflow and retry the send at increasing intervals. If the limit persists, the agent will trigger a failure notification to your team via Slack or email, alerting you that the Postmark quota is exhausted. This prevents data loss during traffic spikes and ensures that you are aware of the need to upgrade your plan before critical communications are permanently dropped.
Ceven uses Postmark templates with Template Model syntax. Instead of sending a giant block of HTML, the agent sends a JSON object containing the specific variables the template requires. For example, if your template has a placeholder for the user name and their last order number, Ceven pulls those values from your CRM and injects them into the API call. This allows you to keep your design and branding locked in the Postmark UI while the agent handles the logic of what data goes into each specific email for each single recipient.
The agent can both read from and write to the Postmark suppression list. When a user requests to be removed from all communications, Ceven can add them to the bounce or suppression list via the API to ensure no future messages are sent regardless of the workflow triggering them. Conversely, if a user corrects a typo in their email address, the agent can remove the old, incorrect address from the suppression list so that the new one can be used without interference. This keeps your list hygiene automated and compliant with global email regulations.
The delay is minimal because Ceven utilizes Postmark webhooks for event driven triggers. When Postmark records a delivery or a bounce, it pushes that data to our endpoint in real time. The agent then processes the event and kicks off the associated workflow immediately. In most cases, the window from the email event to the subsequent action in your CRM or database is under two seconds. This speed is critical for time sensitive flows like two factor authentication or urgent security alerts where a delay of several minutes would result in a poor user experience.
Yes, Ceven can create templates via the API, but there is a quirk to be aware of regarding the Postmark permission model. The API token used must have the appropriate administrative permissions to create or modify templates on the server. If you are using a restricted token, the agent will receive a forbidden error. We recommend using a server token with full access for the initial setup of your templates. Once the templates are created, you can switch to a more restricted token for daily sending operations to follow the principle of least privilege.

Alternatives to Postmark

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

SendGrid logoSendGridMailgun logoMailgunAmazon SES logoAmazon SES

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Postmark and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free