Shaped to how you work. Then it runs itself.

Off-the-shelf tools make you bend your process to fit their fields, then send you to another product to automate it. Here you add your own record types and rules, and the automation runs in the same place the records live.

No credit card. Qikbot is included.

Why it's different

Automation that lives where the records live.

Most automation is a third product passing data between two others, and it breaks quietly when either one changes. Here the records, the rules and the automation are one system, so nothing is passed anywhere.

Most toolsQik

Your own data

Extra fields on the objects the vendor decided you need.

Your own record types. A placement, a vehicle or a grant gets the same lists, permissions, history and API as the built-in types.

A process

A board where people drag cards and remember what to do next.

Cards move themselves when the required form comes back, the tasks are ticked or the deadline passes. Each step can email, text, add someone to a group, grant access or run your code on the way in and out.

Triggers

A separate tool watching for changes from outside.

Rules fire the moment a record is created or changed, or on a schedule, using the same filters you use to build a list.

The unusual cases

Not possible, or a custom integration to host yourself.

Write JavaScript and Qik runs it for you, in a sandbox with only the access you give it, and with its own web address if another system needs to call it.

How it works

01

Define your records

Add the types and fields your organisation works with: vehicles, placements, grants, whatever you track.

02

Set the rules

Say what's required, what's shown and what happens next, as plain rules.

03

It runs itself

Workflows move, reminders send and jobs run on schedule without anyone watching.

Your records, your rules

Shaped around you, not the other way round

Every organisation tracks something nobody else does. Vehicles, placements, instruments, cases. Add your own kind of record with your own fields and rules, and it behaves like it was always there: searchable, permissioned, ready for your website and within Qikbot's reach.

  • Your own record types - add a new kind of record, or extra fields on the ones already there. Signatures, uploads, locations, links between records and more.
  • Rules, not workarounds - show, hide or require a field depending on the answers so far. The rule is checked again when it's saved, so it can't be skipped.
  • Lists that ask real questions - "aged 5 to 12, attended fewer than twice this term, with a guardian on file". Save it once and it stays current.
  • Workflows that move themselves - a card moves on when the form comes back or the deadline passes, then emails, texts, assigns or grants access without being asked.

The basics, covered

Your shape, then your rules, then hands off

Everything here can be set up by asking Qikbot, or by hand if you'd rather.

Your own record types

Create new kinds of record with their own fields, lists and permissions, or add fields to the built-in ones.

Rules as expressions

Show a field, require it or work out a value from other answers.

Lists that stay current

Save a question as a list and it updates itself. Around sixty ways to compare, including across related records.

Workflows that move themselves

A card moves when a form comes back or a deadline passes. Each step can send an email, add someone to a group, grant access or run your code.

When something changes

Run a job the moment a record is created or updated.

On a schedule

Run a job every morning, every Monday or on the first of the month.

Your own code, run for you

Write JavaScript for the unusual cases. It runs in a sandbox with only the access you give it, and can have its own web address for other systems to call.

Test without consequences

Try a workflow in test mode before real people are in it.

Built by asking

Describe the process and Qikbot sets up the records, rules and workflow.

When something happens, something else does

Pick an event, like a new incident report, and choose what runs next. No workflow board needed.

Or just ask Qikbot

Ask which staff have a Working with Children Check expiring, put them on a workflow, and have it checked every morning from now on. Qikbot sets up the cards and the schedule, and asks before anything sends.

Start today

The hard parts are already done.

Start a free trial and tell Qikbot what you need, or talk to the people who build it. Either way you begin with something that works.

No credit card. Your data stays yours, and you can export it any time.