HexSign sends an alert whenever a certificate or provisioning profile crosses one of the thresholds you configure. Alerts can go to email, a chat channel (Slack or Microsoft Teams), or an incident-management tool (Jira, PagerDuty, Jira Service Management, or incident.io). Every channel can be tested before it's enabled in production.
Pick the right thresholds
- 90 days: useful for Distribution certificates so rotation can be planned outside a release.
- 30 days: the default "start the work" threshold.
- 14 days: last call before the certificate hits the danger zone.
- 7 days: escalation; treat as a P1.
Add an alert
- 1
Open the Alerts page
Go to Alerts in the dashboard and click Add alert. Each alert is one destination plus its thresholds and the event types (certificates, profiles) it covers.
- 2
Pick a channel and fill in the destination
Choose a channel and enter its destination fields. The channel type is fixed once the alert is created, so pick the right one up front.
- 3
Send a test, then create
Click Send test to confirm the destination is wired up, then save. A test posts a sample alert so you catch a typo'd webhook URL or a bad token before any real alert fires.
Chat channels: Slack and Microsoft Teams
- Slack: add the Incoming Webhooks app, pick the channel HexSign should post to (e.g. #releases or #ios-on-call), and paste the webhook URL.
- Microsoft Teams: create a Workflow that posts to a channel and paste its webhook URL. (Classic Office 365 connectors are deprecated.)
Incident management and ticketing
Beyond chat, HexSign can route alerts into the tools your on-call and release process already run on. Each one batches a threshold's expiring items into a single ticket, incident, or alert.
- Jira
- Add your Jira Cloud site URL, account email, an API token, and a project key. HexSign opens an issue in that project for each batch of expiring items.
- PagerDuty
- Paste an Events API v2 integration routing key. HexSign triggers an incident, with severity scaled to how close the expiry is.
- Jira Service Management
- Add a JSM Operations API integration key and HexSign raises a P1–P5 alert. JSM is Atlassian's replacement for Opsgenie, which is being retired.
- incident.io
- Create an HTTP alert source (Alerts → Configuration), then paste its URL and token. HexSign sends an alert event incident.io can group, route, or escalate into an incident.
Set up email
Email alerts go to the address you set on the alert. It can be any address (including a distribution list like ios-releases@your-team.com), and the recipient doesn't need a HexSign account.