Give campaign replies a dedicated capture endpoint
When your email system signals that a reply capture route is needed, Notis can create a Proxiedmail webhook receiver and report where it is ready to receive callbacks.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
A reply capture setup can slip between campaign planning and launch when you have to switch tools and remember each setup step.
- Create a dedicated callback receiver when a campaign route is ready.
- Keep endpoint setup tied to a clear launch signal.
- Get a run report without checking Proxiedmail manually.
Setup
Build it in a few focused steps.
- 1Connect Dynosend and Proxiedmail to Notis once in the portal.
- 2Create an automation in the portal or tell Notis in plain language what receiver to create when your backend signals a campaign reply route is ready.
- 3Choose an incoming webhook trigger and send a test request from your backend.
- 4Select where Notis should report runs, then test with one real campaign route.
Questions about this workflow
Does Dynosend trigger this automation directly?
No. Dynosend has no integration trigger events here. Notis starts the workflow when your external tool or custom backend sends an HTTP request.
What does the action do?
It creates a Proxiedmail webhook receiver for incoming email callbacks.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Dynosend to Proxiedmail. A trigger fires from one place; an action lands in another.
Dynosend triggers
Proxiedmail actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get API Token
Tool to retrieve a permanent api token. use after obtaining a bearer token from the auth endpoint (post /api/v1/auth).
List proxy bindings
Tool to fetch a list of proxy bindings. use after authentication to list all proxy bindings associated with the user.
Update Proxy Binding
Tool to update an existing proxy binding. use after obtaining the binding id to modify its addresses or settings.
Connect any two apps with Notis in the middle.
Dynosend and Proxiedmail, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Proxiedmail.