Check BTCPay payment requests when an Algolia order inquiry arrives
When your support or checkout service sends an order inquiry, Notis can retrieve payment requests for the specified BTCPay store and summarize any relevant match in the run report.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get Payment Requests
Lists payment requests for a store.
Why this helps
Finding a payment request while replying to an order question means digging through BTCPay Server and then returning to the conversation.
- Start a lookup from an HTTP request sent by your support or checkout service.
- Retrieve payment requests only for the store ID provided in the request.
- Get a concise summary of relevant requests in the run report.
Setup
Build it in a few focused steps.
- 1Connect Algolia and BTCPay Server once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, tell Notis to use the supplied order reference and store ID to retrieve payment requests and summarize matching results without claiming payment status unless the returned data includes it.
- 4Choose the Webhook trigger and select where run reports should go.
- 5Send one real order inquiry with a valid store ID to test the workflow.
Questions about this workflow
Does this workflow check Algolia automatically?
Algolia has no trigger event here. The workflow starts when your support or checkout service sends an HTTP request to the Notis Webhook.
Can it confirm that an invoice has been paid?
The listed action retrieves payment requests. Do not treat its results as payment status unless that information is included in the returned data.
What information must the request include?
Include the BTCPay Server store ID and an order or payment request reference that Notis can use to look for relevant results.
When this happens · Trigger
Do this · Action
Lists payment requests for a store.
Supported Triggers and Actions
Notis builds workflows that link Algolia to BTCPay Server. A trigger fires from one place; an action lands in another.
Algolia 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
Deletes a pending payout; it cannot be canceled once processed or completed.
Conditions and details
The operation deletes a specific payout that is pending and no longer needed. It can be canceled only while awaiting approval or awaiting payment; payouts that have already been processed or completed cannot be canceled. The API key must have permission to manage payouts for the store.
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.
Algolia and BTCPay Server, or any other combination from 1,600+ 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.