← Change Slack setup choice

Selected path New Slack bot

Set up Jira Task Helper in Slack.

Complete the Slack app, agent settings, access rules, integrations, and final checks below.

01
SLACK API // WORKSPACE CREDENTIALS

Generate configuration tokens.

These workspace-level tokens let Agent Barn prepare a new Slack app. Generate both values and keep them ready for the next steps.

  1. 01.1

    Open Slack API → Your Apps.

    Go to api.slack.com/apps ↗, sign in, and confirm that you are working in the workspace where this agent should operate.

  2. 01.2

    Find “Your App Configuration Tokens.”

    Scroll near the bottom of the page and click Generate Token.

    Focused crop of the Slack App Configuration Tokens panel
    Slack API → Your Apps → App Configuration Tokens.
  3. 01.3

    Select the workspace and generate the pair.

    Choose the same workspace, then click Generate. Slack returns a configuration access token and an xoxe- refresh token.

    Slack Generate Your App Configuration Token workspace dialog
    1 // Select the workspace. 2 // Generate the token pair.
  4. 01.4

    Store both values securely.

    The access token authorizes app creation and expires after 12 hours. The refresh token rotates that access. Never place either value in chat, logs, prompts, or URLs.

  5. 01.5

    Submit the token pair in Agent Barn.

    Paste the configuration access token and xoxe- refresh token into their matching fields, then continue while the access token is still valid.

02
SLACK APP // PUBLIC IDENTITY

Define the bot identity.

Use recognizable, role-oriented metadata. These values are visible to teammates and can be changed later.

  1. 02.1

    Choose the display name.

    This name appears in Slack messages, mentions, and the app directory. Avoid secrets, environment names, or workspace-specific data.

    RECOMMENDEDAgentBarn_Jira_Task_Helper
  2. 02.2

    Write a one-sentence description.

    Describe the outcome teammates can expect rather than the implementation behind it.

    SUGGESTED

    Turns a plain-language request into a structured Jira task and files it for the team.

  3. 02.3

    Choose the icon background color.

    Pick a readable color that follows your workspace convention. Agent Barn orange is the recommended default.

    Aubergine#511152

    A familiar Slack-adjacent choice.

    Blue#1264A3

    Calm and conventional for utility bots.

    Green#2EB67D

    Useful for workflow or status-oriented agents.

    Amber#ECB22E

    High visibility for reminders and alerts.

    Agent Barn orange#CC4400

    Recommended for a consistent Agent Barn identity.

  4. 02.4

    Review the public metadata.

    Confirm that the name states the role, the description states the result, the color remains legible at small sizes, and no sensitive information is exposed.

  5. 02.5

    Create the app and confirm it appears in Slack.

    Save the identity in Agent Barn, complete app creation, then confirm the new app appears under Your Apps in the intended workspace before continuing.

03
SLACK API // SOCKET MODE

Connect the new Slack app.

Create the app-level token, install the bot, and store the two resulting credentials that Agent Barn needs.

Open Slack apps ↗
  1. 03.1

    Select the new app and verify its connection settings.

    Return to Your Apps ↗, open the app created for this recipe, verify the workspace, and confirm Socket Mode and the recipe's event subscriptions are enabled.

  2. 03.2

    Open App-Level Tokens and start a new token.

    In Basic Information → App-Level Tokens, click Generate Token and Scopes. The crop keeps the only control you need in view.

    Slack App-Level Tokens section focused on the Generate Token and Scopes button
    Basic Information → App-Level Tokens → Generate Token and Scopes.
  3. 03.3

    Name the Socket Mode token and add connections:write.

    Use a descriptive name such as agent-barn-socket. Add only connections:write, which lets Slack route Socket Mode events over WebSockets, then click Generate.

    Slack Generate an app-level token dialog with token name, connections write scope, and Generate button
    1 // Name the token. 2 // Confirm connections:write. 3 // Generate it.
  4. 03.4

    Copy the app-level token.

    Slack displays the xapp- token after generation. Click Copy, then keep it ready for the Agent Barn App-level token field. The token is blurred in this reference.

    Slack app-level token confirmation with the token value blurred and the Copy button highlighted
    The generated token has connections:write.
  5. 03.5

    Install the app to the workspace.

    Open Install App, then choose Install to [your workspace]. Review the requested permissions, make sure the workspace selector is correct, and choose Allow.

    Slack Install App page focused on the Install to workspace button
    Install App → Install to your workspace.
    Slack app permission review with workspace selection and Allow button
    1 // Confirm the workspace. 2 // Approve only after reviewing permissions.
  6. 03.6

    Find the Bot User OAuth Token after installation.

    After installation, Slack shows an OAuth Tokens section containing the Bot User OAuth Token. Click Copy and keep the xoxb- value ready for Agent Barn. The token is blurred in this reference.

    Slack Installed App Settings OAuth Tokens section with the token value blurred and the Copy button highlighted
    Installed App Settings → OAuth Tokens → Bot User OAuth Token → Copy.
  7. 03.7

    Enter both tokens in Agent Barn.

    Paste the xapp- value into App-level token and the xoxb- value into Bot token.

  8. 03.8

    Save and verify the connected app.

    Save both fields and confirm Agent Barn resolves the expected Slack app and workspace. Stop if either identity is wrong.

