Email Setup
How email works in Scitor
Scitor uses a simple flow for email:
Inbound: customer → your support address → forwarding → Scitor → GitHub Issue
Outbound: /send comment → Scitor → email provider → customer
Each repository gets a unique email address like abc123@scitor.io. Emails sent to this address are processed and converted into GitHub Issues or Discussions.
Setting up email forwarding
Google Workspace
- Open Gmail settings
- Click Add a forwarding address
- Enter your Scitor email address
- Click Proceed and confirm the verification
Microsoft 365
- Go to Exchange admin center → Mail flow → Rules
- Create a new rule to forward emails matching your support address to your Scitor email
Other providers
Most email providers support forwarding. Look for “forwarding rules” or “routing” in your email provider’s admin panel.
Custom sender address
By default, outbound emails are sent from no-reply@mail.scitor.io. You can customize this with the /set-from-address command:
/set-from-address support@yourcompany.com "Your Company Support"
Domain verification required
To use a custom sender address with your own domain, you need to verify the domain first. Without verification, you can only use @scitor.io or @mail.scitor.io addresses.
Reply threading
Scitor automatically threads email conversations:
- New email → Creates a new Issue or Discussion
- Customer replies → Added as a comment to the existing Issue or Discussion
- You reply with
/send→ Sent as email, customer can reply back
This works because Scitor encodes a unique thread identifier in the Reply-To address. When the customer hits “Reply” in their email client, the response is automatically linked to the right issue.
Attachments
Scitor handles email attachments automatically:
- Attachments are uploaded and linked in the issue body
- Inline images (embedded in HTML) are preserved
- File size limits follow your email provider’s limits (typically 25MB per email)