Skip to main content

Create Your First Vibe: Jira to Slack Automation

In this tutorial, you will build your first autonomous workflow ("Vibe") using Jinba. We will create a flow that monitors a Jira project for high-priority bugs and automatically posts a summary to a Slack channel.

Prerequisites​

  • Jinba App installed and running.
  • Access to a Jira Cloud instance.
  • Access to a Slack workspace.
  • (Optional) Git installed for cloning MCP servers.

Step 1: Define the Intent​

Open the Execution Canvas (the main chat window) and type your intent naturally.

Prompt:

"Check my 'Mobile App' Jira project for any High priority bugs created in the last 24 hours. If you find any, summarize them and post a report to the #engineering-alerts channel on Slack."

Step 2: Connection & Authentication (MCP)​

Jinba will analyze your request and detect that it needs access to Jira and Slack.

If these tools are not yet connected, Jinba will prompt you to configure the MCP Servers.

  1. Jira MCP Server:
    • Jinba will ask for your Jira URL, Email, and API Token.
    • Enter the details in the secure form provided.
  2. Slack MCP Server:
    • Jinba will ask for your Slack Bot User OAuth Token.
    • Enter the token.

Jinba securely stores these credentials in your local keychain.

Step 3: Vibe-to-UI Generation​

Once connected, Jinba will not just blindly run code. It will generate a Plan Preview.

You will see a structured card in the chat:

Proposed Action Plan

  1. Fetch: Query Jira JQL project = "Mobile App" AND priority = High AND created >= -24h
  2. Analyze: Summarize ticket descriptions using LLM.
  3. Action: Post message to Slack channel #engineering-alerts.

Action: Click "Approve Plan" to proceed.

Step 4: Execution & Visualization​

Jinba executes the workflow.

  1. Fetching Data: You will see a spinner next to the "Jira" icon.
    • Result: "Found 3 tickets: MOB-101, MOB-102, MOB-105."
  2. Reasoning: Jinba composes the summary.
  3. Posting: You will see a spinner next to the "Slack" icon.
    • Result: "Message posted successfully."

Step 5: Verify​

Check your Slack channel. You should see a neatly formatted message:

Daily Bug Report

  • MOB-101: Crash on login screen (Reported by @sarah)
  • MOB-102: Payment gateway timeout (Reported by @mike)

Generated by Jinba Vibe

Taking it Further​

You just vibe-coded a complex integration without writing a single line of Python or Glue code.

Next Ideas:

  • "Fix it" Flow: Ask Jinba to "Create a GitHub branch for MOB-101 and generate a fix based on the stack trace."
  • "Schedule it": Tell Jinba, "Run this flow every morning at 9 AM."

Explore more MCP capabilities in the AI Docs.