Appbricx
Docs
FeaturesPricingStart free

Get started

OverviewWhat Appbricx isQuickstart with a coding agentQuickstart with the builderCore concepts

Guides

Data and tablesAccess and rolesBusiness rulesSign-inCustom screensRealtime and topicsWorkflows, schedules and webhooksServer functionsAI in your appPaymentsFilesMessagesIntegrationsVerifyPublishing, domains and rollbackOperating your appExport and self-hostSelf-host install

Tutorials

Build a booking app with Claude CodeMulti-user todo listClient portalSlack on new sign-upTemplates

Reference

Reference homeFrontend SDKHTTP APIMCP toolsCLIIntegrations catalogContract formatAI key resolutionRun Appbricx locally

ntfy

Send push notifications to any device using the ntfy pub/sub service.

CommunicationNo credentials2 actionsAll integrations

On this page
  1. Connect
  2. Call it from a workflow
  3. Actions (2)
  4. send_notification
  5. custom_api_call
  6. Details

Connect

Auth type: No credentials (none). Nothing to connect: the actions run without credentials.

  • In the editor: Backend panel, Integrations tab, then Connect. This connects it for the project.
  • For every project in a workspace: Workspace settings, Integrations.
  • Owners and admins choose which integrations members may connect in the admin panel (Integrations tab), and can attach their own OAuth app there.

Call it from a workflow

Pass the action name and its input. The call resolves with { success, output, error? }; a missing connection resolves with success false and the reason. See ctx.integrations.invoke and ctx.integrations.call.

Native workflow
// .workflow.js (native ctx)
export async function run(ctx) {
  const res = await ctx.integrations.invoke("ntfy", "send_notification", {
    "topic": "<topic>",
    "message": "<message>"
  });
  if (!res.success) throw new Error(res.error);
  ctx.log.info("ntfy answered", { output: res.output });
}
defineWorkflow module
// defineWorkflow module (@app/sdk ctx)
import { defineWorkflow } from "@app/sdk";

export default defineWorkflow({
  id: "ntfy-send-notification",
  name: "ntfy: Send Notification",
  description: "Calls ntfy when a row is created.",
  trigger: { type: "entity_event", entity: "tickets", event: "created" },
  async run(ctx, event) {
    const res = await ctx.integrations.call("ntfy", {
      "action": "send_notification",
      "topic": "<topic>",
      "message": "<message>"
    }) as { success: boolean; error?: string };
    if (!res.success) throw new Error(res.error);
  },
});
From an app (connector proxy)
curl -X POST "$APP_ORIGIN/__appbricx/connector-proxy/ntfy/send_notification" \
  -H "Authorization: Bearer $APP_KEY" \
  -H "content-type: application/json" \
  -d '{"props":{"topic":"<topic>","message":"<message>"}}'

Actions

send_notificationin catalog

Send Notification. Send a notification to ntfy

InputTypeDescription
topicrequiredtextThe topic/channel to send the notification to, e.g. test1
titleoptionaltextThe title of the notification
messagerequiredlong textThe message to send
priorityoptionaltextThe priority of the notification (1-5). 1 is lowest priority.
tagsoptionalarrayThe tags for the notification.
iconoptionaltextThe absolute URL to your icon, e.g. https://example.com/communityIcon_xnt6chtnr2j21.png
actionsoptionallong textAdd Action buttons to notifications, see https://docs.ntfy.sh/publish/#action-buttons
clickoptionaltextYou can define which URL to open when a notification is clicked, see https://docs.ntfy.sh/publish/#click-action
delayoptionaltextLet ntfy send messages at a later date, e.g. 'tomorrow, 10am', see https://docs.ntfy.sh/publish/#scheduled-delivery

custom_api_call

Custom API Call. Make a custom API call to a specific endpoint

InputTypeDescription
urlrequiredobject (depends on other props)url
methodrequiredone of "GET" | "POST" | "PATCH" | "PUT" | "DELETE" | "HEAD"Method
headersrequiredobjectAuthorization headers are injected automatically from your connection.
queryParamsrequiredobjectQuery Parameters
body_typeoptionalone of "none" | "json" | "form_data" | "raw"Body Type
bodyoptionalobject (depends on other props)Body
response_is_binaryoptionalbooleanEnable for files like PDFs, images, etc.
failsafeoptionalbooleanNo Error on Failure
timeoutoptionalnumberTimeout (in seconds)
followRedirectsoptionalbooleanFollow redirects

Details

Id
ntfy
Category
Communication
Tags
push, notifications, open-source, self-hosted
Package
@activepieces/piece-ntfy@0.2.4
Tier
Community

On this page

  1. Connect
  2. Call it from a workflow
  3. Actions (2)
  4. send_notification
  5. custom_api_call
  6. Details
Appbricx

The backend, runtime and hosting for apps your coding agent builds. On our cloud, in yours, or on your own servers.

Features

Coding agents and MCPVerify testingBuilder consolePostgres databaseData APIRealtimeRow-level securitySign-in and authPaymentsWorkflows and jobsAI in your appIntegrationsBackups and rollbackHosting and domainsSelf-host and exportAll features

Product

ShowcasePricingFor coding agentsTemplatesPrivate cloudBring your own AI keyFAQ

Compare

Appbricx vs SupabaseLovable alternativeBolt alternativeFor freelancersFor agencies

Resources

DocumentationReferenceBlogSupportContact

© 2026 Appbricx. All rights reserved.

TermsPrivacyCookiesAcceptable Use