This guide walks you through importing a Katapult job into Cloneable using an existing configuration. Once imported, the job's poles, spans, and connections will appear on the map and be ready for your field crews to collect data. When fieldwork is complete, the data can be exported back to Katapult.
Looking to set up your configuration first? See How to Import a Katapult Model into Cloneable.
In This Guide
Before You Start
Make sure you have the following:
A Katapult model configuration already imported into Cloneable (with import and export triggers assigned)
Your Katapult API key (if this is your first job import, you will be prompted to enter it)
The Katapult job/project you want to import already created in Katapult
Verified data in Katapult — confirm all poles are present and the aerial path is in place before importing. What goes in is what you get out, so clean up the Katapult data before triggering the import.
Note: If you have not yet imported a Katapult model configuration, complete that step first. See How to Import a Katapult Model into Cloneable.
Step 1: Choose Job Type
From the Cloneable dashboard, navigate to Create Job. You will see two options:
Import from Katapult — Import pole and span data directly from your Katapult project, including all existing measurements and locations
Create Blank Job — Start with an empty job and add poles manually or import from other sources
Select "Import from Katapult" and click "Get Started".
Step 2: Connect Your Katapult API Key
If your organization has already connected a Katapult API key, this step will be skipped automatically and you will see a green "API Key Connected" confirmation. Click "Continue" to proceed to Step 3.
If this is your first time, you will see a "Connect to Katapult" screen with a field labeled "Katapult API Key". To find your key in Katapult:
Log in to your Katapult account
Click the Apps icon in the top right (just to the left of your user icon)
Click Home to see the API key section
Copy your existing API key, or create a new one
Back in Cloneable, paste the key into the "Katapult API Key" field
Click "Save and Continue"
Note: Your API key is encrypted and stored securely. It is shared across your entire organization, so this only needs to be done once. If you do not see the API key section in Katapult, refer to Katapult's guide on extending the platform.
Step 3: Select a Configuration
Choose which configuration this job should use. Configurations define how data is structured, what attributes are collected, and how information maps between Cloneable and Katapult. For details on configuring visualizations such as icon colors and conditional rules, see Setting Up Conditional Map Styles and Icons.
You will see a list of your available configurations, each showing badges for the templates and triggers it includes (e.g., Pole Template, Span Template, Import Trigger, Export Trigger). If you have more than a few configurations, a search bar will appear to help you find the right one.
Important: Only configurations with an import trigger assigned will appear in this list. If you do not see any configurations, you may need to import a Katapult model first or verify that your configuration has an import trigger.
If you need to create a new configuration, click "Import New Configuration" to start the model import process. You will be returned to the job creation wizard when finished.
Select your configuration and click "Continue".
Step 4: Select a Katapult Job
Cloneable will connect to your Katapult account and retrieve a list of your available projects. Click "Select a job" to open the dropdown, then search for and select the Katapult job you want to import.
After selecting a job:
The Job Name field will automatically fill in with the Katapult project name
You can customize the name if you prefer something different in Cloneable
Both a selected Katapult job and a job name are required to continue.
Note: Each Katapult project can only be imported once. If you need to re-import a project, archive the existing job first.
Step 5: Review & Create
The review screen shows a summary of everything you have selected:
Field | What It Shows |
Job Type | Katapult Import |
Job Name | The name you entered or customized |
Description | Optional description, if provided |
Katapult Project | The selected Katapult job name |
Katapult Job ID | The Katapult project identifier |
Configuration | Your selected configuration, with its template and trigger badges |
Below the summary, you will see a note confirming that the import will start automatically after the job is created and may take a few minutes depending on project size.
Verify the details are correct, then click "Create Job & Start Import".
After Import: What to Expect
After you click "Create Job & Start Import," you will see a confirmation message and be taken back to the dashboard. Here is what happens next.
The Import Process
The import begins automatically in the background. Cloneable pulls in all poles, spans, connections, and associated data from Katapult based on your configuration. You do not need to stay on the page. Import time depends on the size of the Katapult project.
Once the import is complete, the data will appear in the job. You can check by opening the job and looking for your poles and spans on the map.
Changing the Job Status
Imported jobs start with a Draft status. Before heading to the field, take a quick look at the map to verify everything imported correctly, then change the status to In Progress. In the job list on the dashboard, click the status column and select In Progress from the dropdown.
Note: Statuses are a visibility tool for your team. Draft means not started, In Progress means actively being worked, Completed means fieldwork is done, and Cancelled means the job was voided. Changing a status does not trigger anything in the system.
Getting the Job to Field Crews
Once the import is complete, the job will be available to fielders in the Utility Scout app. Fielders should sync on good WiFi before heading to the field to ensure they have the latest data on their device.
Managing Your Job
From the job list, you can:
Edit the job name, description, or other details
Archive a job when it is no longer active (archived jobs can be restored later). For more on archiving, searching, and organizing jobs, see Job Management: Archiving, Searching, and Organizing.
Exporting Data Back to Katapult
Once your fielders have completed their work, you can export data back to Katapult. If your configuration has an export trigger assigned, you can track export progress from the job detail view, including:
How many items have been exported vs. how many remain
Export execution history with status for each batch
For step-by-step export instructions, see How to Export a Job to Katapult.
Troubleshooting
Issue | What to Check |
No configurations appear in Step 3 | Make sure your configuration has an import trigger assigned. Configurations without an import trigger will not appear for Katapult job imports. |
No Katapult jobs appear in the dropdown | Verify your API key is correct. You may need to re-enter it if it was recently regenerated in Katapult. |
Data does not appear in the job after waiting | If the import encountered an error, you may see a notification when the job was created. Contact Cloneable support with the job name and Katapult project ID for help. |
Data looks incomplete after import | Check your configuration's model element selections. Only the node types, connection types, and attributes you selected during model import will be pulled in. |
Fielders do not see the job on their device | Make sure the import has finished (open the job and check if data is on the map). Fielders should sync on good WiFi to see the new job. |
Error when importing a job that was previously imported | Each Katapult project can only be imported once. Archive the existing job first, then re-import the Katapult project. The original job must be archived before a new import will work. |
Map or data downloaded incorrectly | Archive the job in Cloneable and re-import. Archived jobs can be cleaned up on the admin side. |
Tips & Reminders
Verify your Katapult data is clean before importing. Poles, spans, and aerial paths should all be in place.
Your Katapult API key is shared across your organization. It only needs to be entered once.
You can import multiple Katapult jobs using the same configuration, but each Katapult project can only be imported once.
The import runs in the background. You do not need to stay on the page.
Change the job status from Draft to In Progress before sending fielders out.
If your configuration changes after a job is imported, fielders should sync in the Utility Scout app to pick up the updates.
Archive completed or inactive jobs to keep your job list organized. Archived jobs can be restored at any time.
The attributes selected in your configuration determine what gets collected in the field and what gets exported back to Katapult.