ceven

Proxiedmail

Generates disposable proxy email addresses for your users and routes incoming mail directly into your workflows via webhooks.

Try Proxiedmail in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Proxiedmail integration

    • Describe the outcome and Ceven picks the right Proxiedmail 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 Proxiedmail data, across all 5 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Proxiedmail 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 Proxiedmail, when, and on whose behalf.
    • The agent pauses and asks when Proxiedmail is unclear instead of plowing ahead.

  4. Enterprise grade security

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

Supported tools

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

Create webhook receiver
Use this when you need a unique endpoint to capture incoming email callbacks and route them to a specific workflow.
Get API Token
Pull the permanent API token for the account. Use this after you have obtained a bearer token from the auth endpoint.
List proxy bindings
Pull a complete list of all active proxy bindings associated with the user account to audit current aliases.
Update Proxy Binding
Modify the addresses or settings of an existing proxy binding using the specific binding ID.
Create proxy binding
Use this to generate a new proxy email address and link it to a destination inbox.
Delete proxy binding
Remove a proxy address permanently to stop receiving mail at that specific alias.
Get binding details
Pull the full configuration and metadata for a single proxy binding by its ID.
Set webhook URL
Update the destination URL where ProxiedMail sends the JSON payload for incoming emails.
List webhook receivers
Pull all configured webhook endpoints to see which workflows are currently listening for mail.
Delete webhook receiver
Remove a webhook endpoint to stop the flow of email data to a specific external URL.
Search proxy bindings
Query your aliases by keyword or destination to find a specific proxy address quickly.
Validate email address
Check if a specific proxy address is currently active and routed correctly within the system.

12 actions · scroll to see them all

Frequently asked questions

Ceven acts as the listener for the webhook receiver you create. When an email hits a ProxiedMail proxy address, ProxiedMail sends a POST request containing the email body and metadata to the webhook URL. Ceven captures this payload in real time and maps the content to your specific workflow variables. This allows the agent to perform actions like summarizing the email, extracting a verification code, or updating a database record without you ever needing to log into an email client. The entire process happens in the background and triggers your defined logic immediately upon receipt of the packet.
No. ProxiedMail is designed specifically as a receiving and proxying service to protect your privacy. It does not provide SMTP or API endpoints for sending outbound mail. If your workflow requires sending a response, you must connect a separate tool like SendGrid or Mailgun. Ceven can coordinate this by taking the data received via ProxiedMail and passing it to your chosen sending service. This separation ensures that your receiving infrastructure remains isolated and your sending reputation is managed through a dedicated delivery provider.
Yes. ProxiedMail enforces strict tier gating on the number of active proxy bindings. Free accounts are limited to a small handful of bindings, while paid tiers increase this limit significantly. If you attempt to create a binding beyond your current plan limit, the API will return a 403 forbidden error. Ceven will surface this error in the workflow logs as a quota limit reached notification. You can manage your active bindings using the List proxy bindings action to delete old ones and make room for new ones without upgrading your plan.
Ceven stores your ProxiedMail API tokens using AES 256 encryption at rest. These tokens are only decrypted in memory for the duration of the API call and are never exposed in the logs or to the end user. Because ProxiedMail uses a bearer token system for its permanent API access, we treat these as high sensitivity secrets. You can rotate your token at any time within the ProxiedMail dashboard, and you simply need to update the connection in Ceven to restore service. No raw tokens are ever passed into the LLM prompt context.
ProxiedMail attempts to deliver the webhook payload to the specified URL. If your endpoint returns a non 200 status code or times out, the delivery is marked as failed. It is important to note that ProxiedMail does not currently offer a built in retry queue for failed webhook deliveries. To prevent data loss, we recommend using a robust listener like Ceven which maintains high availability. If a delivery fails, that specific email event is lost unless the sender resends the message to the proxy address.
ProxiedMail focuses on the transmission of the email body and headers. Large attachments are typically stripped or replaced with a reference depending on the specific configuration of the proxy. When Ceven receives the webhook, it processes the text content of the email. If you need to handle heavy binary attachments, you should check the metadata provided in the payload to see if a download link was generated. The agent can then be instructed to fetch that link and upload the file to your preferred cloud storage provider like S3 or Google Drive.
Proxy bindings remain active indefinitely unless you manually delete them or your account status changes. There is no automatic expiration date set by the system. However, we recommend a regular cleanup workflow in Ceven to delete old bindings that are no longer needed for your project. This keeps your account under the plan limit and ensures that you are not receiving unwanted traffic on old aliases. You can easily build a workflow that lists bindings and deletes any that have not received mail in thirty days.
Yes. You can configure multiple proxy bindings to point to the same webhook receiver URL. When the data arrives in Ceven, the payload includes the specific proxy address that received the mail. This allows the agent to use a conditional switch to determine which user or project the email belongs to. For example, if the email arrived at proxy one, the agent updates Project A, and if it arrived at proxy two, it updates Project B. This architecture allows you to scale your alias count without needing to manage hundreds of different webhook endpoints.

Alternatives to Proxiedmail

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

Mailgun logoMailgunSendGrid logoSendGridSimpleLogin logoSimpleLoginAnonAddy logoAnonAddy

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Proxiedmail 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