Skip to content
Notis

Connect Box to Jira

When something happens in Box, Notis takes the next step in Jira. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Fires when a Box collaboration’s details change.

Do this · Action

Upload and attach a file to an issue.

Examples

Ways Notis can move work from Box to Jira

Turn Box file feedback into a Jira issue

Create a Jira issue when a new Box file comment reports a defect, request, or actionable concern.

Update Jira when a Box file gets a new version

Use a new Box file version to refresh the description or review details on its related Jira issue.

Create Jira issues from new Box folder items

Turn new items arriving in a Box intake folder into Jira issues with their available file context.

Batch new Box files into Jira issues

Create Jira issues for new files added to a Box folder, grouping related intake into a bulk issue creation action.

Move Jira work when a Box Sign request changes

Transition the related Jira issue when a Box Sign request reaches a meaningful status, such as completion.

Refresh Jira when a Box task is resolved

Update a related Jira issue when a Box task assignment is completed, approved, or rejected.

Transition Jira when a Box task changes state

Move the related Jira issue when a Box task's status or completion details change.

Tell Jira when a Box file link changes

Add a Jira comment when a Box file's sharing settings change, so reviewers know the document access may have changed.

Refresh Jira when Box file details change

Update the related Jira issue when a Box file's name, description, location, or status changes.

Supported Triggers and Actions

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

Box triggers

Jira actions

Recurring trigger

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

TriggerScheduled

Add Attachment

Upload and attach a file to an issue.

ActionInstant

Webhook trigger

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

TriggerInstant

Add Comment

Add a rich-text comment to an existing issue.

ActionInstant

Collaboration Details Changed

Fires when a Box collaboration’s details change.

TriggerPolling

Add Watcher to Issue

Add a user to an issue’s watcher list.

ActionInstant

Comment Changed

Fires when a Box comment’s content or details change.

TriggerPolling

Add Users to Project Role

Adds users or groups to a Jira project role.

ActionInstant

New File Comment Added

Fires when a new comment is added to a Box file.

TriggerPolling

Add Field to Screen Tab

Adds a field to a Jira screen tab and updates linked project field associations by default.

ActionInstant

File Metadata Changed

Fires when a Box file’s metadata or properties change.

TriggerPolling

Assign Issue

Assign an issue to a user or default assignee, or leave it unassigned.

ActionInstant

File Shared Link Changed

Fires when a Box file’s shared link settings change.

TriggerPolling

Add User to Group

Adds a user to a group.

ActionInstant

New File Version Uploaded

Fires when a new version is uploaded to a Box file.

TriggerPolling

Bulk Create Issues

Create multiple issues in one action.

ActionInstant
Trigger Types

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 schedule (recurring or one-time), and a change in one of your Notis databases.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,700+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

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.

Any HTTP POSTCustom backendIoT event
Works with
ZapierPipedream
Most used

Scheduled triggers

Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.

Daily · 8:00Weekdays onlyOnce · Dec 13
Beta

Database triggers

Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.

Row addedProperty editedValue > limit
Why AI automation

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.

Classic automationAI automation
Cost
$ · pay per run
$$ · AI models per run
Reliability
Breaks on schema change
Adapts to format changes
Setup
Click 8 dropdowns
Describe it in English
Handles fuzzy
Hard-coded fields only
Reads intent, summarises
Human in loop
Bolted on
Built in · approval inbox
Maintenance
You own every break
Self-heals · we own it
Ease of use

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.

Notis

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:

TriggerRow added to "Q4 OKRs"
Condition✦Status = "Blocked"
AI step✦Summarise the blocker in plain English
ActionDM the row owner with summary
Timeout✦No reply in 24h → ping you
Observability

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

All12Manager5Telegram1Messages0WhatsApp2Email4Slack8

Migrate background jobs to a durable queue You can cancel it through Stripe

3 days

Notis v3 release update This one’s v3: Notis Manager (desktop app with …

8 days

Add multi-tenant RBAC User initiates a voice call

13 days

Draft pricing v (tiers, limits, overages) and sanity-check margins

2 weeks

Verify analytics events for new features That’s a really interesting automat…

1 month

Everything 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.

Related pairs

More ways to connect Box and Jira

Connect any two apps with Notis in the middle.

Box and Jira, or any other combination from 1,700+ 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.