Integrations
Create and update incidents by sending emails to Runframe.
How it works
Email sent → Runframe receives → Incident created or updatedSend an email to your Runframe forwarding address and it becomes an incident. Reply to a notification email and your message gets added to that incident's timeline.
No webhooks, no API keys.
Who can send emails
| Sender | Setup required |
|---|---|
| Any active user in your Runframe organization | None, works by default |
One authorized external email (e.g. support@yourcompany.com) | Enable in Settings > Email |
Emails from unrecognized senders are silently ignored.
Configure email intake
- Go to Settings > Email
- Copy the forwarding email address shown on the page
- To route incidents to a specific service and trigger on-call, enable "Create incidents from email" and select a service
- To allow a non-user email address to create and update incidents, add it as the authorized sender email
Service linking is optional but recommended. Without it, email-created incidents are unassigned. With a linked service, incidents go to the right team and trigger on-call automatically.
Field mapping
| Email field | Runframe field |
|---|---|
| Subject | Incident title (Re: and Fwd: prefixes are stripped) |
| Body | Incident description (up to 2,000 characters) |
| Sender | Creator (matched to org user or authorized email) |
Replying to incidents
Runframe notification emails include the incident number in the subject (e.g. [INC-1234]). Reply to one and your message is added to the incident timeline as a comment.
This works for all organization users by default. You can disable it in Settings > Email.