Skip to content
Notis

Keep Jira company context aligned with Akta

Refresh an issue when company details need another look, so the Jira discussion has useful context close at hand.

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

Jira issues can retain outdated company context after the underlying profile or enrichment has changed.

  • Refresh existing issue context from company intelligence
  • Keep research discussions grounded in current information
  • Start the update from an HTTP request

Setup

Build it in a few focused steps.

  • 1Connect Akta and Jira once in the Notis portal.
  • 2Create an automation in Automations, then New Automation, and give it a name.
  • 3Describe in one instruction which issue context to update from the Akta company profile.
  • 4Choose a webhook trigger and where run reports should go.
  • 5Test with one real company profile and its Jira issue.

Questions about this workflow

Will the workflow overwrite all issue fields?

Describe which context should be refreshed. The Jira Edit Issue action updates an existing issue with supplied values and operations.

How do I identify the correct Jira issue?

Provide its issue key or other identifying context in the HTTP request and explain how Notis should use it.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

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

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