Refresh BTCPay store context after a ClickUp task update
Keep payment configuration visible whenever the task changes.
Trigger
Task Updated
Triggers when a task is updated. Fires for every kind of update on the task, including comments. If you only care about a specific property changing, prefer the dedicated trigger (`CLICKUP_TASK_STATUS_UPDATED`, etc.) — those are pre-filtered by ClickUp and produce less traffic. `changes[]` can carry any FieldChange variant (`StatusChange`, `PriorityChange`, `AssigneeAddChange`, `AssigneeRemoveChange`, `TagAddChange`, `TagRemoveChange`, `DueDateChange`, `TimeEstimateChange`, `TimeSpentChange`, `NameChange`, `ContentChange`, `CommentChange`, `CustomFieldChange`).
Action
Get Store
Tool to retrieve information about a specific store. use when you need full store configuration.
Why this helps
Small task edits can leave operators working from outdated store assumptions.
- Keep context current
- Reduce repeated lookups
- Support faster decisions
Setup
Build it in a few focused steps.
- 1Connect ClickUp and BTCPay Server in Notis once.
- 2Create an automation for payment operations task updates.
- 3Describe that Notis should retrieve the related store and summarize only changes relevant to the task.
- 4Pick ClickUp Task Updated as the trigger and choose a report channel.
- 5Test with one real task update.
Questions about this workflow
Will this run for comments too?
The broad task update event can include comments; use a dedicated comment trigger if you need narrower behavior.
Does it change store settings?
No. It retrieves store information for context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Clickup to Btcpay server. A trigger fires from one place; an action lands in another.
Clickup triggers
Btcpay server actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Payment Request
Tool to create a new payment request for a store. use after confirming store id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Store
Tool to create a new store in btcpay server. use when you need to provision a new store before processing transactions.
Folder Created
Triggers when a new Folder is created.
Create BTCPay Server User
Tool to create a new btcpay server user. use when you need to register a new user programmatically as an administrator.
Folder Deleted
Triggers when a Folder is deleted.
Register a Webhook
Tool to register a new webhook. use when you need to receive store event notifications.
Folder Updated
Triggers when a Folder is updated (renamed, content edited, etc.).
Delete API Key
Tool to revoke a specific api key. use when you need to remove an api key to immediately prevent its use. call after identifying the key to revoke.
List Created
Triggers when a new List is created.
Delete Payment Request
Tool to delete a specific payment request. use when you need to archive/remove an existing payment request for a store.
List Deleted
Triggers when a List is deleted.
Delete Store Payout
Tool to delete a specific payout from a store. use when you need to cancel a payout no longer needed.
List Updated
Triggers when a List is updated (renamed, content edited, etc.).
Get API Key
Tool to retrieve the current api key. use after authentication to get api key details.
Connect any two apps with Notis in the middle.
Clickup 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.