Skip to content
Notis

Keep Jira aligned with lead status updates

When a Callingly lead status update is submitted, tell Notis how to update the related Jira issue so follow-up stays aligned.

Trigger

Webhook received

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

Action

Edit Issue

Updates an existing jira issue with field values and operations. supports direct field parameters (summary, description, assignee, priority, etc.) that are merged with the fields parameter. direct parameters take precedence.

Why this helps

A lead's progress can change while a related Jira task still reflects an old state or next step.

  • Bring a submitted lead status update into the team's Jira work.
  • Keep the issue summary or description current with the latest provided context.
  • Make changes easier to see in the issue history.

Setup

Build it in a few focused steps.

  • 1Connect Callingly and Jira once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and name it for lead status updates.
  • 3Tell Notis to use each webhook request's lead status and issue reference to update the corresponding Jira issue with the supplied context.
  • 4Pick the webhook trigger and choose where run reports should go.
  • 5Test with one real status update and its related Jira issue.

Questions about this workflow

Will Notis choose a Jira workflow transition automatically?

This automation edits issue fields with the supplied status context. If you need a workflow state change, use a transition-specific instruction and verify the issue offers that transition.

Where does the new lead status come from?

It must be included in the webhook request or be available through the connected Callingly tools.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

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

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