Scheduler
Every job, every deadline, one calendar.
See every recurring and one-off job your tools run on one month or week view — which are due, late, failed or paused — next to the yearly compliance plan: who does what each month, who approves it, and the evidence that it was done.
Free while in beta
In beta: open to invited organisations and not billed yet. Write to us and we add yours.
What it does
- Cron and one-off jobs from your tools, with their last run and the next one
- Late and failed runs marked, with a Run now button
- Yearly plan: a row per activity, a column per month, assignee and approver
- Evidence per deadline: a file, a link, or a linked job’s successful run
- Submit, approve or return each month’s deadline
How this tool bills
Today's list prices in EUR, read from the qzila price list when this page was built. You are billed monthly for what you used.
In beta: open to invited organisations and not billed yet. Write to us and we add yours.
The API
Every qzila tool is a GraphQL API first; the web UI is one client of it. Anything you can do in the browser you can do from a script, a CI job or the Asign platform.
https://scheduler.tools.qzila.com/graphqlPOST · application/json · { "query": "…" }
Requests are authenticated with your qzila session (the same sign-in as the browser). For automation, sign in once at identity.qzila.com and reuse the session cookie; API keys for service accounts are on the roadmap.
Whatever this tool detects — a verdict flip, a regression, a change, an incident — is emitted as a signal to the qzila alert hub, which forwards it to email, Slack, a webhook, SMS or Jira, and to ServiceWatch. Each signal carries the asset it belongs to, so you can correlate it back to your own inventory (or to an Asign asset).
Main operations
calendarqueryEvery job occurrence and plan deadline in a window, in your time zone.
query { calendar(from: "2026-11-01", to: "2026-11-30", timezone: "Europe/Bratislava") { entries { tool title at state late } deadlines { title month state } } }runNowmutationFire a job now, outside its schedule.
mutation { runNow(jobId: "job_1") { occurrenceId state } }planYearqueryThe yearly plan: each activity with the state of every month.
query { planYear(year: 2027) { rows { activity { title frequency } cells { month state evidenceCount } } } }
Send requests to https://scheduler.tools.qzila.com/graphql
Questions about Scheduler
Where do alerts go?
Every tool reports through one alert hub. You choose per destination: email, Slack, a webhook, SMS or a Jira ticket — and ServiceWatch shows the same signals on one board.
Where is my data kept?
The tools run on AWS in the EU (Frankfurt), operated by adcore s.r.o., a Slovak company. A few services they rely on sit outside the EU — Stripe for card payments, Google for analytics after your consent, the threat-intelligence lookups behind SafeCheck — and the privacy policy lists each one.
Start with one tool. Add the rest when you need them.
In beta: open to invited organisations and not billed yet. Write to us and we add yours.