Connect tools and notification delivery

Connections authorize Anectico to interact with another product. Notification channels define a concrete delivery destination used by alert rules. A connection alone does not route any alert.

Connect an external tool

Open Connections and choose a provider:

• Slack, GitHub, Jira, and Linear use an authorization flow;
• PagerDuty accepts an Events API v2 routing key.

Complete the provider flow, return to Anectico, and confirm the provider shows Connected. A Needs reauth state means the saved authorization can no longer be used. Choose Reauthorize to replace its OAuth grant in place; linked tickets remain pinned to that connection. Disconnect a provider only after checking alert routes and linked ticket workflows that depend on it.

If Anectico detects more than one non-revoked connection for a provider, the page shows Connection conflict with every exact connection ID and status; it does not hide a broken connection behind an active duplicate. Disconnect the unintended duplicate before choosing Reauthorize on the connection that existing tickets use.

Jira setup asks for the target project key, issue type, optional priority, and any required customfield_N values before redirecting to Jira. Linear setup asks for the team plus the open and done workflow-state IDs. These values are non-secret connection metadata and survive the OAuth callback; access and refresh tokens remain write-only. Reauthorization pre-fills the current setup so you can rotate authorization without silently changing the ticket destination.

Credential rotations are validated before Anectico replaces the current credential. If another admin rotated it first, refresh and retry against the new version; an invalid or stale update leaves the last working credential untouched. Disconnect is an idempotent revocation. Existing durable delivery attempts remain pinned to the credential they started with, while new sends no longer select it. A new delivery with no active connection fails once as a configuration error; it is not repeatedly sent to the retry queue. Restore or replace the connection before retrying that notification route.

Create a notification channel

Open Settings → Notifications → Notification channels. Create a channel for webhook, Slack, email, or PagerDuty delivery. Select the connected provider or enter the required destination, save, then choose Test on the saved channel.

Only attach a channel to an alert rule after the test succeeds. When deleting a channel, update every rule that routes to it; those rules will otherwise stop delivering to that destination.

Configure personal contact methods

In Settings → Notifications → My contact methods, add an email address or Slack DM destination. Those are the personal methods that deliver today; SMS and phone are shown as coming soon and cannot be selected. Slack DM requires an active Slack connection. Contact methods belong to the signed-in member, while notification channels belong to the organization.

After adding a contact method, confirm it is available when building the relevant on-call and escalation workflow.

Slack alert and escalation messages include Acknowledge. Anectico accepts the click only after Slack signature/freshness verification and an explicit mapping from that Slack user to a current Anectico organization member. The first ACK wins across Slack, dashboard, CLI, and MCP; repeated clicks cannot change its actor, time, or note, and the canonical ACK stops the escalation.

Troubleshoot delivery

1. Test the saved notification channel directly.
2. Confirm its connection is active and the destination still exists.
3. Confirm the alert rule is enabled and routes to that exact channel.
4. Check whether the alert actually entered the firing state.
5. For on-call paging, confirm the active schedule, escalation step, and responder contact method.
6. In delivery history, select the same project as the alert. Delivery records are project-scoped and show attempts, sanitized provider errors, and provider correlation IDs without exposing secrets.

Never paste provider tokens or routing keys into support messages.

• Create alerts
• Handle incidents and on-call