Where: web portal, Settings, then Secrets vault. Needs: the Org Admin role.
When you finish: your Katapult API key is saved, which lets Cloneable pull jobs from Katapult and send work back. Do this before the Katapult import, so the key is already there when you reach its Connect Katapult step.
Do this before the Katapult import. The import's Connect Katapult step chooses the two automations that move jobs out of Katapult and finished work back in. They run against your stored key, so if no key is stored yet, that step asks you for one first.
Add your Katapult key
Open your settings and choose Secrets vault.
Choose Create secrets, then Add platform secrets.
The Secrets vault, with Create secrets ringed.
Pick Katapult from the list of platforms. Cloneable fills in the name it needs.
Select platform: Roboflow, Katapult and Custom.
Paste the key value. Add a description if it will help whoever looks at this next.
Choose Save all secrets. Cloneable confirms with "Secrets created successfully".
Opening Create secrets and the platform list.
Good to know | Detail |
Two tabs | Platform secrets are credentials for a connected system like Katapult. Trigger secrets are for automations we have set up for you. You almost always want the first. |
Saving is all or nothing | Save stays greyed out until every row has a name and a value. If it looks stuck, an empty field is why. |
Other platforms | Cloneable also lists Roboflow and a blank Custom option. Use Custom only if we have asked you to; the name has to match what the integration expects. |
You cannot read a value back | After saving, the list shows name, description and date, never the value. Keep the original wherever your team keeps credentials. If you lose it, generate a new one in Katapult and replace it here with Edit. |
Saving is all or nothing: Save all secrets stays greyed until every row has a name and a value.
Never send us a credential by email or chat, and do not paste it anywhere outside this page. If you need us to set one up, ask and we will tell you how to hand it over safely.
Change or delete a key
Change: choose the pencil Edit button on the key, paste the new value in the "New value" box, and choose Save. Cloneable confirms with "Secret updated successfully". If that message does not appear, the new value did not save.
Edit opens a New value box, with Cancel and Save.
Delete: read the name twice first. The confirmation names the key and has two buttons, Cancel and Delete secret. Deleting quietly breaks anything that depended on the key, and the failure shows up somewhere else entirely, not on this page. If you are replacing a key, use Edit instead. Do not delete it or add a second one: Cloneable refuses a second key with the same name, keeps the old one, and this page shows no error when that happens.
Why this matters more than it looks
Cloneable checks only that a key is saved, not that Katapult accepts it. The message "Katapult API key connected" means a key is saved, nothing more. To know the key really works, check three things:
Your models load in the Model list when you bring in a model from Katapult.
Your Katapult jobs load when you choose Add job, then Import from Katapult.
A test export finishes with no issues on the Exports tab. Use a test job, because an export writes to Katapult.
If no key is saved, the job wizard asks for one in an API key step. If a key is saved but Katapult does not accept it, the wizard shows "Katapult jobs couldn't be loaded." with Try again. Make a new key in Katapult, then choose Edit on the key here. See "Error loading jobs" when I import from Katapult.
Related