Skip to content

Slack integration

EvenTier posts request updates to a Slack channel through an incoming webhook, or through a Slack app's bot token so that each request keeps its own thread. Add the app's signing secret, and replies in that thread are added to the request as public comments from the people who wrote them.

Set up in
Admin → Settings → Integrations → Chat notifications
Who can set it up
People with the Manage integrations permission

Request updates in a channel

Each Slack destination posts the events you pick: new requests, updates, resolutions and approval decisions. A message shows the request number and title, a one-line summary of the change, the request's details and an Open request button.

  • New destinations start with new, updated and resolved requests
  • Limit a destination to some teams, request types or priorities
  • Add an intro or footer line with placeholders such as {{requestNumber}}, {{assignedTeam}} and {{requestUrl}}
  • The message mentions the assignee when their EvenTier profile has a Slack member ID

One thread per request

With a bot token and a channel ID, the first message about a request starts a thread, and later updates are posted as replies in it. An incoming webhook posts each update as a separate message.

Thread replies added to the request

With reply sync on, a reply in a request's thread is added to the request as a public comment. It is posted as the EvenTier user who wrote it, with that user's own permissions.

  • Slack's signature is checked on every event, and events more than five minutes old are refused
  • Senders are matched by the Slack member ID on their EvenTier profile, or by email address when Slack returns one
  • A reply is not added if its sender cannot be matched or cannot comment on the request. People with the Manage integrations permission get an alert, at most once a day
  • Bot messages, edits and new top-level messages in the channel are ignored

Confidential requests stay out of Slack

Nothing about a confidential request is posted, because everyone in the channel would see it. The check runs when each message is sent, so a request made confidential after an update was queued is left out too.

Profile photos from Slack

When a reply arrives, EvenTier imports the sender's Slack photo in the background, at most once a day. It skips Slack's generated placeholder. It never replaces a photo the member uploaded, or one from your directory or single sign-on (SSO).

  • Needs the bot's users:read scope
  • To stop imports, turn off Import profile photos in Admin → Settings → Organization settings → General

Set up Slack

  1. 01

    Add a Slack destination

    Choose Slack, name the destination and pick the events to post. For channel alerts, paste an incoming webhook URL from Slack. It starts with https://hooks.slack.com/services/.

    Where:
    Admin → Settings → Integrations → Chat notifications → Add chat destination
    Permission:
    Manage integrations
  2. 02

    Add a bot token for threads

    For one thread per request, use a Slack app installed in your workspace. Enter its bot token, which starts with xoxb-, and the ID of the channel to post in. A destination uses either the webhook URL or the bot token and channel ID.

  3. 03

    Choose routing and send a test

    Open Show routing and templates to limit the destination to some teams, request types or priorities, or to add an intro or footer. Save the destination, then send a test message from it.

  4. 04

    Turn on reply sync

    Add the Slack app's signing secret and Slack workspace ID to the destination. Copy the Slack events URL shown on the saved destination and paste it into the app's Event Subscriptions.

    Where:
    The saved bot-token destination, then your Slack app's settings
    Permission:
    Manage integrations
  5. 05

    Link people to their Slack accounts

    Each person can add their Slack member ID to their EvenTier profile. In Slack, they find it under View full profile, then Copy member ID. An admin can also set it in Admin → Users. When Slack returns a sender's email address and it matches an active EvenTier user, that person is linked automatically.

    Where:
    Profile · Admin → Users
    Permission:
    None for your own profile; Manage users for anyone else's

Data flow

Updates go from EvenTier to the channel. Thread replies come back to EvenTier only when reply sync is on. The webhook URL, bot token and signing secret are stored encrypted.

Sent to Slack

  • The request number, title and a link to the request
  • A summary of the change and who made it, and for approvals, the decision
  • Status, priority, request type, team, requester and assignee
  • Your intro and footer templates, filled in

Read from Slack

  • Replies in a request's thread, with the sender's Slack member ID (reply sync only)
  • The sender's email address and profile photo, looked up with the bot token

Never sent

  • Anything about a confidential request
  • Comments and internal notes from the request

Questions about Slack

Which Slack credentials does EvenTier need?
An incoming webhook URL is enough for channel alerts. One thread per request needs a Slack app's bot token and a channel ID. Adding replies from Slack to the request also needs the app's signing secret and workspace ID.
Can I post different requests to different channels?
Yes. Add a destination for each channel, each with its own events and its own team, request type and priority filters.
Who can reply from Slack?
Any active EvenTier user whose Slack account is linked. Their reply is added with their own permissions, so it is not added if they cannot comment on the request.
Are confidential requests posted to Slack?
No, because everyone in the channel would see it. The people who can open a confidential request still get email and in-app notifications about it.

Get notified when signup opens.

EvenTier is in private early access. Leave your work email and we will let you know when you can create a workspace.

No card. We use your email only for your early-access invite and launch news. Privacy Policy