Slack and Microsoft Teams Integrations

Connecting Slack or Microsoft Teams lets your Alpharun automations deliver their results where your team already works, either posted to a shared channel or sent as a direct message to each person. Results delivered in Slack or Teams include the full report text, so readers get the insight without clicking back into Alpharun. Every result is also saved in Alpharun regardless of where it is delivered.

You can connect Slack, Microsoft Teams, or both. Each automation delivers through one provider at a time: email, Slack, or Teams.

Setting up chat delivery takes approval on two sides: the right Alpharun role to connect the integration and build automations, and an administrator on the Slack or Microsoft side to approve Alpharun's access.

A Slack workspace admin (or a member allowed to install apps) approves the Alpharun app when you connect. Alpharun requests only what it needs to deliver results:

Alpharun cannot read messages in your channels or DMs.

Teams requires two separate approvals:

1. Admin consent in Microsoft Entra ID. A Microsoft 365 administrator who can grant tenant-wide consent (typically a Global Administrator or Privileged Role Administrator) approves Alpharun's read-only Microsoft Graph permissions for your organization.

2. App installation in Teams. A Teams administrator adds the Alpharun app to each team that should receive results.

All four are read-only. The Alpharun Teams app is notification-only: it posts results but cannot read channel conversations, chats, or files.

1. In Alpharun, go to Settings > Integrations and select Slack.

2. Click Connect and sign in to the Slack workspace you want results delivered to.

3. Review the permissions and click Allow. You return to Alpharun with Slack shown as Connected.

4. For any private channel that should receive results, invite the Alpharun app in Slack by typing /invite @Alpharun in that channel. Public channels need no invite.

Direct messages are matched by email, so each teammate's email in Alpharun must match the email on their Slack account.

Teams is enabled per account. If you do not see Microsoft Teams under Settings > Integrations, ask your Alpharun contact to turn it on.

1. In Alpharun, go to Settings > Integrations and select Microsoft Teams.

2. Click Connect. A Microsoft 365 administrator signs in and accepts the permissions on behalf of your organization. If you are not that administrator, forward them the consent step.

3. A Teams administrator adds the Alpharun app to every team that should receive channel posts. In the Teams admin center this is under Teams apps > Manage apps; from there, add the app to each team.

4. Back on the Microsoft Teams page in Alpharun, check Connection status. Both rows should show green: Admin consent granted and Alpharun app installed in Teams, with the list of teams Alpharun can reach.

Alpharun shows App not installed until the app is in at least one team, because consent alone does not let it post anywhere.

A few Teams rules to know:

• Alpharun posts to standard channels only. Private and shared channels are not supported.

• Direct messages reach people who belong to a team with the app installed. To reach people outside those teams, your Teams admin can also install the app for everyone through an app setup policy.

• As with Slack, direct messages are matched by email, so each teammate's Alpharun email must match their Microsoft 365 account.

Once a provider is connected, you choose it in an automation's delivery settings. This works the same way for the built-in templates (such as customer praise digests, perfect calls, and playbook score movement) and for custom automations set to One shared result or One result each.

1. Open the automation and find Delivery channel.

2. Select Slack or Microsoft Teams. If the provider is not connected yet, a Connect button appears here.

3. Choose where results go:

   • Channel: search for and pick one or more channels. Everyone in the channel sees the same result, and the automation's recipient list is ignored.

   • Direct messages: each selected person gets their own result privately, matched by email.

4. Save the automation and run a preview to confirm the output before enabling it.

If a channel you expect is missing from the picker, it usually means Alpharun cannot post there yet. In Slack, invite the app to the private channel. In Teams, add the app to that channel's team. Then refresh the channel list.

Weekly coaching goals are delivered by email only and do not offer Slack or Teams.

When a custom automation's Result type is set to Custom, there is no delivery picker. Alpharun reads your instructions on every run to decide what reports to write, who gets them, and where they are delivered. To deliver through Slack or Teams, your instructions need to say so explicitly.

Include these four things:

1. Name the provider. Say "in Slack" or "in Microsoft Teams." If you name neither, results go by email.

2. Name the destination. Use the exact channel name, or say the results should be sent as direct messages to specific people or managers.

3. Use one provider per automation. An automation cannot post to Slack and Teams in the same run. Create a second automation if you need both.

4. Map each report to its channel when you want several reports. For example, one report per group, each posted to its own channel.

Names are not case-sensitive. The channel must already be reachable: a private Slack channel needs the app invited, and a Teams channel must be a standard channel in a team with the app installed.

• "Post one company-wide weekly digest to the Revenue channel in Microsoft Teams."

• "Write a separate report for the SDRs group and post it in Slack channel #sdr-reports."

• "Write separate reports for the SDRs and AEs groups. Post the SDRs report in Slack channel #sdr-reports and the AEs report in #ae-reports."

• "Send each manager a Slack direct message summarizing their team's calls."

Each run records how it interpreted your instructions. Open the run and review the interpretation step, which describes the report plan and lists any warnings. Common warnings:

• Provider not connected. The run falls back to email. Anything addressed to a channel is not delivered, since email has no channels.

• Channel not found. That channel is skipped, and every other destination still receives its report.

• More than one channel with that name. Common in Teams. Use the team-qualified name, such as Sales › Revenue.

• A group cannot receive results about group calls. Reports about a group's calls can go to that group's manager or to a channel mapped to the group, not to the group's members.

Run a preview after any change to the instructions. A preview notifies no one, so you can confirm routing safely.

Disconnecting Slack or Teams in Settings > Integrations stops all automation deliveries through that provider. Results are still saved in Alpharun.