Skip to content
Notis

Keep contact research current as Jira work changes

When a Jira issue is updated with new contact research, check whether that person has changed jobs and bring the result into the run report.

Trigger

Updated Issue

Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.

Action

Detect Job Change

Tool to detect if a contact changed jobs. Use when verifying a contact’s current employment details by email.

Why this helps

Contact details can go stale between research and outreach, leading to wasted follow-up or inaccurate assumptions.

  • Recheck current employment when relevant issue details change.
  • Catch potential job changes before acting on contact research.
  • Keep verification close to the Jira work that prompted it.

Setup

Build it in a few focused steps.

  • 1Connect Jira and Datagma once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and name it for contact verification.
  • 3In one instruction, ask Notis to check the named contact's current employment by email when an issue is updated, and summarize the result.
  • 4Choose the Jira Updated Issue trigger and select a channel for run reports.
  • 5Test with one real issue update that includes a contact email.

Questions about this workflow

Does this trigger on comments?

No. Jira Updated Issue does not fire for adding, editing, or deleting comments. It fires when an issue field changes in the configured project.

What does Datagma need for a job change check?

The action is intended to verify a contact's current employment details by email, so include the contact email in the issue information available to Notis.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Jira triggers

Datagma actions

Recurring trigger

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

TriggerScheduled

Detect Job Change

Tool to detect if a contact changed jobs. Use when verifying a contact’s current employment details by email.

ActionInstant

Webhook trigger

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

TriggerInstant

Enrich Person or Company

Enrich person or company data using LinkedIn URLs, emails, domains, or names. Returns enriched data including: contact information, LinkedIn profiles, company details, work experience, education, phone numbers (with phoneFull), and company metrics. Input types: LinkedIn profile URL (~100% success), email (~60% success), name+company (~90% success), company domain/name, or SIREN number (French companies).

ActionInstant

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Find Work Email

Find verified work email address for a person using their name and company. Returns a professionally verified email address with validation metadata including SMTP checks and MX records. Requires either fullName or firstName+lastName, plus company domain or LinkedIn company slug.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Get Credits

Get the current credit balance for the authenticated Datagma API account. Use this to check how many API credits remain before making enrichment calls.

ActionInstant

Updated Issue

Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.

TriggerInstant

Get Twitter Profile By Email

Retrieve Twitter account information associated with an email address. This action looks up Twitter username and display name for a given email address using Datagma's enrichment database. Returns Twitter username, display name, and the queried email if a match is found, or status 'NOT_FOUND' if no Twitter account is associated with the email. Use this when you need to: - Find someone's Twitter handle from their email address - Verify if an email has an associated Twitter account - Enrich contact data with social media information

ActionInstant

Get Twitter Profile by Username

Enrich Twitter profile data using Datagma's database. Returns contact information (email), social media profiles (LinkedIn, Facebook, GitHub), and professional details (skills, interests, industry) associated with a Twitter username. Note: Not all usernames are in Datagma's database. A 'not found' response (code 5) indicates the username hasn't been indexed yet.

ActionInstant

Reverse Phone Lookup

Tool to reverse-lookup information associated with a phone number. Use when you have a phone number and need associated details (e.g., carrier, location).

ActionInstant

Search Phone Numbers

Find mobile phone numbers using email address and/or LinkedIn profile URL. Returns list of phone numbers with confidence scores and optional WhatsApp verification. Best results when both email and LinkedIn URL are provided.

ActionInstant

Connect any two apps with Notis in the middle.

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