Create webhook receiver
Tool to create a webhook receiver for incoming email callbacks. Use when you need a unique endpoint to capture proxiedmail webhook events.
ProxiedMail offers privacy-focused email services, including automatic creation of proxy emails and receiving emails via webhooks.
Tool to create a webhook receiver for incoming email callbacks. Use when you need a unique endpoint to capture proxiedmail webhook events.
Tool to retrieve a permanent API token. Use after obtaining a Bearer token from the auth endpoint (POST /api/v1/auth).
Tool to retrieve data from a webhook receiver. Returns the payload sent to the webhook's call_url, status info about whether a callback was received, and the HTTP method used.
Tool to fetch a list of proxy bindings. Use after authentication to list all proxy bindings associated with the user.
Tool to update an existing proxy binding. Use after obtaining the binding ID to modify its addresses or settings.
The Proxiedmail integration connects your Dench AI CRM directly to Proxiedmail, so agents can read and act on your Proxiedmail data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
5 actions are available for agents to invoke on your behalf. Every call runs through Proxiedmail's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Proxiedmail and click Connect — you'll authorize access through Proxiedmail's own sign-in flow. No API keys or code required.
Ask an agent to use Proxiedmail in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Proxiedmail integration connects your AI CRM to Proxiedmail, so AI agents can work with your Proxiedmail data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Proxiedmail integration currently exposes 5 actions, including Create webhook receiver, Get API Token, Get webhook data, List proxy bindings, and Update Proxy Binding. Agents invoke them on your behalf from chat or from automations.
No. You connect Proxiedmail from your Dench workspace using Proxiedmail's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Proxiedmail's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Proxiedmail connection from your workspace settings at any time.