Keep them private

Enter Slack tokens only in their matching Agent Barn fields. Do not include them in messages or screenshots.

04
AGENT BARN // OPERATING BOUNDARIES

Configure how the teammate operates.

Work through these settings in order. Each controls a different part of the agent’s behavior or access.

  1. 04.1
    IDENTITY

    Name the teammate for its role.

    The operational name appears in dashboards and audit history. A short human name makes conversations and mentions easier.

    OPERATIONAL NAME

    AgentBarn_Jira

    Clear in dashboards and logs.

    SUGGESTED HUMAN NAME

    Juno

    Easy to mention and remember.

  2. 04.2
    MODEL

    Choose the model that performs the work.

    The model affects capability, speed, and cost. The supplied configuration shows DeepSeek: DeepSeek V4 Flash 0731. Confirm it is available and appropriate for this recipe’s complexity and data sensitivity.

    How to decide

    Use a fast model for structured, repeatable work. Use a more capable model for ambiguous context or nuanced reasoning. Evaluate representative tasks before granting broader access.

  3. 04.3
    COMMAND APPROVAL

    Decide when a human must approve commands.

    Start with the most restrictive mode that still makes the workflow useful.

    Command approval options: Auto, Manual, and Off
    Current default shown: Auto.
    RECOMMENDED START

    Auto

    Low-risk commands run automatically; higher-risk commands still require approval.

    MAXIMUM OVERSIGHT

    Manual

    The agent asks before every command. Best for pilots and sensitive systems.

    NO APPROVAL GATE

    Off

    All prompts are skipped. Use only with tightly sandboxed, narrowly scoped, reversible tools.

  4. 04.4
    CHANNEL ACCESS

    Choose which channels the agent may answer in.

    Slack controls which channels the app can see; this policy controls where the agent may respond.

    Channel access options: Allowlist and Open
    Current default shown: Allowlist.
    RECOMMENDED START

    Allowlist

    Respond only in approved channels. Best for pilots and team-specific workflows.

    BROAD AVAILABILITY

    Open

    Respond in any reachable channel. Use only for intentionally workspace-wide roles.

  5. 04.5
    DIRECT MESSAGES

    Control who can start private conversations.

    Direct messages remove shared-channel context and oversight. Enable them only when private interaction is genuinely needed.

    Direct message options: Off, Allowlist, and Open
    Current default shown: Off.
    RECOMMENDED START

    Off

    Ignore direct messages and keep work visible in approved channels.

    LIMITED PRIVATE ACCESS

    Allowlist

    Only designated operators and reviewers may send direct messages.

    WORKSPACE-WIDE DMS

    Open

    Anyone who can reach the app may DM it. Use only with strong identity and tool controls.

  6. 04.6
    VERBOSITY

    Choose how much work the agent narrates.

    This changes what teammates see while the agent works; it does not change capabilities or approvals.

    Verbosity options: Verbose and Concise
    Current default shown: Concise.
    VISIBLE EXECUTION

    Verbose

    Announces each step. Useful during onboarding, debugging, and supervised pilots.

    RECOMMENDED STEADY STATE

    Concise

    Provides final answers without narrating every intermediate step.

  7. 04.7

    Add the intended Slack destinations.

    Invite the app to each permitted channel. When Allowlist is selected, add the same channels and approved direct-message users in Agent Barn before testing.

  8. 04.8

    Configure the recipe trigger and workflow.

    Trigger: A teammate submits a request in an allowed Slack channel or direct message.

    1. Read request. Collect the request and its available context.

    2. Structure work. Prepare the title, description, and required task fields.

    3. Check gaps. Ask for missing information when the configured workflow requires it.

    4. File task. Create the Jira item and return its link to Slack.

  9. 04.9

    Apply the recipe requirements and review rule.

    Template

    The project-specific intake questions and ticket format.

    Skills

    Jira access and the actions permitted in the connected project.

    Policies

    Where intake is allowed and who can request ticket creation.

Suggested starting profile

Auto command approval · Channel allowlist · Direct messages off · Concise responses. Expand access only after representative tests and review of the agent’s tools and data boundaries.

05
AGENT BARN // TOOLS AND CREDENTIALS

