Skip to content
Notis

Update Jira issues with clarified Botpress requirements

When a Botpress exchange clarifies what a user needs, ask Notis to update the related Jira issue with the confirmed details.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

Action

Edit Issue

Updates an existing jira issue with field values and operations. supports direct field parameters (summary, description, assignee, priority, etc.) that are merged with the fields parameter. direct parameters take precedence.

Why this helps

Requirements clarified in conversation can fail to make it back into the Jira ticket that guides implementation.

  • Keep confirmed requirements with the work item.
  • Reduce retyping after a clarification conversation.
  • Make changes traceable through the Jira issue history.

Setup

Build it in a few focused steps.

  • 1Connect Botpress and Jira once in the Notis portal.
  • 2Create an automation and give it a clear name.
  • 3In one instruction, ask Notis to extract only confirmed requirements from the supplied Botpress conversation and update the referenced Jira issue.
  • 4Pick the webhook trigger and choose where run reports should go.
  • 5Test with one real clarification exchange and its Jira issue.

Questions about this workflow

What if the conversation contains uncertain details?

Tell Notis to leave uncertain details out of the update and report what still needs confirmation.

How should the issue be identified?

Include the Jira issue key in the webhook request or conversation context so Notis can target the intended issue.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Botpress to Jira. A trigger fires from one place; an action lands in another.

Botpress triggers

Jira actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Add Attachment

Uploads and attaches a file to a jira issue.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Add Comment

Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.

ActionInstant

Add Watcher to Issue

Adds a user to an issue's watcher list by account id.

ActionInstant

Assign Issue

Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.

ActionInstant

Bulk Create Issues

Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.

ActionInstant

Create Issue

Creates a new jira issue (e.g., bug, task, story) in a specified project.

ActionInstant

Link Issues

Links two jira issues using a specified link type with optional comment.

ActionInstant

Create Project

Creates a new jira project with required lead, template, and type configuration.

ActionInstant

Connect any two apps with Notis in the middle.

Botpress and Jira, or any other combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Jira.