Auto-Sync Configuration
Auto-sync uses GitHub webhooks to automatically trigger syncs when Figma Make pushes changes.
How It Works
- Figma Make pushes to its auto-created repository
- GitHub sends a webhook to GitFig server
- GitFig syncs changes to your target repository
- You receive the changes as a PR or direct push
Setting Up Webhooks
Step 1: Get Your Webhook URL
The GitFig webhook URL is:
https://oauth.gitfig.com/api/webhooks/github
Step 2: Generate a Secret
Generate a secure webhook secret:
openssl rand -hex 32
Save this secret - you'll need it for both GitHub and GitFig.
Step 3: Configure on GitHub
- Go to your Make repository on GitHub
- Click Settings → Webhooks → Add webhook
- Fill in the fields:
| Field | Value |
|---|---|
| Payload URL | https://oauth.gitfig.com/api/webhooks/github |
| Content type | application/json |
| Secret | Your generated secret |
| SSL verification | Enable |
| Events | "Just the push event" |
- Click Add webhook
Step 4: Verify Webhook
GitHub shows a green checkmark when the webhook is working. If you see a red X, check the recent deliveries for error messages.
Webhook Security
The webhook secret ensures only GitHub can trigger syncs:
- GitFig validates the
X-Hub-Signature-256header - Invalid signatures are rejected with 401 Unauthorized
- This prevents malicious sync triggers
Monitoring Syncs
View sync history in GitFig:
- Open the Make Bridge tab
- Click "History" to see recent syncs
- Each entry shows status, timestamp, and commit info
Troubleshooting
Webhook not triggering
- Check webhook is configured on the Make repo (not target)
- Verify the secret matches
- Check GitHub webhook delivery logs
"Signature verification failed"
- Webhook secret doesn't match
- Reconfigure with the correct secret
Sync fails but webhook works
- Check GitFig has access to both repositories
- Verify sync strategy settings