/ /
Slack Message Agent

The Slack Message Agent bridges Slack and DevRev, automatically creating DevRev issues, tickets, or incidents from Slack messages. With @mentions assignment enabled, it parses @mentions to auto-assign owners and spectators, posts confirmation links back in the thread, and prompts users when required context is missing.

For more information, refer to the Slack message agent on the DevRev marketplace.

Install

  1. Install the DevRev Slack app.

  2. Install the Slack message agent in your org.

Configure the custom Slack bot

  1. Go to Slack API and create a new app From scratch.

  2. Go to Basic Information β†’ App Credentials and copy the Signing Secret.
    β–Ž πŸ’‘ Save this somewhere safe β€” you'll need it when configuring DevRev.

  3. Add bot scopes
    Go to OAuth & Permissions β†’ Bot Token Scopes and add the following:

    Scope

    Purpose

    app_mentions:read

    Trigger on @bot mentions (required for @mention assignment)

    channels:history

    Read messages in public channels

    channels:join

    Allow bot to join channels

    channels:read

    Read  public channel metadata

    chat:write

    Post confirmation messages and prompts in threads

    files:read

    Download file attachments from messages

    groups: history

    Read messages in private channel

    groups: read

    Read private channel metadata

    metadata.message:read

    Read message metadata

    team:read

    Resolve workspace URL for Slack thread links

    usergroups:read

    Resolve @group mentions

    users:read

    Resolve @user mentions to display names

    users:read.email

    Map Slack users to DevRev users by email

  4. Click Install to Workspace (or Reinstall if updating scopes), then copy the Bot User OAuth Token.

  5. Go to Event Subscriptions β†’ toggle Enable Events to ON.

  6. Under Subscribe to bot events, add:

    1. app_mention β€” fires when someone @mentions the bot (required for @mention assignment flow)

    2. message.channels β€” fires on all public channel messages (for non-mention mode)

    3. message.groups β€” fires on all private channel messages (for non-mention mode)
      β–Ž ⚠️ Leave the Request URL blank for now. You'll paste the Trigger URL from DevRev in a later step.

  7. Add the bot to channels.

  8. Invite both the custom Slack bot and the DevRev Slack Bot into each Slack channel you want to monitor.

Configure DevRev

  1. Install the Slack Message Agent snap-in from the DevRev Marketplace.

  2. Under Keyrings, enter:

    1. Slack Signing Token β†’ the Signing Secret from step 2

    2. Slack Bot Token β†’ the Bot User OAuth Token from step 3

  3. Add Channel IDs for the object types you want to create:

    Input

    What it does

    Incident Channel IDs

    Messages in these channels create incidents

    Ticket Channel IDs

    Messages in these channels create tickets

    Issue Channel IDs

    Messages in these channels create issues

    β–ŽπŸ’‘ Finding a Channel ID: Right-click the channel name in Slack β†’ View channel details β†’ the ID is at the bottom of the panel.

    β–Žβš οΈ A channel should only appear in one list. Do not add the same channel to incident, ticket, and issue lists.

  4. Toggle the corresponding Sync switches to enable bidirectional custom field sync (Slack thread link, channel, timestamp) for each object type.

  5. Select a Part ID β€” the DevRev part to associate with created tickets and issues. Required when ticket or issue channels are configured.

  6. Select an Account ID β€” the default account for new rev users created from Slack. Required when ticket channels are configured.

  7. Toggle Enable @Mention Assignment to ON to activate the full assignment flow.

    Behavior

    When enabled βœ…

    When disabled ❌

    Owner assignment

    First @mentioned person becomes the owner

    owned_by is empty

    Spectators

    Additional @mentioned people added as watchers

    No watchers

    Title cleanup

    @mentioned names stripped from the title

    Names may appear in title

    Missing @mention

    Bot replies asking user to @mention an assignee

    Object created without owner

    File-only messages

    Bot prompts user to include a description

    Object created with minimal title

    Confirmation

    Bot posts DevRev link + assignees in thread

    No confirmation posted

    Forwarded messages

    Original message content used for title

    Same behavior

    Example:

    β–Ž A user posts: @bot @alice @bob Fix the login page

    β–Ž β†’ Agent creates an issue titled "Fix the login page"

    β–Ž β†’ Alice is set as owner, Bob as spectator

    β–Ž β†’ Bot posts a confirmation in the thread with the DevRev issue link

  8. Toggle Improve workflow line breaks to ON if you use Slack Workflow forms β€” this expands compact field formatting into separated paragraphs in DevRev.

  9. Click Save. The snap-in will display a Trigger URL.

  10. Go back to your Slack app β†’ Event Subscriptions β†’ paste the Trigger URL into the Request URL field. Slack will verify the URL automatically.

  11. Click Save Changes in Slack.

TroubleShooting

Issue

Solution

Bot doesn't respond

Ensure both the custom bot and DevRev Slack Bot are in the channel. Check that the channel ID is in the correct list.

Signature verification fails

Verify the Signing Secret matches your Slack app's Basic Information page.

Owner not set

Ensure the @mentioned Slack user has an email that matches a DevRev dev user. Check snap-in logs for No DevRev dev user found for email.

Duplicate channel error on activate

A channel ID appears in more than one list. Each channel must be in exactly one list.

Files not attached

Ensure the files:read scope is added and the file is under 250 MB.

Title contains bot name

Ensure Enable @Mention Assignment is toggled ON β€” this strips all @mentions from the title.

Bot posts "please @mention" even with mentions

Ensure at least one @mention besides the bot itself is in the message. The bot's own mention doesn't count as an assignee.

Was this article helpful?