Skip to content
GeoJibe

Save a workflow as a Job

Save a Job when you want to use a workflow again. You do not need a Job to convert a file once.

Then click Save as Job.

Tip

Just converting a file once? You don't need to save a Job.

What GeoJibe remembers

A Job stores the Source, any processing (Convert, Transform, Python), and the Destination.

Next time you Run Now, GeoJibe repeats that workflow with the current data from the Source.

Before you start

  • Sign in
  • Use a saved Source (URL, HTTP/API, S3, FeatureServer, PostGIS, SQL Server, MySQL / MariaDB, Oracle Spatial, GeoServer, GeoNode, or Hub). Upload and DuckDB cannot be saved as a Job Source — there is no file sitting on the server waiting for next week.
  • Use a saved Destination other than Download or DuckDB. Scheduled and saved Jobs deliver to PostGIS, SQL Server, MySQL / MariaDB, Oracle Spatial, S3, SFTP, GeoServer, GeoNode, or Webhook.

One-off Upload → Convert → Download stays on the Canvas. It is not a Job.

1. Build the workflow

On the Canvas, add the Source, optional processing, and Destination. Import/inspect until every card says Configured.

2. Save as Job

Click Save as Job.

  1. Enter a Name, such as Neighborhoods Import.
  2. Choose a Schedule, or leave Manual / No schedule if you will only click Run Now.
  3. Optionally enable Notifications (email and/or a notification webhook). Failure notices are recommended; success notices are off unless you turn them on.
  4. Click Save Job.

You can also create a Job from Jobs → Add Job → Build Manually.

3. Run it again

Open Jobs, find the row, and click Run Now.

Enable / Disable only controls the schedule. A disabled Job can still use Run Now.

What happens next?

The Job appears on the Jobs list with its last run. Open Runs for history.

To change it, Edit (Canvas) or Classic editor. Click Save changes.

See also