Some of what Cloneable does on your behalf happens against other systems. Pulling jobs from Katapult is the common one. For that to work, Cloneable needs a credential from that system, stored in your organization.
This is where those live. Cloneable describes it as managing your organization's secrets and API keys.
Getting there
Open your settings and go to Secrets Vault. You need administrator access.
Two kinds, and you probably want the first
Platform Secrets are credentials for a connected system, like Katapult.
Trigger Secrets are for automations you have had set up.
Cloneable keeps them on separate tabs, and each list shows a name, a description and when it was created.
Adding a Katapult credential
Choose Create Secrets.
Choose Add Platform Secrets.
Pick Katapult from the list of platforms. Each one tells you how many credentials it expects, so you know what you commit to.
Cloneable fills in the name of the credential it needs. You supply the value, and a description if it will help whoever looks at this next.
Choose Save All Secrets.
Cloneable confirms when they are saved.
Video: Setting Up Katapult API Secrets and Triggers
Two details worth knowing before you start:
Saving is all or nothing. The save stays unavailable until every row has both a name and a value, so a half-filled row blocks the whole batch rather than saving what it can. If the button looks stuck, an empty field is why.
Cloneable also offers Roboflow and a blank custom option, alongside Katapult. Use Custom only if we have asked you to, since it means naming the credential yourself and the name has to match what the integration expects.
You will not be able to read the value back
Once a credential is saved, the lists show its name, its description and its date. They never show the value again. That is deliberate, and it is the right behavior for something like this.
The practical consequence: keep the original wherever your team normally keeps credentials. If you lose it, the recovery is to generate a new one in the other system and replace it here, not to look it up in Cloneable.
Do not send credentials to us by email or chat, and do not paste them anywhere outside this page. If you need us to set one up, ask and we will tell you how to hand it over safely.
Changing one
Update it in place and give it the new value. Cloneable confirms the update, or tells you plainly if it failed.
Deleting one, and please be careful here
Deleting a credential can quietly break something that worked before. A trigger that depended on it, or your Katapult connection, will simply stop, and the failure will show up somewhere else entirely rather than on this page.
Read the name before you start, not after. You will most likely get a confirmation step naming the credential and telling you the action cannot be undone. That step offers you no button to back out with. It has one control on it and that control deletes.
So treat opening it as the decision. Check the name twice first, and if you remove one to replace it, add the replacement first.
Why this matters more than it looks
If your organization has no valid Katapult credential stored, creating a job that pulls from Katapult fails, and the error mentions neither Katapult nor credentials. It talks about loading jobs, and retrying does not help.
So if someone reports that, this page is the answer. See Error loading jobs when importing from Katapult.
Store your Katapult API key before you import your configuration, not just before your first job. The import asks you to choose an import trigger and an export trigger, and we set those up against your stored key. Without it there is nothing to choose at that step. See What you need before you start (Katapult).