Make API token retrieval a deliberate routine
For a planned integration setup, Notis can retrieve the permanent Proxiedmail API token after the auth step supplies a bearer token, with the run reported to your chosen channel.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get API Token
Tool to retrieve a permanent api token. use after obtaining a bearer token from the auth endpoint (post /api/v1/auth).
Why this helps
API setup can stall when authentication steps are split across tools and the next step is easy to lose track of.
- Put a setup follow-up on a predictable schedule.
- Keep the token retrieval step connected to its prerequisite.
- See whether the scheduled run completed.
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 ask Notis to retrieve the permanent Proxiedmail API token after the auth endpoint bearer token is available.
- 3Choose a schedule aligned with your planned integration setup.
- 4Select a secure, appropriate run-report channel and test with the required bearer-token prerequisite in place.
Questions about this workflow
Will this obtain the bearer token?
No. The listed action retrieves the permanent API token after obtaining a bearer token from the auth endpoint.
Should this run as a routine if no setup is underway?
Use a schedule only when it matches a deliberate integration task and its authentication prerequisite is available.
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.