Slack Notifications

On tymeslot.app, Slack is ready to connect, with no app to register:

1. Open Dashboard → Automation → Slack.
2. Click Add to Slack and confirm the workspace and permissions inside Slack.
3. Back in Tymeslot, pick the channel the bot should post to. Public channels are listed automatically. For a private channel, invite the bot in Slack first, then click Refresh and pick it from the list.
4. Choose which events should send notifications, then save. Click Test on the integration card to send a test message.

OAuth gives every user a one-click "Add to Slack" button, messages sent under your own Slack App's name and icon, and channel changes without pasting new URLs. Use it for any deployment with more than one user.

Register a Slack App at api.slack.com/apps and configure it as follows:

1. Click Create New App → From scratch and pick any workspace for development.
2. Under OAuth & Permissions, add the redirect URL:
   Copy

   https://your-domain/api/slack/oauth/callback

3. On the same page, add these bot token scopes:
   Copy

   chat:write
   chat:write.public
   channels:read
   groups:read
   team:read

4. Under Manage Distribution, enable public distribution if you want any workspace to install the app. For an internal deployment, leave it private and install from your own workspace.
5. Copy the Client ID and Client Secret from Basic Information → App Credentials.

Then set these environment variables on your Tymeslot deployment:

SLACK_CLIENT_ID=<your client id>
SLACK_CLIENT_SECRET=<your client secret>

Setting SLACK_CLIENT_ID enables Slack notifications. With both variables set, OAuth mode is active and users see the "Add to Slack" button in the dashboard.

If you would rather not configure OAuth on your server, users can paste an Incoming Webhook URL instead. Set:

SLACK_ENABLED=true

With SLACK_ENABLED=true and no OAuth credentials, the dashboard offers only the Incoming Webhook URL form.

To generate a URL, in Slack:

1. Open api.slack.com/apps and create a new app (or pick an existing one).
2. Open Incoming Webhooks and toggle the feature on.
3. Click Add New Webhook to Workspace, pick the channel, and approve.
4. Copy the generated URL (it looks like https://hooks.slack.com/services/...) and paste it into Tymeslot.

OAuth mode: click Edit on the integration, pick a new channel and save. Public channels appear automatically. A private channel appears only once the bot is a member: invite it in Slack with /invite @YourApp, then click Refresh.

Webhook URL mode: generate a new Incoming Webhook URL in Slack for the channel you want, click Edit on the integration and paste it into Slack Webhook URL. The new URL replaces the old one.

• channel_not_found: the channel no longer exists or the bot cannot see it, and Tymeslot disables the integration. Invite the bot to the channel (or pick another one with Edit), then click Re-enable on the card.
• not_in_channel: the bot is not a member of a private channel. Invite it with /invite @YourApp, or switch to a public channel, which chat:write.public can reach without invitation.
• token_revoked / account_inactive: the workspace removed the app or deactivated the bot user, and Tymeslot disables the integration. Delete it and connect again with Add to Slack.
• Webhook URL stopped working: a workspace admin can revoke Incoming Webhook URLs at any time, and Tymeslot disables the integration with the reason "webhook URL was revoked in Slack". Generate a new URL in Slack, paste it in with Edit, then click Re-enable.
• Rate limiting: when Slack throttles posting, Tymeslot waits for the interval Slack asks for and sends the message again. Rate limiting never counts towards disabling the integration.

Each notification contains only what identifies the meeting: its title (meeting type and attendee name), the attendee's email address, the time and duration, a cancellation or decline reason where there is one, and a link to your Tymeslot meetings page. No calendar contents, video links or answers to booking questions are sent.

The scopes requested are the minimum needed to post messages and list channels the user picks from: chat:write, chat:write.public, channels:read, groups:read, and team:read. The app cannot read messages, browse files, or access user profiles.

To revoke access at any time, open Slack → Settings & administration → Manage apps, find the Tymeslot app and remove it. Slack invalidates the token at once, and Tymeslot disables the integration on its next attempt to post.