Proxiedmail MCP integration
Stands up webhook receivers for incoming mail, checks the payloads they captured, and repoints existing proxy bindings.
5actions available
What your agent can do with Proxiedmail
Every action runs live through MCP. Nothing to build, nothing to maintain.
Create a webhook receiver for incoming email callbacks.
How businesses use Proxiedmail + Lyro
Each card is one request a support team gets, and the Proxiedmail actions Lyro runs to close it.
Stand up an endpoint for incoming mail and prove it fired
Lyro creates a webhook receiver to capture ProxiedMail callbacks, then reads back the payload delivered to its call URL to confirm the event actually arrived rather than assuming it did.
Create Webhook ReceiverGet Webhook DataRepoint a proxy address that has moved
Lyro lists the proxy bindings on the account, updates the addresses or settings on the one that needs to change, and reads the API token those calls authenticate with.
List Proxy BindingsUpdate Proxy BindingGet API Token
How it works
Get started in 3 steps
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Proxiedmail actions it has and picks the ones a request needs.
- 01
Connect Proxiedmail
Authorize the Proxiedmail account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
- 02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Proxiedmail actions that close it and chains as many as the request needs.
- 03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free
Everything else about Proxiedmail
Setup, permissions, and the limits of what Lyro can do inside Proxiedmail.
No. This toolkit covers the configuration around existing addresses - listing and updating proxy bindings, and the webhook receivers that catch their mail. Issuing a new proxy address is not one of the five actions, so it stays a task in ProxiedMail.
Every action available in Proxiedmail
All 5 actions your agent can call on Proxiedmail, straight from the live MCP connection.
Create webhook receiver
Create a webhook receiver for incoming email callbacks.
Get API token
Retrieve a permanent API token.
Get webhook data
Retrieve data from a webhook receiver.
List proxy bindings
Fetch a list of proxy bindings.
Update proxy binding
Update an existing proxy binding.
The tools Proxiedmail sits next to
Same connection, same setup. Pick the next one your team already uses.
Apilio
Reads current variable values, lists the conditions and logicblocks behind an automation, and shows which triggers fire on time or device state.
Crowdin
Reports translation progress by language and branch, files and labels new source strings, and runs builds so a release stops waiting on a manual status check.
Formdesk
Reads a form's field rules, files entries on a customer's behalf, and forwards finished submissions to an external endpoint.
Maintainx
Finds assets and work orders, raises work requests and orders with comments, maintains categories and procedures, and drives jobs to close-out.
Procfu
Reads Google Sheets in as arrays, works out what changed between two list versions, and moves files between Podio, FTP, and Google Drive.
Spondyr
Tracks whether generated correspondence was delivered, triggers delivery, and maintains the template conditions and transaction schemas behind it.

Ready to connect Proxiedmail?
Authorize the account and your agent has all 5 actions from the first conversation.