Assign the skills this recipe needs.

Skills connect the agent to external platforms. Select only the integrations required for the workflow, then connect each one with a dedicated or approved shared credential.

REQUIRED

Jira

atlassian

Read project metadata and create structured issues in approved projects.

Credential
An Atlassian account email, site URL, and scoped or non-scoped API token.
Permissions
Projects: browse · Issues: create · Comments: add only when follow-up requires it
  1. Choose the target project and allowed issue types.
  2. Map required fields, components, and labels before launch.
  3. Create a test issue and verify the agent cannot write to projects outside scope.
  1. 05.1

    Keep required skills; resolve “choose one” integrations.

    Skills marked Required by template are part of this recipe’s workflow. When a card names alternatives, choose the provider your team actually uses. Optional skills should remain disconnected until a defined task needs them.

  2. 05.2

    Choose how each credential will be supplied.

    Choose Enter credentials to connect an account now. Choose Use shared credential when the correct workspace account is already connected.

    NEW CONNECTION

    Enter credentials

    Connect the account required by this recipe.

    EXISTING CONNECTION

    Use shared credential

    Select a matching account already available in Agent Barn.

  3. 05.A1

    Record the Atlassian site URL.

    This recipe connects to Jira. Copy only the site origin, for example https://aai-labs.atlassian.net. Omit Confluence space and Jira project paths.

    Atlassian browser address showing the site origin before a Confluence path
    Use the site origin only; omit everything after .net.
  4. 05.A2

    Confirm Jira and Confluence access.

    The API token inherits its Atlassian account’s product and content permissions. For Jira Task Helper, the required boundary is: Projects: browse · Issues: create · Comments: add only when follow-up requires it.

    One credential, verified twice

    When Jira and Confluence are both required, test the same credential against one permitted Jira item and one permitted Confluence page. Confirm locations outside the configured boundary remain unavailable.

  5. 05.A3

    Open Atlassian account security.

    Open the profile menu, choose Account settings, then open Security.

    Atlassian profile menu with Account settings
    1 // Profile menu → Account settings.
    Atlassian Account navigation with Security selected
    2 // Open the Security tab.
  6. 05.A4

    Open the API token manager.

    Choose Create and manage API tokens, then select a standard or scoped token. The choice must match the Authentication Type selected in Agent Barn.

    Atlassian Security page API tokens section
    Security → API tokens → Create and manage API tokens.
    Atlassian API Tokens page showing standard and scoped token actions
    Choose the token type deliberately.
    SHARED JIRA + CONFLUENCE

    Non-scoped token

    Can use the account’s Jira and Confluence permissions. Limit the account itself and verify both products before reuse.

    APP-SPECIFIC ACCESS

    Scoped token

    Limits API scopes. Create or reuse only a token whose selected app and scopes match the credential block.

  7. 05.A5

    Name, expire, and copy the token.

    Name it AgentBarn_Jira or another value that identifies the recipe. Choose an expiration date, create the token, and copy the value before closing the dialog.

    Atlassian Create an API token dialog
    Choose a recognizable name and expiration.
    Atlassian Copy your API token dialog
    Copy the token for Agent Barn.
  8. 05.A6

    Complete the Atlassian credential block.

    Enter the site origin, matching authentication type, account email, and API token. Jira and Confluence may use the same saved credential when the token mode and account permissions cover both products.

    SITE URL

    Shared Atlassian site origin.

    AUTHENTICATION TYPE

    Scoped or non-scoped.

    EMAIL

    Account that created the token.

    API TOKEN

    Token used for Jira and Confluence.

  9. 05.Z

    Validate every selected skill before hiring.

    Run one expected action and confirm the recipe cannot reach anything outside its selected accounts and resources. Resolve permission issues before choosing Hire.

06
FINAL CHECK

Verify the setup before launch.

Run this short review once Slack, Agent Barn, and the required skills are configured.

  • Confirm the app is installed in the intended Slack workspace.
  • Verify the xapp- and xoxb- values connect the intended Slack app.
  • Validate every required skill and confirm its credential has only the intended site, space, project, or repository access.
  • Test one representative request in an allowlisted channel.
  • Confirm higher-risk commands still trigger the expected approval path.
  • Review the agent’s response quality, visibility, and logs before expanding access.
  • Run the configured trigger: A teammate submits a request in an allowed Slack channel or direct message.
  • Confirm the result follows Read request → Structure work → Check gaps → File task.
  • Apply the review rule: Use project-specific required fields and keep any consequential prioritization or assignment with the responsible team.
RECIPE PATH COMPLETE

Jira Task Helper is ready for a controlled pilot.

Start with a narrow audience and reversible work, then widen access after observing representative tasks.

Return to recipes →