Beginner

Integrations Overview

Connect Tapioca with your development tools for seamless workflow automation and comprehensive time tracking.

Tapioca integrates with your existing development workflow to automate time tracking, link code changes to tasks, and provide evidence of work. This section covers the Git-based integrations that power developer workflows.

Available Git Integrations

Core Concepts

Evidence-Based Time Tracking

Tapioca uses your Git activity as evidence for time tracking. When you make commits, open pull requests, or participate in code reviews, these events are automatically captured and can be linked to tasks.

Why evidence matters:

  • Verification - Prove that work was done during reported time
  • Accuracy - Catch forgotten time entries by reviewing Git activity
  • Automation - Auto-link commits mentioning task IDs
  • Compliance - Audit trail for billing and reporting

Task Linking

Connect Git activity to Tapioca tasks in several ways:

MethodExampleAutomation Level
Task ID in commitgit commit -m "Fix bug TAP-123"Automatic
Task ID in branchfeature/TAP-123-new-loginAutomatic
Task ID in PR title[TAP-123] Add new featureAutomatic
Manual linkingLink in Tapioca UIManual

Consistent Naming

Adopt a consistent commit message or branch naming convention across your team. This enables automatic task linking without any manual intervention.

Webhook Events

Both GitHub and GitLab send webhooks to Tapioca when events occur:

Pull Request / Merge Request Events:

  • Opened β†’ Creates evidence, can move task to β€œIn Progress”
  • Merged β†’ Creates evidence, can move task to β€œReview” or β€œDone”
  • Closed β†’ Creates evidence, optionally closes task

Code Review Events:

  • Review submitted β†’ Creates evidence of code review work
  • Comments added β†’ Creates evidence of collaboration

Commit Events:

  • Push received β†’ Links commits to tasks based on message patterns

Getting Started

1

Choose Your Provider

Set up GitHub, GitLab, or both based on where your code lives

2

Install the Integration

Follow the provider-specific setup to connect your organization

3

Map Repositories

Link Git repositories to Tapioca projects for automatic association

4

Configure Automation

Set up automatic task status updates and linking rules

Integration Features Comparison

FeatureGitHubGitLab
PR/MR to Task Linkingβœ…βœ…
Commit Linkingβœ…βœ…
Code Review Evidenceβœ…βœ…
Issue Importβœ…βœ…
CI/CD Pipeline Trackingβœ…βœ…
Two-way Syncβœ…βœ…
Self-hosted SupportGitHub EnterpriseGitLab CE/EE
Time Tracking Syncβ€”βœ…

Multiple Providers

You can connect both GitHub and GitLab to the same Tapioca organization. This is useful if your team uses different platforms for different projects.

Security & Permissions

Tapioca follows the principle of least privilege:

  • Read Access - View repositories, commits, PRs/MRs
  • Webhook Events - Receive notifications of code changes
  • No Write Access - We don’t modify your code or repository settings (unless explicitly enabled)

All webhook payloads are verified using cryptographic signatures to ensure authenticity. See Security for more details.

Next Steps

Was this page helpful?

Let us know how we can improve