Any endpoint can be set to run on a schedule ("Every N minutes," in its builder header) instead of only when someone calls it directly, useful for periodic cleanup, syncing data from elsewhere, or sending a recurring report.
What a scheduled run looks like
A scheduled run happens with an empty request, no caller, no query string, no body, so its logic shouldn't depend on request data being present. Anything it needs (an external API call, a stored secret) should come from the endpoint's own blocks.
The real interval, in practice
How often your schedule can actually fire depends on our hosting plan's cron frequency, not on the number you type here. Right now that's once a day, so an endpoint set to run "every 10 minutes" will, in practice, run once daily until that changes. This is a platform-wide limit, not something specific to your project or plan.
Tip: If timing matters for what your endpoint does (a report needing "yesterday's data," for example), write its logic to work correctly no matter how long it's actually been since the last run, rather than assuming exactly N minutes have passed.