Skip to content

Documentation

Integrations

Post request updates to Slack and Microsoft Teams, send signed webhooks, store attachments in S3-compatible storage with ClamAV scanning, and use the REST API.

Where
Admin → Settings → Integrations
Permission
MANAGE_INTEGRATIONS
Updated
October 2026

Overview

Slack: post request updates to a channel through an incoming webhook, or one thread per request with a bot token.

With a Slack bot token and signing secret, replies in a request's Slack thread are added to the request as comments.

Microsoft Teams: post updates through Microsoft Graph or a Teams Workflows webhook. A Graph change-notification subscription is optional.

Webhooks: subscribe to four event types. Every payload is signed with HMAC SHA-256.

Nothing about a confidential request is posted to Slack or Teams, because everyone in a channel would see it. People who can open the request still get email and in-app notifications.

Webhooks do deliver confidential requests, and mark them with isConfidential.

Attachment storage works with S3-compatible services (AWS S3, Cloudflare R2, MinIO). Each organization gets its own key prefix.

ClamAV scans every file before it is stored. In production, a file that cannot be scanned is refused.

Step by step

  1. 01

    Connect Slack

    Add Slack as a chat destination so request updates post to a channel.

    • Incoming-webhook URL: posts updates to a channel
    • Bot token and channel ID: one thread per request
    • Optional: limit the destination to some teams, request types or priorities
    1. Admin → Settings → Integrations → Chat notifications → Add chat destination → Slack
  2. 02

    Sync Slack thread replies

    Turn replies in a request's Slack thread into public comments on the request. This needs a bot-token Slack destination.

    • On the destination, add your Slack app's signing secret and workspace (team) ID
    • Paste the Slack events URL shown on the destination into the app's Event Subscriptions
    • Each agent sets their Slack member ID on their profile, so their thread replies are added as public comments
    • Replies from people with no mapped member ID are refused and reported to admins
  3. 03

    Connect Teams

    Add Microsoft Teams as a chat destination, using a Teams Workflows webhook or Microsoft Graph.

    • Legacy incoming webhook URLs work until Microsoft retires them
    • Or enter Microsoft Graph credentials for richer delivery and change-notification subscriptions
    1. In EvenTier:
    2. Admin → Settings → Integrations → Chat notifications → Add chat destination → Microsoft Teams
    3. In Teams, for webhook delivery:
    4. 1. Open the target channel and choose Workflows
    5. 2. Pick the "Send webhook alerts to a channel" template
    6. (trigger: When a Teams webhook request is received)
    7. 3. Save it and copy the workflow URL it gives you
    8. 4. Paste that URL into EvenTier
  4. 04

    Add a webhook

    Send request events to a URL in your own system.

    • Choose the events and paste your endpoint URL
    • Copy the signing secret; it is shown once
    1. Admin → Settings → Integrations → Webhooks → Add endpoint
  5. 05

    Store attachments in S3 (self-hosted)

    A self-hosted install can keep attachments in AWS S3, Cloudflare R2 or MinIO. Attachments and malware scanning has the settings.