Integrations

Your tools. One pipeline.

Connect ticket trackers, AI providers, CI/CD services, design tools, and notification channels. Each integration maps to canvas nodes you can drag into any phase.

Ticket Sources

Import work from anywhere

Start a flow unit by picking a ticket from a connected source. Recent tickets are pre-loaded. Search across projects. Or enter a ticket manually with AI-enhanced descriptions.

JR

Jira Cloud

REST v3 + ADF rendering. Import issues with full description, labels, and sprint data.

Scope phase

LN

Linear

GraphQL API. Import issues with labels, cycles, and project context.

Scope phase

NT

Notion

Import database items as tickets. Supports rich text properties.

Scope phase

SE

Sentry

Import error events as flow units. Stack traces become scope context.

Scope phase

CL

Crashlytics

Import crash reports with device info, OS version, and stack traces.

Scope phase

GH

GitHub Issues

Import issues with labels, milestones, and linked PRs.

Scope phase

AI Providers

8 LLM providers. Your keys.

All AI calls go direct from the plugin in your IDE to the provider API. Bring your own key (BYOK) -- or use Gemini Flash free for your first 10 flow units. Ollama runs entirely local.

CL

Claude (Anthropic)

AnthropicConnector. BYOK required.

Planning / Implementing / Reviewing

GP

GPT-4o (OpenAI)

OpenAI-compatible connector. BYOK required.

Planning / Implementing / Reviewing

GM

Gemini Flash (Google)

Free for first 10 flow units. No key needed to start.

Planning / Implementing / Reviewing

MS

Mistral Devstral

OpenAI-compatible connector. BYOK required.

Planning / Implementing / Reviewing

GQ

Groq

Ultra-fast inference. OpenAI-compatible. BYOK required.

Planning / Implementing / Reviewing

DS

DeepSeek

OpenAI-compatible connector. BYOK required.

Planning / Implementing / Reviewing

OL

Ollama

100% local. No API key. No data leaves your machine.

Planning / Implementing / Reviewing

OR

OpenRouter

Multi-model gateway. Access many models through one key.

Planning / Implementing / Reviewing

CI/CD and Delivery

Build, test, and ship

Testing (CI) and Distribution (CD) are separate phases with distinct node types. Run tests locally or trigger remote pipelines. Deploy to any app distribution channel.

GA

GitHub Actions

Trigger workflows. Monitor runs. Gate on CI status.

Testing + Distribution

CC

CircleCI

Trigger pipelines. Wait for build status.

Testing + Distribution

BR

Bitrise

Mobile-first CI/CD. Trigger builds for Android and iOS.

Testing + Distribution

FB

Firebase App Distribution

Upload APK/AAB. Distribute to internal testers.

Distribution

TF

TestFlight

Upload iOS builds for beta testing.

Distribution

PS

Play Store

Publish to internal, alpha, beta, or production tracks.

Distribution

AS

App Store

Submit iOS builds for App Store review.

Distribution

Design and Collaboration

From design to code to notification

Extract design tokens from Figma. Create PRs on GitHub or GitLab. Post summaries back to tickets. Notify the team on Slack.

FG

Figma

Extract styles, components, and design tokens. Convert frames to Jetpack Compose or SwiftUI.

Planning + Designing

GH

GitHub

Create branches, apply patches, open pull requests. PRCreator with full diff support.

Implementing + Reviewing

GL

GitLab

PRCreator support for GitLab merge requests.

Implementing + Reviewing

GR

Gradle

Build verification via ProcessBuilder. Explicit arg arrays -- never shell concat.

Reviewing + Testing

SK

Slack

Notify channels on phase completion, checkpoint approval, or distribution success.

Distribution

TC

Ticket Commenter

Auto-post flow unit summaries back to the originating ticket (Jira, Linear).

All phases