> ## Documentation Index
> Fetch the complete documentation index at: https://docs.corunner.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Connect Inbound Email to Corunner for Decision Capture
> Capture explicitly recorded decisions from forwarded email. A one-way inbound channel that stages decisions for human review before they enter memory.
Inbound Email is a Direct Connection that captures explicitly recorded decisions from forwarded email. It is a one-way inbound channel: emails you forward to a Corunner address are received, verified, and staged as decision-capture events for human review before they enter memory.
This is not a general email inbox integration. It does not read your Gmail or Outlook inbox. It only receives signed decision emails you forward to Corunner.
## What Corunner does with Inbound Email
Corunner listens for signed email events and stages them as **decision approvals**. A curator reviews each staged decision and either captures it into memory or rejects it. Use this when a decision was made over email and you want it recorded without retyping it in chat.
## What you get
* Receive signed email events
* Stage decision approvals
## Authentication
Connect with an API key you generate in Corunner. Configure the forwarding rules in your email provider to send the target messages to the Corunner inbound address.
## What breaks if you disconnect
* Email decision capture
## Manage this connection
Open **Integrations** in the Corunner web app, then find **Inbound Email** under the **Direct Connections** tab.
## Connect Inbound Email
Open the **Connect Inbound Email** dialog and enter the credentials for the inbound email channel.
The credential is encrypted at rest and used only for the scopes shown. Corunner verifies it the moment you connect. If the credential is invalid, an error appears in the dialog.
Enter the alias assigned to your inbound email channel. Corunner uses it to identify email events sent through this connection.
Paste the credential used to verify incoming email events.
Enter a recognizable name, such as `Inbound Email – Production`, to distinguish this connection from other environments.
Use the provider code configured for the connection, such as `email_inbound`.
Corunner verifies the credential immediately and saves the inbound email connection when validation succeeds.