Skip to main content
Turn voice-captured feedback, customer requests, and bugs directly into GitHub issues with full context and automatic labeling. Perfect for engineering teams who want retroactive batch processing with review-then-create workflows.
🟡 In Review — Coming soon to Zapier directory. Learn more about the template.

​
What It Does

This template uses a unique “Tag Attached” trigger, allowing you to capture multiple notes and batch-create GitHub issues when you’re ready. Perfect for converting customer interviews, feature requests, and feedback sessions into organized, tracked engineering work without manual transcription or issue creation.

​
How It Works (Retroactive Batch Processing)

This template is different from others—it uses tag-based triggers instead of automatic processing:
1

Voice Capture (Anytime)

Create Cleft notes whenever inspiration strikes—during calls, meetings, or sessions. No immediate action needed.
2

Add Checkboxes

Include checkboxes for items you want to track:
- [ ] Add dark mode to editor
- [ ] Improve search performance
- [ ] Fix mobile rendering bug
3

Save & Move On

Notes are saved. No automation yet. Use them as context-rich notebooks.
4

Review & Tag

Later (minutes, hours, or days), tag the notes with “tasks” when you’re ready to create issues
5

Extract & Process

Automation runs immediately on all checked items in that note
6

Issues Created

Each checkbox becomes a GitHub issue with “from-cleft” label and source link back to your note

​
Key Differences from Other Templates

FeatureGitHubOther Templates
TriggerTag Attached (retroactive)Note Created (immediate)
ProcessingBatch when you add “tasks” tagAutomatic on every note
ControlReview before creatingAutomatic, hands-off
Best ForIntentional, curated workflowsContinuous capture
Use CaseFeature requests, customer feedbackDaily task capture
This retroactive approach is perfect when you want to:
  • Review notes before converting to issues
  • Batch-process multiple related notes at once
  • Capture context that may not immediately need action
  • Control when automation happens

​
Setup Requirements

  • ✅ Cleft Plus subscription
  • ✅ GitHub account with repository access
  • ✅ Zapier account (free tier works)
  • ✅ Permission to create issues in your GitHub repo

​
Installation Steps

  1. Click Install GitHub Template
  2. Connect your Cleft account
  3. Connect your GitHub account
  4. Select your target repository
  5. Configure optional field mapping
  6. Turn on the Zap
Then start using the workflow:
  1. Create notes in Cleft capturing ideas and feedback
  2. When ready, tag them with the “tasks” tag
  3. Automation runs and creates GitHub issues

​
Real-World Examples

​
Example 1: Customer Interview → Feature Backlog

Monday 9 AM: Sarah attends customer calls. She voice-records in Cleft: 
Meeting with Acme Corp - Feature requests from CTO

- [ ] REST API rate limiting configuration
- [ ] Batch export to CSV format
- [ ] SAML/OAuth single sign-on
- [ ] Custom webhook security headers
Monday 4 PM: Sarah reviews her notes and tags with “tasks”. Result: Four GitHub issues created automatically:
  • Title: “REST API rate limiting configuration”
  • Title: “Batch export to CSV format”
  • Labels: “from-cleft” (tracking origin)
  • Source: Link back to original Cleft note
Time saved: 30 minutes (customer interview + transcription + GitHub issue creation)

​
Example 2: Product Review → Sprint Backlog

Weekly Product Meeting: Team discusses roadmap and priorities. Marcus captures in Cleft: 
Q4 Product Review - Engineering asks

- [ ] Refactor authentication module for 2FA
- [ ] Performance optimization for search
- [ ] Fix reported UI glitch in dashboard
- [ ] Add analytics event tracking
- [ ] Update API documentation
After meeting: Marcus tags “tasks”, issues appear in GitHub. Result: Engineering team has 5 new backlog items ready to estimate. Time saved: 40 minutes (note review + GitHub issue creation + team discussion in one place)

​
Example 3: Support → Issue Triage

