Delivering Alerts to Slack

When an alert rule fires, Aperture can post a formatted message directly to a Slack channel. This is in addition to the in-app inbox and email. Slack delivery needs two things: a Slack integration saved in the org settings, and that integration selected in the Notification section of the alert rule.

Connect a Slack integration

Manage integrations in Settings → Integrations. Only members with the Admin role can open the Settings area, so only an admin can add or change an integration.

1. Open Settings and select the Integrations tab.
2. Choose a workspace in the Workspace dropdown. Integrations apply to the selected workspace, and Add Integration stays disabled until you pick one. If the organization has only one active workspace, Aperture selects it for you. A table then lists the workspace’s integrations with their name, type, configured channel, and whether each one is enabled.
3. Click Add Integration.
4. Fill in the dialog that opens:
   • Name. A label for this integration. The default is “Slack Integration”. Choose a descriptive name if you plan to run several, for example “Pricing Alerts – #retail-ops”.
   • Webhook URL. Required. Paste the Incoming Webhook URL from Slack. Generate one on Slack’s Incoming Webhooks configuration page for your workspace.
   • Channel. Optional. Enter a channel name such as #alerts to override the default channel set on the webhook itself. Leave it blank to use the webhook’s default.
   • Enable this integration. Checked by default. Only enabled integrations appear in alert-rule delivery options.
5. Click Save.

Test the connection before saving

Click Test Connection at any point while the Webhook URL field has a value. Aperture posts a short confirmation message to the channel immediately:

✅ Test message from import.io:aperture - Integration configured successfully!

A green banner (“Test message sent successfully!”) confirms success. A red banner shows the error that Slack returned. The test uses the current form values, so you can check the channel override as well.

Tip

Run a test before saving. If the webhook URL is wrong or the Slack app has been removed, the test shows the error straight away. Without a test, the error only appears when a real alert fires.

Attach Slack delivery to an alert rule

Configure Slack delivery per alert rule on Configure & name, the last of the three steps in the alert rule wizard.

1. Near the bottom of the step, find Notification. It starts collapsed, showing a one-line summary such as “Email to you · Slack not set”. Click Change to expand it.
2. If no enabled Slack integrations exist, the Slack notification checkbox is disabled and the text underneath reads “No Slack integrations configured”, with a hint to configure one in Settings (Integrations tab). Connect an integration first, as described above.
3. Check Slack notification to enable it. A dropdown appears that lists all enabled integrations. Each entry shows the integration name. When a channel was set, the entry also shows that channel in parentheses, for example “Pricing Alerts – #retail-ops (#retail-ops)”. Integrations without a channel override show only their name. If only one enabled Slack integration exists, Aperture pre-selects it.
4. Choose the integration. Save stays disabled until you do. If Slack is checked with no integration chosen, the Notification section opens by itself and shows “Select a Slack integration.”
5. Below Notification, a Summary panel recaps the trigger, scope, and notification settings, together with an estimated count of monitored products, before you click Save alert rule.

The Notification section is also where you configure email notification recipients. Both channels can be active at the same time on the same rule, and the section reopens by itself whenever it has an unresolved problem, such as a missing recipient or a missing Slack integration.

Note

The Slack checkbox is disabled and cannot be checked if this workspace has no enabled Slack integrations. Add at least one integration in Settings before you return to the alert rule.

What arrives in Slack

When the alert fires, Aperture posts a structured message built with Slack Block Kit:

• Header. 🚨 Alert Triggered: rule name
• Rule detail. The alert type and description you set on the rule.
• Violation count. A line stating how many violations were found.
• Violations. Each affected product appears as a bullet, with a linked product name followed by the trigger description, for example “18% above Example Retailer”, “12% below market average”, or “Example Retailer pricing below MAP threshold”. When two or three retailers violate the same product’s MAP price, the bullet names them, for example “3 retailers pricing below MAP threshold (Example Retailer, Another Retailer, Third Retailer)”. With four or more violating retailers, the bullet shows only the count, for example “4 retailers pricing below MAP threshold”. The message lists the first 10 violations. If there are more, a final line reads “…and N more”.

Reminders go to the same channel. If you postpone an alert in the in-app inbox and the postpone window expires, Aperture re-delivers the alert to the same channel as a reminder. The header for a reminder reads ⏰ Reminder — Alert Triggered: rule name, so it is visually distinct from a fresh event. The reminder also adds a line stating when you postponed the alert.

Test delivery on a saved rule

On the Alerts page, open the Manage rules tab. Each row you can manage has a Test notifications button with a send icon. Click it to fire a synthetic test through every delivery channel configured on that rule, including Slack if enabled. This confirms that an existing rule reaches your channel without waiting for a real violation. The header of the Slack message starts with 🧪 [TEST] Alert:, and its rule-detail section includes the line “This is a test — no action required.” The message lists one synthetic violation for “Test Product” with the text “This is a test notification — your alert delivery is working correctly”, which tells it apart from a genuine alert. A success or failure toast appears for email and Slack when they are configured on the rule. A toast also appears for the in-app AI chat assistant. If AI chat alerts are not enabled for any of the rule’s recipients, that toast is an error explaining that nobody received the test.

Manage existing integrations

From the Integrations table you can:

• Edit. Click the pencil icon to reopen the dialog and change the name, webhook URL, channel, or enabled state. Unchecking Enable this integration while one or more alert rules use it shows an inline warning naming how many rules currently post to this Slack integration.
• Delete. Click the bin icon. A confirmation dialog warns that deletion cannot be undone. If any alert rules currently post to this integration, the dialog also names how many.

To suspend Slack delivery temporarily without removing the integration, uncheck Enable this integration in the edit dialog. Disabled integrations remain in the table, but alert-rule delivery selectors hide them.

Caution

Deleting a Slack integration does not leave the rules that used it broken. Aperture immediately turns off Slack delivery on every rule that named the deleted integration. Those rules stay enabled and keep creating alert events in the inbox, and email delivery stays in place if a rule already had it configured; a rule that only used Slack becomes inbox-only. The confirmation dialog states this and names how many rules are affected before you confirm. To keep Slack delivery on those rules, select a different integration in each rule’s Notification section before you delete this one.

Disabling an integration instead of deleting it does not change the rules that use it: Slack delivery simply pauses, and resumes automatically once you enable the integration again.

Separately, if your workspace has more than one enabled Slack integration and a rule has no integration recorded on it (for example, a rule saved before the workspace added a second integration), Aperture cannot guess which channel it should use, so Slack delivery stops until someone edits the rule and picks one.