Applies to: Katapult customers. If your organization does not use Katapult, you can skip this article.
In this guide
Cloneable handles this entirely. What you provide: the secret from the secrets vault.
A trigger is the automation that actually moves data between Cloneable and your Katapult account: it pulls a Katapult job's data into Cloneable when you import, and it writes your field data back to Katapult when you export. It is the engine behind the round trip described in Getting Started as a Setup Admin / Implementer. Trigger setup is handled entirely by Cloneable; it is not something you do yourself.
What you do, and what Cloneable does
Setting up the Katapult connection is a two-part job with a clear division of labor:
You put your Katapult API key (and, if needed, your private Katapult domain address) into the secrets vault.
Cloneable then creates the import and export triggers for your organization, attaches your secret to them, and connects them to your configuration.
Trigger setup is handled entirely by Cloneable. You do not build, configure, or manage triggers yourself. Your only job here is to make sure your Katapult key is in the secrets vault first, then let your Cloneable contact know you are ready for them to wire it up.
Why the order matters
The trigger uses your stored Katapult key to sign in to Katapult, so the key has to exist before the trigger can work. If a trigger runs without the key in place, it cannot authenticate and the export fails. There is a second reason the order matters: when you go to create a Katapult job, only configurations that already have an import trigger connected will be available to choose. That connection is part of what Cloneable wires up. So the sequence is always: your secret first, then Cloneable wires the trigger and connects it to your configuration, and only then is that configuration ready to import Katapult jobs.
How to tell it is working
From your side, the sign that the trigger is working is simple: Katapult jobs import cleanly, and exports back to Katapult complete. The Exports tab (Issues & Status) on your dashboard, covered in the Work in the web portal section, shows export progress, success and error counts, and a list of any export issues to work through. Cloneable also has a detailed trigger dashboard and logs on their side for deeper troubleshooting.
If it is not working
If imports or exports are failing, contact Cloneable with your organization name, the configuration or job name involved, and a short description of what you saw (a screenshot of the error helps). Common causes are a missing or expired Katapult key, or a private-domain customer whose domain address was not set. Because the trigger is Cloneable's to manage, they can inspect the logs and re-run it for you.