Support Tickets: Incoming customer bugs via email. Support team voice-logs in Cleft: 
Support intake from email - Critical bugs

- [ ] Users cannot change password
- [ ] Export fails with special characters
- [ ] Mobile app crashes on iOS 16
- [ ] Dashboard widget rendering
Tagged in Cleft: Automation runs. Result: Engineering sees 4 tracked issues with full context and source links. Time saved: 20 minutes per batch (triage + issue creation + context preservation)

​
Advanced: Retroactive Batch Processing

One of the most powerful features: you can tag old notes. This enables:
  • Brainstorm sessions: Capture 30 ideas, tag 5-10 when you’re ready to work them
  • Meeting notes: Tag the important meeting 3 hours later
  • Archive mining: Find old notes and batch-create issues from historical feedback
  • Controlled rollout: Spread work across multiple sprints by tagging over time
This is perfect for teams that want voice capture without being locked into immediate automation.

​
Customization

In Zapier, you can customize:
  • Repository: Change which repo receives issues
  • Labels: Auto-add labels like “from-cleft”, “customer-request”, “feature-request”
  • Assignee: Auto-assign to specific team members
  • Milestone: Assign to sprint milestones
  • Project: Add to GitHub Projects board
Edit the Zap in Zapier to access these options.
The template automatically links back to your Cleft note in the GitHub issue. This gives engineers full context:
  1. They can see the original note text
  2. Understand the source (customer feedback, meeting, etc.)
  3. Jump back to the full Cleft note for details
No context lost, full traceability maintained.
Only certain tags trigger issue creation:
  1. The “tasks” tag is the default
  2. You can add multiple tags (e.g., “tasks” or “bugs” both trigger)
  3. Use different tags for different workflows if needed
This gives you fine-grained control over when automation runs.

​
Checkbox Format

- [ ] GitHub issue title here
- [ ] Another issue to track
- [ ] And one more for the backlog
Requirements:
  • Start with dash and space: -
  • Empty brackets: [ ] (not [x])
  • Text after brackets becomes the issue title
  • One checkbox = one GitHub issue

​
Troubleshooting

  1. Zap is ON: Check Zapier dashboard
  2. Correct tag: Make sure you’re using the “tasks” tag
  3. Checkbox format: Verify - [ ] text format
  4. GitHub connection: Ensure GitHub is properly connected
  5. Check Runs: Look at Zapier’s activity log to see if it triggered
Edit your Zap and select the correct GitHub repository in the “Create Issue” step.
Make sure each checkbox has complete text:
  • Correct: - [ ] Implement user authentication
  • Wrong: - [ ] (empty), - [ ] (just spaces)
Create multiple Zaps, one per repository. Use filters to route notes to the right Zap based on tags or content.

​
Perfect For

  • 👨‍💻 Engineering teams managing customer feedback
  • 🔍 QA teams logging bugs from testing
  • 📦 Open source projects accepting community requests
  • 🚀 Startup teams moving fast from ideas to issues
  • 📊 Product-led companies capturing user requests
  • 🎯 Dev teams doing customer interviews and discovery

​
Why Use GitHub + Cleft?

  • Voice capture: No typing while listening to customers
  • Full context: Keep original notes linked to issues
  • Retroactive control: Tag when ready, not on capture
  • Zero transcription: Automatic extraction from notes
  • Traceability: Every issue links back to source
  • Team alignment: Issues immediately visible to engineering

​
Template Details

  • Template ID: 255679911
  • Status: 🟡 In Review (coming soon)
  • Trigger Type: Tag Attached (retroactive)
  • Target Platform: GitHub
  • Setup Time: ~2 minutes
  • Best For: Customer feedback, feature requests, bug reports

Jira

For enterprise issue tracking

Reflect

For daily note consolidation

Trello

For visual issue tracking

ClickUp

For team-wide project management

​
Support

Ready to capture customer feedback as tracked GitHub issues? View the template → (Coming soon to Zapier directory)