Teams Integration
Tap supports Microsoft Teams as a campaign delivery channel alongside email and Slack. When configured, campaign invitations are sent as Teams messages to participants.
How It Works
Similar to the Slack integration, an organization admin connects their Teams environment to Tap through an OAuth-based app installation. Once connected, campaigns can target participants via Teams messages containing their unique feedback links.
Setup
- Admin connects Teams -- Initiates the OAuth flow from organization settings
- App authorization -- Admin consents to the Tap app in their Microsoft 365 tenant
- Token exchange -- Tap receives and stores the access credentials
- Ready to use -- Campaigns can now select "Teams" as the delivery channel
Delivery Channel Comparison
Tap supports three delivery channels. The choice depends on where participants are most likely to see and act on the invitation.
| Feature | Slack | Teams | |
|---|---|---|---|
| Setup required | None (default) | OAuth workspace install | OAuth tenant install |
| Delivery method | HTML email via Resend | Slack DM via Bolt | Teams message via Graph API |
| Rate limiting | Token bucket (2/sec) | SlackQueue limiter | Teams API limits |
| Reminders | Automated via cron scheduler | Not yet supported | Not yet supported |
| Best for | External participants, broad reach | Internal teams using Slack daily | Internal teams using Teams daily |
| Participant experience | Click link in email | Click link in DM | Click link in message |
Configuration
When creating a campaign, the delivery channel is set via the delivery_channel field on the campaign:
email(default) -- Invitations sent via Resendslack-- Invitations sent via Slack DMsteams-- Invitations sent via Teams messages
The participant experience after clicking the link is identical regardless of channel -- they land on the same token-based chat interface.