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

Pushover

Send push notifications to mobile and desktop devices via Pushover.

CommunicationAPI key1 actionAll integrations

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

Connect

Auth type: API key (secret_text). Paste the API key (or token) from the provider's settings into the connect dialog. It is encrypted at rest and only decrypted on the server when an action runs.

  • 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("pushover", "send_notification", {
    "message": "<message>"
  });
  if (!res.success) throw new Error(res.error);
  ctx.log.info("Pushover answered", { output: res.output });
}
defineWorkflow module
// defineWorkflow module (@app/sdk ctx)
import { defineWorkflow } from "@app/sdk";

export default defineWorkflow({
  id: "pushover-send-notification",
  name: "Pushover: Send Notification",
  description: "Calls Pushover when a row is created.",
  trigger: { type: "entity_event", entity: "tickets", event: "created" },
  async run(ctx, event) {
    const res = await ctx.integrations.call("pushover", {
      "action": "send_notification",
      "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/pushover/send_notification" \
  -H "Authorization: Bearer $APP_KEY" \
  -H "content-type: application/json" \
  -d '{"props":{"message":"<message>"}}'

Actions

send_notificationin catalog

Send Notification. Send a notification to Pushover

InputTypeDescription
titleoptionaltextThe title of the notification
messagerequiredlong textThe message to send
htmloptionalbooleanTo enable HTML parsing
priorityoptionalnumberThe priority of the notification (-2 to 2). -2 is lowest priority. If set to 2, you should also specify Retry and Expire.
retryoptionalnumberWorks only if priority is set to 2. Specifies how often (in seconds) the Pushover servers will send the same notification to the user.
expireoptionalnumberWorks only if priority is set to 2. Specifies how many seconds your notification will continue to be retried for (every retry seconds).
urloptionaltextA supplementary URL to show with your message.
url_titleoptionaltextA title for the URL specified as the url input parameter, otherwise just the URL is shown.
timestampoptionaltexta Unix timestamp of a time to display instead of when our API received it.
deviceoptionaltextThe name of one of your devices to send just to that device instead of all devices.

Details

Id
pushover
Category
Communication
Tags
push, notifications, alerts, mobile
Package
@activepieces/piece-pushover@0.2.3
Tier
Community

On this page

  1. Connect
  2. Call it from a workflow
  3. Actions (1)
  4. send_notification
  5. 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