Automator

Let the tools do the routine on their own.

Connect the qzila tools into workflows. A schedule, a webhook, a tool event or a click starts a run; the steps read and act in the tools, decide, wait for a person’s yes or no, build a PDF report and send it by email or Slack.

Ask for beta access Pricing & examples

Free while in beta

In beta: open to invited organisations and not billed yet. Write to us and we add yours.

All tools →

What it does

Starts on a schedule (every 15 minutes at most), a webhook, a tool event or by hand
Conditions, loops, waits and an approval step that asks a person yes or no
PDF reports from your own templates, sent by email or to Slack
Every run kept step by step: input, output, error, time
Runs as its author: a tool lets the workflow do only what the author may

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.

Endpoint

https://automator.tools.qzila.com/graphql

POST · application/json · { "query": "…" }

Authentication

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.

Signals

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

runWorkflowmutation
Run a workflow now as its author: the approved version, or the draft to try it first.
```
mutation {
  runWorkflow(id: "wf_1", draft: false) {
    id
    status
    startedAt
  }
}
```

runsquery

A workflow’s recent runs: how they started, how they ended, how many steps.

query {
  runs(workflowId: "wf_1", limit: 10) {
    source
    status
    ops
    error
    endedAt
  }
}

activateWorkflowmutation
Switch a workflow on: the draft becomes version 1 the first time.
```
mutation {
  activateWorkflow(id: "wf_1") {
    status
    liveVersion
  }
}
```

Send requests to https://automator.tools.qzila.com/graphql

Other tools

All tools →

Scheduler

Every job, every deadline, one calendar.

Timetracking

Know where your hours go.

Secure Storage

Files that must not leak, shared by links that expire.

Questions about Automator

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.