---
title: "Go From Slack to Pull Request in One Reply"
description: "Tag @flowsery on a bug alert to go from Slack to pull request: it reads the failing session, changes your repo and opens a draft PR for review."
url: "https://flowsery.com/features/slack-to-pull-request"
---

# Reply to the Alert and Go From Slack to Pull Request

Tag @flowsery on an issue alert to go from Slack to pull request without opening your editor. Flowsery reads the failing session, changes the code on its own branch, runs your test command and opens a draft PR in GitHub.

[Start Free](https://flowsery.com/signup)[See Pricing](https://flowsery.com/pricing)

Guardrails

### It Works on Its Own Branch, Inside the Paths You Allow.

Flowsery reads your code, pushes to its own branches and opens pull requests. You set the allowed and denied paths per repository, CI config, lockfiles and secrets are always blocked, and **nothing reaches your default branch unless you merge it**.

Review

### A Draft PR With the Session Attached, Waiting on You.

Every fix arrives as a draft pull request that links the session it came from, runs through your normal checks and merges only when you approve it. **Flowsery never merges its own work**.

Auto mode

### Or Skip the Reply and Let It Open the PR on Its Own.

Turn on Auto pull requests and Flowsery **opens a draft PR for each new issue** at or above the severity you choose, one draft per repository changed. Team includes 10 fix PRs a month and Pro includes 30.

## Frequently Asked Questions

### 

### 

### 

### 

### 

### 

## Turn Your Next Alert Into a Pull Request

Connect Slack and your GitHub repository, then answer the next bug alert with a reply instead of a sprint ticket.

[Start Free](https://flowsery.com/signup)[See Alerts & Tickets](https://flowsery.com/features/automatic-bug-tickets)