Skip to content
Notis

Find the right Elorus contact from an updated Jira issue

When a Jira issue changes and needs client follow-up, Notis can look up the Elorus contact using the identifier you provide.

Trigger

Updated Issue

Action

Get Contacts

Retrieve your contacts.

Why this helps

Finding a client's record in another system adds a search task at the moment you need to respond to a work update.

  • Reduce manual contact searches after Jira changes.
  • Use a client identifier supplied by the issue or instruction.
  • Get a contact lookup result for the next follow-up step.

Setup

Build it in a few focused steps.

  • 1Connect Jira and Elorus once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a name.
  • 3In one instruction, tell Notis when an issue change needs a client lookup and which supplied identifier to use to retrieve the Elorus contact.
  • 4Pick Jira's Updated Issue trigger and choose where run reports should go.
  • 5Test with one real issue update that includes a usable client identifier.

Questions about this workflow

Does the workflow change contact details?

No. It uses Get Contacts to retrieve contacts. Updating a contact would require a separate action and an explicit instruction.

What if the issue has no client identifier?

The workflow should report that the identifier is missing and avoid guessing which contact to retrieve.

Does every issue edit trigger this workflow?

Jira's Updated Issue event fires when an existing issue in the configured project changes. Your instruction can tell Notis which changes require a contact lookup.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Jira triggers

Elorus actions

Recurring trigger

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

TriggerScheduled

Create Invoice

Create an invoice or receipt, saved as a draft by default.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Expense

Creates an expense from categorized line items.

ActionInstant

Comment Created

TriggerInstant

CREATE_PRODUCT

Create a product or service in the catalog.

ActionInstant

Comment Deleted

TriggerInstant

Email Invoice

Email an existing invoice to selected contacts.

ActionInstant

Comment Updated

TriggerInstant

Get Bills

Retrieve bills for viewing and managing expenses or purchases.

ActionInstant

Issue Created

TriggerInstant

Delete Invoice

Permanently deletes a draft invoice; issued invoices cannot be deleted.

ActionInstant

Issue Deleted

TriggerInstant

Get Contacts

Retrieve your contacts.

ActionInstant

Issue Updated

TriggerInstant

Get Credit Notes

Retrieve credit notes.

ActionInstant

Connect any two apps with Notis in the middle.

Jira and Elorus, 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 Elorus.