Clear obsolete payment requests after campaign review
Close out a stale campaign payment request when it is identified and removal is explicitly approved.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Delete Payment Request
Archives a payment request; once deleted, it cannot be restored.
Why this helps
Old payment requests can remain in the way after a campaign changes or is no longer active.
- Bring potentially obsolete requests into a scheduled review.
- Require a specific request and explicit removal confirmation.
- Keep the reason for cleanup in the run report.
Setup
Build it in a few focused steps.
- 1Connect Adyntel and BTCPay Server once in the Notis portal.
- 2Create an automation from any channel or in Automations, New Automation.
- 3Tell Notis to identify a specific obsolete request for the confirmed store and delete it only after explicit removal approval.
- 4Pick a recurring schedule as the trigger and choose where run reports should go.
- 5Test with one approved cleanup case and a confirmed store.
Questions about this workflow
Will the workflow delete requests automatically based on age?
No. No age-based status or campaign mapping is specified. The prompt should require a clearly identified request and explicit approval.
What does it need to delete a request?
It needs the specific payment request and confirmed store context, as required by the action.
Can Adyntel prove a payment request is obsolete?
No. Campaign insights may provide context, but obsolescence and deletion approval must be supplied or confirmed by a person.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Adyntel to Btcpay server. A trigger fires from one place; an action lands in another.
Adyntel triggers
Btcpay server actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Payment Request
Creates a reusable payment request page for customers to pay an amount.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Store
Creates a new store.
Create BTCPay Server User
Creates a new user account.
Register a Webhook
Registers a webhook to receive real-time notifications about store events.
Delete API Key
Immediately revokes an API key so it can no longer be used.
Delete Payment Request
Archives a payment request; once deleted, it cannot be restored.
Cancel Store Payout
Get Current API Key
Retrieves details and permissions for the current API key only, not all account keys; it cannot change keys.
Connect any two apps with Notis in the middle.
Adyntel and Btcpay server, 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 Btcpay server.