Skip to content
Notis

Keep Jira documentation work current with Botpress content changes

When Botpress content changes, a scheduled Notis review can keep the related Jira documentation task aligned with what changed.

Trigger

Recurring schedule

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

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

Bot content updates can leave related Jira documentation or review tickets describing an older version.

  • Keep related Jira work informed about confirmed Botpress content changes.
  • Preserve a concise change summary on the issue.
  • Reduce manual comparison between bot content and open tasks.

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 review Botpress content available to it and update a referenced Jira issue only when the related task and confirmed change are clear.
  • 4Pick a recurring schedule and choose where run reports should go.
  • 5Test with one real content change and its related Jira issue.

Questions about this workflow

Does Botpress provide a change event for this workflow?

No Botpress trigger events are listed here. A Notis schedule starts the review, which can analyze content available through the connection.

How does Notis find the related Jira task?

Include the issue key in the content or your instructions, or define a reliable reference. Ask Notis to report changes without a clear match.

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.