✅ Quick Summary
Push44 authenticates with Zite using your session and CSRF tokens, fetches your project's complete snapshot template files, and pushes them to GitHub.
The Problem
Zite projects contain sophisticated template files and component definitions. Without export capability, all that AI-generated structure stays inside Zite's platform.
How Push44 Solves It
Push44 authenticates with Zite using your session and CSRF tokens, fetches your project's complete snapshot template files, and pushes them to GitHub.
Step-by-Step Guide
Get your Zite session credentials
Open Zite in your browser. In Developer Tools (F12), go to Application → Cookies and find 'connect.sid' (your session ID) and 'fillout-csrf-token' (your CSRF token). Copy both.
Connect Zite in Push44
In Push44, select Zite and enter your session ID and CSRF token. Push44 proxies the Zite API through its dev server to avoid CORS issues.
Select your Zite app
Push44 loads your Zite workspace and apps. Select the app to export. Push44 reads the app's snapshot template — the complete file structure.
Push to GitHub
Configure your GitHub repository and push. All Zite template files are committed to your repo.
Pro Tips
- Zite tokens expire with your browser session — get fresh tokens if Push44 shows auth errors.
Common Mistakes to Avoid
- Forgetting that Zite needs both the session AND CSRF token — entering only one will fail.
Ready to Export?
Push44 is free, open source, and takes under 2 minutes to set up.