Share jobs

A job package is one .querylane.json file with one or more jobs. Use it to send jobs to a colleague or move them to another Mac without git. Connection passwords and secret values are not written to it.

What the file contains

• the jobs: name, description, variables, steps, output settings and notifications;
• folders and tags, if you keep them;
• a description of each connection the steps use: its name, type, host, port and database, without credentials;
• the npm packages that JavaScript steps import;
• the plugins that steps and notifications use, with their version and the presets they pick.

The file leaves out:

• values of variables whose names suggest a secret, such as token, key, password, secret or auth, and of variables locked for export;
• secret plugin settings;
• step version history, run history and artifacts.

A schedule time can travel in the file, but an import never turns a schedule on.

Export jobs

To export one job, click the export icon (Export to file) on its row in the jobs list. To export all jobs of a folder, use Export folder on the folder.

To pick several jobs:

1. Click Export jobs at the top of the jobs list.
2. Select jobs, or use Search jobs and Select all. The dialog shows Selected: 3.
3. Leave Keep folders and tags on if the jobs should land in the same folders on import.
4. Click Export and choose where to save the file.

Credentials typed directly into an API step, for example an Authorization header or a password in a URL, are part of the step and go into the file as they are. QueryLane finds them before the export and shows Credentials in the jobs with the affected steps. Click Cancel and move the values into secret variables, or click Export anyway.

Import jobs

1. Click Import jobs from a file at the top of the jobs list and choose the file. You can also drop the file onto the jobs list.
2. Check the sections of Import jobs and click Import.

Jobs lists the jobs in the file. When a job with the same id or name already exists, choose Import as a copy (the default) or the Replace option with the name of your job. A copy gets a free name such as Daily report (2). A replaced job keeps its place, its schedule and its step version history: changed steps get an Import entry, and steps missing from the file move to Deleted steps (see Versions and git).

What the jobs read and send lists the files the jobs read and the hosts they send requests to.

Connections maps each connection from the file to one of yours. QueryLane selects a match itself when a connection of the same type has the same id, the same name, or the same host, port and database. Pick another connection if the match is wrong. For connections that can switch databases, you also choose the database to use instead of the one in the file. Steps left without a connection must be set up after the import.

Secret variables lists the variables whose values were left out. Fill them in now or later in the job. When you replace a job, empty fields keep the values you already have.

JavaScript packages lists npm packages the steps need that are not installed. Click Install next to each.

Plugins lists the plugins the jobs use, with their state and the permissions they get. Install, set up or enable them here. Presets from the file are added to your plugin settings; presets you already have stay as they are.

Use folders and tags from the file puts new jobs into the folders and tags from the file and creates the missing ones.

Jobs run on your Mac with your access to files, the network and databases. Import files only from people you trust.

Limits

A file holds up to 500 jobs and 20 MB. A file made in a newer version of QueryLane opens only after you update the app.

Agents connected over MCP can use the same format with querylane_jobs_export and querylane_jobs_import.