Hear about the lead in the channel where you already work.

Spectacle connects to Slack in about 2 minutes and posts into a channel the moment something worth acting on happens. A contact enters an audience, a lead is scored highly qualified, Lens unmasks the company behind an anonymous visit — the notification arrives in Slack rather than waiting to be found in a dashboard.

At a glance

• Category: Notifications
• Setup time: About 2 minutes
• Authentication: OAuth, a workspace admin installs the Spectacle app. Spectacle asks for 4 bot scopes: read the channel list, post messages, post to public channels, and read the workspace name
• Slack plan: Any Slack workspace where you are allowed to install apps
• Spectacle plan: Automations are plan-dependent — see the pricing page
• Direction: Spectacle → Slack only. Spectacle posts messages; it reads no channel history and imports nothing
• Triggers: Contact and company audience entry and exit, lead score changes, and Lens company unmasking
• Delivery: Instant, or batched at 15-minute, hourly, or daily intervals
• Docs: /docs/automations-and-webhooks

What Slack is for in Spectacle

Attribution reporting answers questions you go and ask. Some things should not wait to be asked. A named account has come back for the fourth time this week and is reading the pricing page; a contact has just crossed into your highly-qualified audience; Lens has put a company name to a run of anonymous visits from a target account. Each of those has a short window in which acting on it is worth something.

Slack is the destination Spectacle sends those to. It is one of the two things an automation can do — the other being a signed webhook to your own systems — so the same trigger that drives an internal integration can also nudge the person who should pick up the phone.

How it works

• Automations, not a firehose. Every notification comes from an automation you built: a trigger, an audience where the trigger needs one, and Slack as the destination. Nothing is posted that you did not ask for
• Contact triggers: Entered audience, exited audience, and scored as not, somewhat, or highly qualified
• Company triggers: Entered audience, exited audience, unmasked by Lens, and the same three lead-score outcomes
• Any channel: Pick the channel per automation, so sales alerts and marketing alerts do not have to share one
• Instant or batched: High-volume triggers can be aggregated into a 15-minute, hourly, or daily digest instead of arriving one message at a time
• Test before you save: The Send test button posts a test message so you can check the channel and the wording before the automation goes live

The full trigger list, delivery options, and the delivery debugger are covered in the Automations and webhooks docs. This page summarizes; Docs is the source of truth.

What you get

• Sales hears about the lead while it is still warm. Highly-qualified scores and audience entries arrive in the channel the team already watches, instead of in a report someone opens on Monday.
• Named accounts surfaced as they appear. Lens unmasks the company behind anonymous traffic and posts it, so an account that is quietly researching you becomes something you can act on.
• One trigger, two destinations. The same automation model drives signed webhooks into your own systems and Slack messages for the humans, so the alerting and the integration cannot drift apart.
• Volume you can live with. Batched delivery keeps a busy trigger from turning a channel into noise, which is usually what kills alerting.
• Read-only in your workspace. Spectacle posts and lists channels. It does not read messages, and it imports nothing from Slack.

Pairs with

Slack + HubSpot or Salesforce for the follow-up · Slack + LinkedIn Ads for account-based campaigns · Slack + Calendly so a booked meeting is announced as it lands