Skip to main content

@playrunner/schedule

Schedule Integration

Start workflows on recurring schedules with frequency, interval, timezone, and cron summary state built into the node.

View on npmnpm install @playrunner/schedule
Trigger nodeRecurring runsNo auth
Node typeTrigger
Integration idschedule
Backend mount/api/schedule
Frontend

Schedule configuration UI

Default-exports scheduleIntegration and also exports ScheduleConfigPanel for frequency, interval, timezone, and cron summary state.

Workflow model

Trigger node config

Schedule settings are node-specific, so they belong in the workflow node config rather than account-level integration storage.

Backend

Consistent API shape

Exports scheduleRouter, mounted at /api/schedule, even though the current Schedule node has no backend endpoints.

Icon

Lucide source

Uses the AlarmClock icon from lucide-react, so it does not need a packaged image asset.

Exports​

import scheduleIntegration, { ScheduleConfigPanel } from '@playrunner/schedule';
import scheduleApiContribution, {
  scheduleRouter,
} from '@playrunner/schedule/api';

The same contribution objects remain available as named exports. The default exports are the build-composition contract.

Frontend​

The frontend entrypoint default-exports scheduleIntegration, which keeps the existing integration id as schedule so saved workflows continue to resolve their trigger nodes.

Schedule owns the configuration UI, including frequency, interval, timezone, and cron summary state.

Schedule sets showInputPanel: false, so it does not accept inbound workflow connections. It can be added directly to the canvas, but it appears disabled in the node selector when the user is completing a connection target.

The package manifest declares the schedule ID plus its . frontend and ./api surfaces, and both entrypoints default-export their contribution. Frontend and API builds discover those surfaces from installed direct production dependencies and generate static imports; no shared registry edit is required.

API​

The API entrypoint default-exports scheduleApiContribution, containing the empty scheduleRouter and its /api/schedule mount path. The current Schedule node has no package-local backend endpoints.

Orchestrator​

The Schedule package does not currently declare an ./orchestrator surface. Schedule triggers remain on explicit host-managed scheduling and Orchestrator paths. The package-owned contribution model currently supplies Schedule's frontend and API surfaces only.

Assets​

Schedule uses the AlarmClock icon from lucide-react, so it does not need a packaged image asset.