​

Cycle Integration

BuildBetter’s Cycle integration enables automatic recording and analysis of product development meetings, allowing you to track discussions around features, bugs, and development cycles directly within your Cycle workflow.

​

Features

• Automatic Meeting Recording: Record all your Cycle sprint planning and review meetings
• Task-Focused Organization: Automatically link recordings to relevant Cycle tasks and sprints
• Development Context: Connect meeting recordings to your existing development cycles
• Transcript Tagging: Tag transcript segments with relevant Cycle tasks and issues
• Sprint Documentation: Automatically document sprint discussions and decisions

​

Setup Instructions

​

Prerequisites

• An active BuildBetter account
• Cycle account with appropriate access
• Admin permissions in both platforms

​

Connecting Cycle

1. Navigate to Settings → Integrations in your BuildBetter dashboard
2. Select Cycle from the recording integrations
3. Enter your Cycle API key
4. Select the workspace and team you want to connect
5. Configure visibility and access settings
6. Click Connect to activate the integration

​

Configuring Recording Rules

After connecting:

1. Go to Settings → Integrations → Cycle → Recording Rules
2. Configure which Cycle meetings to record:
   • Sprint planning
   • Sprint reviews
   • Backlog refinement
   • Daily standups
3. Set up automatic tagging rules for different meeting types
4. Save your configuration

​

Usage

​

Recording Sprint Meetings

Once connected, BuildBetter will:

1. Detect scheduled Cycle meetings from connected calendars
2. Automatically join and record meetings based on your rules
3. Process transcripts with speaker identification
4. Link recordings to the appropriate sprint and tasks
5. Generate AI summaries focused on development context

​

Task Reference

Link meeting discussions to specific Cycle tasks:

1. During transcript review, select relevant segments
2. Click Link to Cycle Task
3. Search for and select the appropriate task
4. Add an optional note or context
5. Save to create a reference visible in both BuildBetter and Cycle

​

Sprint Documentation

Generate sprint documentation from meetings:

1. After sprint review meetings, go to the meeting recording
2. Click Generate Sprint Documentation
3. Select which aspects to include (decisions, action items, blockers)
4. Review and edit the generated document
5. Push to Cycle as sprint documentation

​

Advanced Features

​

Development Insights

Extract key development insights from recorded meetings:

1. View the Insights tab on any Cycle-linked recording
2. See AI-detected:
   • Feature scope changes
   • Technical decisions
   • Blockers and risks
   • Action items by team member
3. Export insights to Cycle as task comments or documentation

​

Automatic Task Creation

Create Cycle tasks directly from meetings:

1. During transcript review, identify action items or new tasks
2. Select relevant transcript sections
3. Click Create Cycle Task
4. Fill in task details, leveraging content from the selected segment
5. Assign to team members and set due dates
6. Submit to create the task in Cycle

​

Troubleshooting

​

Connection Issues

• Verify your Cycle API key is valid
• Check permissions in your Cycle account
• Ensure proper workspace selection

​

Meeting Detection

• Verify calendar integration is active
• Check that meeting titles include Cycle-related keywords
• Ensure the meeting is associated with a Cycle sprint

​

Task Linking Problems

• Verify proper authentication between platforms
• Check that task IDs are correctly formatted
• Ensure you have access to the target task

​

Use Cases

​

Development Teams

• Document technical decisions in sprint planning
• Create traceable links between discussion and implementation
• Ensure context doesn’t get lost between meetings

​

Product Management

• Record feature discussions linked to their development tasks
• Track how requirements evolve during development
• Document reasons behind priority or scope changes

​

Quality Assurance

• Link bug discussion context to testing tasks
• Document reproduction steps mentioned in meetings
• Create clear references between issues and their resolution discussions