Source

Hosting options & portability — found from sitemap — Zapier

Checked for Zapier on 13 Oct 2026

Technical details

type: page
http status: 200
content hash: sha256:d27c9d04fd72497a78de5850de6f63c246058620e2d8d61fdaebb38e41440323
permission: robots_ok
screenshot: Screenshot on file (internal exhibit, not published)

Cited by

UI to cli export Report an error

“How to migrate a Zapier Developer Platform UI integration to CLI using convert and push commands.”
Convert command Report an error

“zapier convert {your integration id} . --version={integration version you want to convert}”
Deploy command Report an error

“When you’re ready to deploy your CLI version run: zapier-platform push”
Version increment on convert Report an error

“When you created your project with the convert tool we automatically incremented the version you converted.”
UI versions remain editable Report an error

“Your earlier versions, created within the Platform UI, are also still available and can still be edited and used.”
Cli version deletable Report an error

“If you decide that the Platform CLI is not for you, you can delete your new version from Manage > Versions and continue where you left off in the Platform UI.”
Cli advantages source control Report an error

“Easier team collaboration. You’ll be able to check all the code for your Zapier integration into your team’s source control repo.”
Cli advantages automated tests Report an error

“Set up automated regression tests, to catch errors each time you push a change.”
Convert metadata Report an error

“Integrations converted with the zapier convert command will include convertedByCLIVersion in the package.json for informational purposes.”

1 fact read from this page is not shown because it could not be confirmed on the page as captured.