Email to GitHub Issues
Turn support email into GitHub Issues automatically
Scitor converts every inbound support email into a GitHub Issue — sender, subject, body, and attachments included. Your team replies from GitHub with a slash command, and Scitor emails the customer back. No separate helpdesk, no context switching.
The problem with a separate helpdesk
Customer support email and your engineering work happen in two different places. A support ticket about a bug lives in a helpdesk; the code that caused it lives in GitHub. Someone has to manually copy context between the two — paste a stack trace into a ticket, paste a ticket link into a pull request, ping someone on Slack to explain what's actually going on.
For a small dev team, that overhead is disproportionate. You don't need omnichannel routing or a 50-agent queue. You need customer emails to show up somewhere your team already works, with the context intact.
How it works
You get a unique forwarding address when you install Scitor. Point your existing support address at it — or keep using your current inbox and forward messages over. Every email that arrives at that address becomes a new GitHub Issue in your configured repository: sender, subject, and body populate the Issue, and any attachments are uploaded to secure cloud storage and linked directly in the Issue body.
On paid plans, AI triage runs on the incoming message at the edge — a one-line summary, sentiment, and a category label get applied automatically, so your team can filter and prioritize without reading every message first.
To reply, your team writes a normal GitHub comment on the Issue and adds /send on its own line. Scitor converts the Markdown to HTML and emails it to the customer from your support address — they never see GitHub. Use /sendall to reply to every participant in the thread instead of just the original sender.
What the Issue actually looks like
The same email, on both sides — before and after it becomes a ticket.
Login not working on Safari #847
![scitor-customerops[bot]](/images/scitor-bot-avatar.png){kind=avatar}
Developer support without the learning curve
Set up email to GitHub Issues in three steps
Install the GitHub App
Install Scitor from the GitHub Marketplace and pick which repositories should receive support requests. Scitor posts setup instructions with your unique email address.
Forward your support email
Set up forwarding from your existing address (e.g. support@yourcompany.com) to the Scitor address. You can also embed a support form on your website with a single JavaScript snippet.
Reply from GitHub
When a customer emails you, it appears as a GitHub Issue. AI adds a summary and labels. Your team writes a response, adds /send, and the customer gets a professional email.
Full configuration options, including SLA targets and business-hours support, are documented in the post-install guide.
FAQ
-
What do I need to get started?
-
A GitHub repository with Issues enabled. We recommend a dedicated support repository so your product code stays separate. Install the Scitor GitHub App, and you'll receive a unique email address to forward your support emails to.
-
How do I reply to a customer?
-
Write a comment on the Issue with your response, then add /send on its own line. Scitor converts your Markdown to HTML and emails it to the customer. Use /sendall to reply to all participants in the thread.
-
Can I send emails from my own domain?
-
Yes. Configure a custom sending domain through your email provider so replies come from your brand address instead of a Scitor address. This improves deliverability and looks professional to your customers.
-
What happens to email attachments?
-
Incoming attachments are uploaded to secure cloud storage and linked directly in the Issue body. When replying, drag and drop files into your GitHub comment — images will be inlined and other files attached to the outgoing email.
-
Does Scitor store my emails?
-
No. Email content passes through Scitor to create the GitHub Issue, but the message body is not stored on our servers. Only attachments are persisted in cloud storage. Your actual support conversations live in your GitHub repository — not in a third-party database. Full breakdown of what's stored and for how long: scitor.io/security.
-
Can I use Discussions instead of Issues?
-
Yes. Add a .github/scitor.yaml file to your repository with integration: discussions. Incoming messages will create Discussions instead of Issues, which is better for Q&A-style threads where community members can also help answer.
Connect your support email and install the GitHub App
Takes under 5 minutes. Free tier available. No credit card required.
New email from sarah@acme.com
Hi, I can't log in on Safari (iOS 17). I've tried clearing cookies and reinstalling the app. The login button just spins forever. This is blocking my whole team.
AI Analysis