How to Pull Zapier App to Local Machine and Include Additional Trigger Fields

Other Questions Zapier
1

I have a live Zapier app that I want to get onto my computer so I can make some changes. I already created a deploy key and used zapier login --sso to sign in.

I looked through the docs but I’m not sure how to get my app from Zapier’s servers to my local folder. I saw the zapier link command but it doesn’t seem like what I need.

Can anyone help me figure out how to download my app safely without breaking anything in production? Since it’s live, I can’t just try random commands.

Also, I want to add some extra fields to one of my triggers, but when I try to edit it in the Zapier developer dashboard, I get an error saying “This version was created by the CLI and can only be modified there.”

I need to include these fields in my trigger:

const fetchData = (z, bundle) => {
  const result = {
    item_id: bundle.cleanedRequest.item_id,
    title: bundle.cleanedRequest.title,
    custom_property: bundle.cleanedRequest.title, // New field I want to add
    extra_data: bundle.cleanedRequest.title, // Another new field
    // More fields here...
  };
}

Any help with these steps would be awesome. Thanks!

2

yeah theres no way to download existing apps from zapier unfortunately. i had to rebuild mine manually last month which was annoying but doable. just use the dev dashboard to see ur current setup and recreate it locally with zapier init. for the trigger fields, make sure you add them to outputFields array not just the function. test everything localy first before pushing!

3

Unfortunately, you cannot pull an existing Zapier app from their servers back to your local machine. The zapier link command you mentioned is actually for connecting a local app directory to an existing app on Zapier’s platform, not for downloading. What you need to do is recreate your app locally from scratch. Start by running zapier init to create a new project structure, then you’ll have to manually rebuild your triggers, actions, and authentication based on what’s currently live. This is tedious but necessary since Zapier doesn’t provide a download feature. For your trigger fields issue, once you have the local version set up, you can modify your trigger’s outputFields array to include the new fields you want. Make sure to update both the sample data and the actual trigger function. After testing locally with zapier test, push a new version using zapier push and then promote it when ready. I went through this same process last year with one of my apps and it took about a day to reconstruct everything, but it’s definitely doable if you have documentation of your current setup.

4

Unfortunately, you cannot download your existing Zapier app directly from their servers. Since you have access to the CLI, you’ll need to recreate your app by reviewing it in the developer dashboard and building it locally. Begin with zapier init to set up a new project structure, and then manually reconstruct your triggers and actions based on the current setup visible in the dashboard.

For including new trigger fields, update the outputFields in your trigger configuration once your local version is prepared. Make sure those fields are defined in the trigger’s metadata, rather than just within the sample data function. After local reconstruction, thoroughly test with zapier test before you push a new version. I faced a similar situation six months ago, finding the process quite detailed yet manageable if documented carefully.