Connect Jira to Botpress
When something happens in Jira, Notis takes the next step in Botpress. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Jira to Botpress
Check Botpress bot issues when Jira work starts
Use a new Jira issue as a cue to check the selected Botpress bot for related issues, so bot problems are visible while work is being planned.
Review Botpress issues when Jira work changes
When an existing Jira issue changes, review issues on the specified Botpress bot and report the current findings for context during follow-up.
Check Botpress conversations when Jira work opens
On new Jira work, retrieve Botpress conversations so relevant chat history can inform investigation or prioritization.
Revisit Botpress conversations when Jira changes
When Jira work changes, list Botpress conversations for a fresh review of customer chat context during investigation and follow-up.
Find Botpress workspaces when Jira work starts
Use new Jira work as a cue to list Botpress workspaces, helping teams identify the right workspace for a chatbot investigation.
List Botpress workspaces when Jira projects are added
When a Jira project is created, retrieve Botpress workspaces to support a quick inventory of the chatbot environments available to the team.
Refresh Botpress workspace context on Jira changes
When Jira issues change, retrieve Botpress workspaces to help keep workspace context available during ongoing chatbot work.
Review Botpress file tags when Jira work begins
On a new Jira issue, retrieve Botpress file tags and summarize the available content labels for chatbot investigation.
Recheck Botpress file tags as Jira issues change
Use Jira issue updates to refresh a view of Botpress file tags and make content metadata easier to revisit during follow-up.
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.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Jira and Botpress
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.