Keep Botpress workspace context close to changing Jira work
Refresh workspace visibility as Jira work changes, so finding the right Botpress environment takes less effort.
Trigger
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Action
LIST_WORKSPACES
Tool to retrieve a list of workspaces. use when you need to list and page through your botpress workspaces, optionally filtering by handle.
Why this helps
Workspace details often get lost between handoffs, causing repeat searches during Jira follow-up.
- Retrieve workspace context after issue changes.
- Support handoffs with a current workspace list.
- Reduce repeated manual searches.
Setup
Build it in a few focused steps.
- 1Connect Jira and Botpress once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis from any channel.
- 3In one instruction, ask Notis to retrieve Botpress workspaces and provide a concise workspace summary when an issue changes.
- 4Pick Jira Updated Issue as the trigger and choose where run reports should go.
- 5Test with one real Jira issue update and review the report.
Questions about this workflow
Does the workflow change a workspace?
No. The action only retrieves workspace information.
Will every Jira issue update trigger it?
The event fires for changes to existing issues in the configured Jira project.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Botpress. A trigger fires from one place; an action lands in another.
Jira triggers
Botpress actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete File
Tool to delete a file by its id or key. use after confirming the file exists.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Account
Tool to get details of the authenticated account. use after confirming valid credentials.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
LIST_BOT_ISSUES
Tool to list issues associated with a specific bot. use when you need to discover errors or configuration problems tied to a bot, optionally paginating through results.
New Project
Triggered when a new project is added in Jira
LIST_CONVERSATIONS
Tool to list all conversations. use when you need to retrieve and page through chat threads.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
LIST_FILE_TAGS
Tool to list all tags used across all bot files. use when you need to retrieve or display file tag metadata; supports pagination via nexttoken.
LIST_FILE_TAG_VALUES
Tool to list all values for a given file tag across all files. use after determining the tag name; supports pagination via nexttoken.
LIST_PUBLIC_WORKSPACES
Tool to retrieve a list of public workspaces. use when browsing publicly available workspaces before selection.
LIST_WORKSPACES
Tool to retrieve a list of workspaces. use when you need to list and page through your botpress workspaces, optionally filtering by handle.
Connect any two apps with Notis in the middle.
Jira and Botpress, 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 Botpress.