App events

A common goal is “run this when something happens in another app,” such as a new GitHub issue, a paid Stripe invoice, or a Linear status change. Luno OS doesn’t have a separate app-event trigger type; instead you react to app events with the trigger sources you already have, pointed at the app. This page covers the patterns.

There’s no defineAppEventSource. The three sources (webhook, schedule, and poll) cover app events. Pick the one that matches how the app delivers events.

When the app sends webhooks

Most modern apps can push events to a URL. This is the best option when it’s available: point the app’s webhook at a webhook trigger.

Define a defineWebhookSource with a payload schema for the app’s event.
Get the URL with luno triggers url <endpoint> and register it in the app’s settings.
Put event-type constraints (literals, enums) in the payload schema so only the events you care about fire.

src/triggers/stripe-invoice-paid.ts

import { defineWebhookSource } from "@meetluno/luno/trigger";
import { z } from "zod";
import workflow from "../workflows/invoice-paid";

export default defineWebhookSource({
  slug: "stripe-invoice-paid",
  name: "Stripe invoice paid",
  description: "Fires when Stripe sends an invoice.paid event.",
  endpoint: "stripe",
  payload: z.object({
    type: z.literal("invoice.paid"),
    data: z.object({ id: z.string() }),
  }),
}).attach({
  workflow,
  transform: (payload) => ({ invoiceId: payload.data.id }),
});

Providers that send every event type to one URL fit the shared endpoint pattern: many triggers on a single endpoint, each with its own payload for its event.

When the app doesn’t push events

If an app has no webhooks (or you’d rather pull), use a poll trigger. Its run() checks the app’s API on a schedule and starts a run only when there’s something new:

src/triggers/new-issues.ts

import { definePollSource } from "@meetluno/luno/trigger";
import workflow from "../workflows/handle-issue";

export default definePollSource({
  slug: "new-issues",
  name: "New issues",
  description: "Polls for open issues every ten minutes.",
  schedule: "*/10 * * * *",
  run: async () => fetchOpenIssues(),
  filter: (result) => result.issues.length > 0,
}).attach({ workflow });

When the source you’re polling needs credentials, resolve them through an action that you call from run(), or read them from your project’s credentials.

Chat apps: the Slack gateway

Conversations are different from events. To let people talk to an agent from Slack (mention it in a channel or DM it), connect the Luno OS Slack App (luno connect slack --kind luno; catalog slug slackbot) and use the Slack gateway rather than a trigger. The gateway delivers inbound messages to an agent and posts replies back as the bot. See external channels.

Finding integrations

To react to an app, call its API from an action inside a poll’s run(), or point its webhooks at Luno OS as above. See integrations for connecting apps.

Next steps

Webhooks

Receive events the app pushes to a URL.

Polling

Pull events from an app on a schedule.

External channels

Connect agents to Slack and other chat surfaces.

Integrations

Connect the apps you use.

Get started

Learn

Build with AI

Resources

When the app sends webhooks

When the app doesn’t push events

Chat apps: the Slack gateway

Finding integrations

Next steps

Webhooks

Polling

External channels

Integrations

​When the app sends webhooks

​When the app doesn’t push events

​Chat apps: the Slack gateway

​Finding integrations

​Next steps

Webhooks

Polling

External channels

Integrations

When the app sends webhooks

When the app doesn’t push events

Chat apps: the Slack gateway

Finding integrations

Next steps