Add registry context to company identifiers in Jira
When a new issue includes a Russian company identifier, have Notis retrieve the related registration details for review.
Trigger
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Action
Find Company or Entrepreneur
Tool to find company or individual entrepreneur details by inn, ogrn, or kpp. use when you have a valid identifier and need full registration data.
Why this helps
Company identifiers in issue text often require a separate registry lookup before the team can act.
- Retrieve company or entrepreneur registration data by INN, OGRN, or KPP.
- Cut out a manual lookup step during issue review.
- Give reviewers structured registry context alongside the issue.
Setup
Build it in a few focused steps.
- 1Connect Jira and Dadata ru once in the Notis portal.
- 2Create an automation with a name and prompt.
- 3Ask Notis to identify a valid INN, OGRN, or KPP in new issues, look up the matching party, and report the registry details.
- 4Pick Jira New Issue as the trigger and choose where run reports go.
- 5Test with one real issue containing a suitable identifier.
Questions about this workflow
Which identifiers can the lookup use?
Find Company or Entrepreneur supports INN, OGRN, or KPP.
Will it always return a company?
The lookup depends on a valid identifier and available registry data. Notis should report when no match is returned.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Dadata ru. A trigger fires from one place; an action lands in another.
Jira triggers
Dadata ru actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Clean Address
Tool to clean and standardize russian postal addresses. use when you need structured address fields from raw strings.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Clean Birthdate
Tool to standardize and validate birthdate strings. use after capturing raw birthdate inputs to normalize them to yyyy-mm-dd.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Clean Email
Tool to standardize and validate email addresses. use when you have raw email input and need to fix typos, correct domains, and classify as personal, corporate, or disposable. use after collecting user-provided emails.
New Project
Triggered when a new project is added in Jira
Clean Name (FIO)
Tool to standardize and parse full names (fio), detect gender, and return grammatical cases. use when you need structured name parsing and declensions from raw fio inputs.
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.
Clean Passport
Tool to validate a russian passport number against the official registry. use after collecting passport details.
Clean Phone
Tool to standardize and validate phone numbers. use when you need to convert arbitrary phone inputs into a uniform, validated 11-digit format for further processing.
Clean Vehicle
Tool to standardize and parse vehicle data fields. use after obtaining raw vehicle info to extract brand, model, year, vin, and other identifiers.
Find Address
Tool to find address by identifier. use when you need full address details from a cadastral number, fias id, or kladr code.
Connect any two apps with Notis in the middle.
Jira and Dadata ru, 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 Dadata ru.