Timer-based
Run on a schedule Not from a page request
Scheduling Actions
Learn where Node.js Scheduler actions fit in Wappler and how timed workflows differ from page or API-triggered actions.
Introduction
Section titled “Introduction”Scheduling Actions are a Node.js-specific runtime feature in Wappler. Use them when work should run on a timer instead of waiting for a page request, form submit, or API call.
The workflow is still built with familiar Server Connect surfaces, but the trigger is time-based rather than route-based.
Server-side
Use familiar Server Connect steps
Best for maintenance
Sync jobs Cleanup tasks Batch work
Use scheduled actions when the server should run work on its own timetable.
Keep normal page routes and API actions for user-driven request/response flows.
Think of Scheduler as a Node.js runtime trigger attached to the same server-side workflow model.
Wrap-up
Section titled “Wrap-up”Review what you did and choose a next tour.
Next steps
Section titled “Next steps”Continue with the Node.js-specific branch or jump back to the shared Server Connect learning path.