Move Jira work forward after integration confirmation
When a required integration step completes, move the related Jira issue to the next state without a manual status check.
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
Teams can leave completed work waiting in Jira because nobody noticed the integration confirmation or updated the workflow state.
- Transition the Jira issue named in the confirmation request.
- Reduce manual checking after a prerequisite completes.
- Keep the Jira workflow aligned with the integration milestone.
Setup
Build it in a few focused steps.
- 1Connect Celigo and Jira once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis what you want from any channel.
- 3Tell Notis to transition the identified Jira issue to the requested next state when a Celigo confirmation webhook arrives.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real confirmation and verify the issue's available transitions.
Questions about this workflow
Can the workflow move an issue to any state?
The transition must be available for that issue in Jira. The Jira action can look up a transition by name.
What should the webhook include?
Include the Jira issue identifier and enough confirmation context to support the requested transition.
Will it update issues without a confirmation?
No. This workflow is triggered by a confirmation request sent to the Notis webhook.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Celigo to Jira. A trigger fires from one place; an action lands in another.
Celigo triggers
Jira actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Attachment
Uploads and attaches a file to a jira issue.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
Link Issues
Links two jira issues using a specified link type with optional comment.
Create Project
Creates a new jira project with required lead, template, and type configuration.
Connect any two apps with Notis in the middle.
Celigo 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.