Connect Hubspot to Btcpay server

When something happens in Hubspot, Notis takes the next step in Btcpay server. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Hubspot to Btcpay server

View example

Create a Bitcoin payment request for a won deal

Turn a HubSpot deal moved to its won stage into a BTCPay Server payment request, using the store you specify.

View example

Prepare a Bitcoin deposit request for a new contact

When HubSpot creates a contact, create a BTCPay Server payment request for an agreed deposit when the required details are available.

View example

Provision a BTCPay store for a won deal

Use a won-deal event to request a new BTCPay Server store when your instruction identifies a need for a separate store.

View example

Review BTCPay payment requests on a schedule

On a recurring schedule, retrieve payment requests for a specified BTCPay Server store and summarize the results in a run report.

View example

Audit BTCPay store webhooks when requested

Start a Notis run with an HTTP request, list the configured webhooks for your BTCPay Server store, and summarize their details.

Supported Triggers and Actions

Notis builds workflows that link Hubspot to Btcpay server. A trigger fires from one place; an action lands in another.

Hubspot triggers

Btcpay server actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Create Payment Request

Tool to create a new payment request for a store. use after confirming store id.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Create Store

Tool to create a new store in btcpay server. use when you need to provision a new store before processing transactions.

ActionInstant

Contact Created Trigger

TriggerInstant

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.

ActionInstant

Deal Stage UpdatedTrigger

TriggerInstant

Register a Webhook

Tool to register a new webhook. use when you need to receive store event notifications.

ActionInstant

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.

ActionInstant

Delete Payment Request

Tool to delete a specific payment request. use when you need to archive/remove an existing payment request for a store.

ActionInstant

Delete Store Payout

Tool to delete a specific payout from a store. use when you need to cancel a payout no longer needed.

ActionInstant

Get API Key

Tool to retrieve the current api key. use after authentication to get api key details.

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.