> ## Documentation Index
> Fetch the complete documentation index at: https://docs.corelayer.com/llms.txt
> Use this file to discover all available pages before exploring further.

# September 2026

> September 2026 Corelayer release notes: environment-aware analysis with Slack routing, typed Webhook providers, and incident.io declared incidents.

<Update label="September 22, 2026" tags={["New"]}>
  ## Environment-aware analysis and Slack routing

  Corelayer now infers the environment associated with an issue from the available context and considers it during investigation and impact assessment. Environments such as production, staging, and development are distinguished automatically.

  Slack notifications can be routed by environment and severity. Configure destination channels in your Slack integration settings and pick the environment and severity criteria for each route. For example, send critical production issues to your on-call channel and staging issues to a staging channel.

  [Route notifications by environment and severity](/integrations/slack#route-notifications-by-environment-and-severity)
</Update>

<Update label="September 8, 2026" tags={["New"]}>
  ## Dedicated Webhooks with typed providers

  Webhooks are now a first-class area in the sidebar with typed presets for each source. Choose a **Webhook type** when adding a webhook, and Corelayer supplies the URL, token, and provider-specific payload template.

  Supported types:

  * [incident.io](/webhooks/incidentio) — alerts and declared incidents using a signing secret
  * [Honeycomb](/webhooks/honeycomb) — trigger alerts using a webhook recipient and shared secret
  * [CloudWatch](/webhooks/cloudwatch) — alarm state changes through an EventBridge API destination
  * [Datadog](/webhooks/datadog) — monitor notifications using a webhook payload template
  * [Custom alerts](/webhooks/custom) — the generic JSON format with a bearer token

  Each source can be enabled or disabled without losing its configuration, deleted from the list, and rotated for a new bearer token when needed.

  [Browse webhook sources](/webhooks/overview)
</Update>

<Update label="September 8, 2026" tags={["New"]}>
  ## incident.io declared incidents

  The incident.io webhook now investigates declared incidents in addition to alerts. Subscribe to `public_incident.incident_created_v2` or `private_incident.incident_created_v2` on your endpoint and Corelayer opens an investigation using the incident reference, name, and summary, with severity, status, incident type, mode, visibility, Slack channel, role assignments, and custom fields recorded as labels.

  Alert resolution events (`alert_resolved_v1`) are now recorded against the originating alert. Corelayer reads from incident.io and does not write changes back.

  Endpoints created before declared incident support are alert-only and are not updated automatically. Add the incident-created events to an existing endpoint to receive declared incidents.

  [Configure the incident.io webhook](/webhooks/incidentio)
</Update>


## Related topics

- [August 2026](/changelog/august-2026.md)
- [Corelayer Changelog: May 2026 Release](/changelog/may-2026.md)
- [Corelayer Changelog: June 2026 Release](/changelog/june-2026.md)