For the complete documentation index, see llms.txt. This page is also available as Markdown.

Slack

How Spara integrates with Slack.

Spara can update your team about live conversations with prospective customers in Slack.

You must be a Manager- or Integrator-level user to manage third party integrations.

Navigate to the Integrations page by clicking on the Settings link in the left hand navigation bar.

Click the "Authorize" button. This will lead you through an OAuth authentication flow. There are no further steps necessary upon completing this flow. You should see that the integration is "Enabled" within Spara's Integrations page.

Step 2: Configure notifications

Once Slack is connected, choose which events notify Slack and where to send them from Settings > Notifications. See Notifications.

Permissions and data use

When you connect Slack, Slack's authorization screen lists the OAuth scopes Spara requests. As with any Slack app, the screen describes what each scope could allow; Spara's integration exists only to post notifications into the channel you choose.

Scope
What it grants
Why Spara needs it

chat:write

Post messages

Send notifications into the channel you configure.

channels:read, groups:read

View basic info about public and private channels

List your channels so you can pick one during setup.

channels:join

Join public channels

Add the Spara bot to the channel you select so it can post there.

channels:manage

Create and manage public channels

Create the notification channel for you if it doesn't already exist.

users:read, users:read.email

View people in the workspace and their email addresses

Match notifications to the right sales rep.

What Spara will and will not do

Spara will:

  • Post automated notifications into the channel you explicitly configure.

  • List your channels and workspace members so you can complete setup.

  • Maintain an authenticated connection to deliver those notifications.

Spara will not:

  • Read, store, analyze, or export your Slack messages. Spara requests no message-history scope, so it cannot read channel or direct-message history.

  • Access channels outside of what you configure.

  • Monitor, surveil, or index any Slack conversations.

Last updated