# Slack Workflow Integration in Certificate Alerting

**URL:** <https://community.infisical.com/t/slack-workflow-integration-in-certificate-alerting/84>\
**Category:** Feature Requests\
**Tags:** cert-management\
**Created:** [October 14, 2026, 9:56am UTC](https://community.infisical.com/t/slack-workflow-integration-in-certificate-alerting/84 "2026-10-14T09:56:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sinnwise](https://yyz2.discourse-cdn.com/flex048/user_avatar/community.infisical.com/sinnwise/32/121_2.png) [@sinnwise](https://community.infisical.com/u/sinnwise)\
**Post date:** [October 14, 2026, 9:56am UTC](https://community.infisical.com/t/slack-workflow-integration-in-certificate-alerting/84/1 "2026-10-14T09:56:14Z")

</div>

Hey team,

We’d like to send Certificate Manager notifications through Infisical’s existing Slack integration, rather than setting up incoming webhooks separately.

Right now, adding a Slack destination to a certificate alert requires a webhook URL. There doesn’t appear to be a channel override, so each Slack channel we want to notify needs its own incoming webhook. We can reuse a URL across alerts going to the same channel, but routing alerts to different teams means creating and managing multiple webhook destinations—even though we already have the Infisical Slack integration installed.

For example, we’d like to route expiration alerts for one application to its owning team’s channel, while sending alerts for another application to a different team. A central security channel might also receive broader certificate lifecycle notifications.

Ideally, when adding a Slack destination to an alert, we could:

- Choose an existing Infisical Slack integration.
- Select the destination Slack channel.
- Send a test notification before saving.

It would be useful for both application-specific alerts and the broader Certificate Manager alerts, covering expiration, issuance, renewal, and revocation. Keeping incoming webhooks as an alternative would still make sense.

 ![CleanShot 2026-10-14 at 10.55.20](https://canada1.discourse-cdn.com/flex048/uploads/infisical1/original/1X/93173cb95cb84a6c74b864b0447e62131935b566.png)

---

<div class="post-metadata">

**Author:** ![ashwin-infisical](https://yyz2.discourse-cdn.com/flex048/user_avatar/community.infisical.com/ashwin-infisical/32/34_2.png) [@ashwin-infisical](https://community.infisical.com/u/ashwin-infisical)\
**Post date:** [October 14, 2026, 4:14pm UTC](https://community.infisical.com/t/slack-workflow-integration-in-certificate-alerting/84/2 "2026-10-14T16:14:47Z")

</div>

Hey Alex!

Thank you for reaching out! I have passed this along to our engineering team; we’re already implementing a consolidation of alerting across the platform and I believe this is something we will be shipping very soon. I’ll keep you updated as we make this available!