I’m trying to create a new Zapier integration using the command line tool. When I run zapier init myapp, it throws an error about not finding a file.
Error! ENOENT: no such file or directory, open C:\Users\MYNAME:\Users\myname\AppData\Local\Temp\tmp-123456ABC\zapier-template.zip
The path looks weird with the username appearing twice. I’m on Windows 7 and it seems like the CLI is building the file path incorrectly. Has anyone encountered this before or know a workaround? I just want to get started with building my first Zapier app but this error is blocking me from creating the initial project structure.
looks like a classic windows path parsing bug to me. i had this exact issue last month and what worked was clearing the npm cache first with npm cache clean --force then trying the zapier init again. sometimes the cli gets confused about temp folder locations when theres cached data messing with it. worth a shot before doing the more complex fixes the others mentioned
I ran into something similar on an older Windows machine and it turned out to be related to how the CLI handles temporary directories. The double username in your path suggests there’s an issue with environment variable resolution. Try running the command prompt as administrator first - that fixed it for me about half the time. If that doesn’t work, you might need to manually set your TEMP environment variable to a simpler path without spaces or special characters. I ended up creating a folder like C:\temp and pointing my TEMP variable there temporarily just to get past the initialization. Windows 7 can be finicky with newer Node.js applications like the Zapier CLI, so you might also want to check if you’re running a compatible Node version.
That path issue is definitely a Windows-specific bug I’ve seen before. The CLI is concatenating path components incorrectly which explains why you’re seeing the username duplicated. Before trying the administrator route, check if your username has any spaces or special characters - the CLI sometimes chokes on those. I had success by temporarily switching to a different user account with a simple name like ‘dev’ or ‘test’ just for the initialization step. Another option is to run the command from a different directory entirely, maybe something like C:\projects instead of your user directory. The Zapier CLI pulls templates from their servers and extracts them locally, so the temp directory resolution is crucial. If you’re still stuck, you could try using WSL or a virtual machine with a Linux distribution - the CLI tends to be more reliable there.