Bring account profile context into campaign operations
Keep account profile details close to the recurring campaign work that may prompt operational follow-up.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Update BTCPay Server User
Updates the profile of the currently authenticated user.
Why this helps
Account details and campaign operations are reviewed in separate places, making simple follow-ups easy to miss.
- Include authenticated user profile details in an operations report.
- Keep recurring campaign and account review context together.
- Avoid changing user details unless the instruction explicitly calls for an update.
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 summarize Adyntel campaign insights and retrieve the authenticated BTCPay Server user's profile for review, without changing it.
- 4Pick a recurring schedule as the trigger and choose where run reports should go.
- 5Test with one real scheduled review.
Questions about this workflow
Will the automation update the user profile?
No. This workflow retrieves profile information for review. Updating requires a separate explicit instruction and supplied changes.
Does this retrieve an arbitrary user?
No. The available action updates current user information, and this workflow is limited to retrieving the authenticated user's profile.
Can campaign insights determine profile changes?
No. Any requested profile change would need to be supplied explicitly and reviewed.
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.