Skip to content
Notis

Move completed customer work to its next Jira state

Carry a confirmed delivery completion into the Jira workflow so the team can close the loop.

Trigger

Webhook received

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

Action

Transition Issue

Transitions a jira issue to a different workflow state, with support for transition name lookup and user assignment by email.

Why this helps

Completed customer work can remain open in Jira when the final CRM update never reaches the delivery team.

  • Keep Jira workflow status aligned with confirmed customer delivery.
  • Require an explicit completion signal before transitioning.
  • Reduce manual cleanup after a customer milestone is finished.

Setup

Build it in a few focused steps.

  • 1Connect Capsule CRM and Jira once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and name the completion transition.
  • 3Tell Notis to transition the related Jira issue only when the webhook request confirms the agreed work is complete.
  • 4Pick the webhook trigger and choose where run reports should go.
  • 5Test with one completed deal and confirm the intended transition.

Questions about this workflow

Can this transition to any status?

Only transitions available for the issue can be used. Notis can retrieve available transitions to identify the requested one.

Does Capsule completion trigger it by itself?

No. Capsule provides no trigger event in this package. A webhook request must report the confirmed completion.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Capsule crm 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.

Capsule crm 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.