Find the Basin intake submission behind a new Jira issue
When a new issue arrives, Notis can check the relevant Basin submissions for the intake details your team may need.
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
Get Submissions
Tool to retrieve all submissions for a specific form. use when you need to list entries after obtaining the form id.
Why this helps
Issue context can be scattered between Jira and form responses, leaving someone to search for the original request.
- Bring related intake details into the run report.
- Make missing or ambiguous matches visible early.
- Cut down on manual searching across tools.
Setup
Build it in a few focused steps.
- 1Connect Jira and Basin once in the Notis portal.
- 2Create an automation named Check Basin intake submissions for a new Jira issue.
- 3Tell Notis which Basin form to check and how to match a submission to the new issue, such as by an issue key included in the response.
- 4Pick the Jira New Issue trigger and choose where run reports go.
- 5Test with one real issue and a related Basin submission.
Questions about this workflow
Does Basin automatically know which submission belongs to the Jira issue?
No. Tell Notis what form and matching information to use. A shared issue key or other reliable identifier must be present in the submission data.
What happens if no matching submission is found?
Instruct Notis to report that no match was found and identify any information needed to investigate.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Basin. A trigger fires from one place; an action lands in another.
Jira triggers
Basin actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Form
Tool to create a new form in basin. use when you need to automate form setup with name, timezone, and project association; optionally configure redirect, notifications, or spam protection.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Form Webhook
Tool to create a new webhook for a specific form. use when you need to programmatically add a webhook once you have the form id and callback url confirmed.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Create Notification
Tool to create a new notification webhook. use when you need to forward form submissions to an external service.
New Project
Triggered when a new project is added in Jira
Create Project
Tool to create a new basin project. use when you need a new organizational container for forms. example: "create a project named marketing leads."
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.
Delete Form
Tool to delete a form. use when permanently removing a form after it's no longer needed. ensure the form id is correct; this operation is irreversible.
Delete Integration
Tool to delete a form webhook integration. use when removing an obsolete integration by id.
Delete Project
Tool to delete a project. use when you need to remove a project after confirming its id. returns the deleted project's details.
Delete Webhook
Tool to delete a specific webhook. use when you need to remove a webhook from a form after confirming its id.
Connect any two apps with Notis in the middle.
Jira and Basin, 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 Basin.