Check DeployHQ project details from a Jira launch request
See the project context you need to move a launch request forward without switching tools to hunt for it.
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 Project
Tool to view an existing project in DeployHQ. Use when you need to retrieve details about a specific project by its permalink or identifier.
Why this helps
Launch requests arrive without clear deployment context, leaving you to search DeployHQ by hand.
- Surfaces relevant project details alongside a new launch request.
- Highlights missing project identifiers for follow-up.
- Reduces manual context switching.
Setup
Build it in a few focused steps.
- 1Connect Jira and DeployHQ once in the Notis portal.
- 2Create an automation in the portal or tell Notis in plain language, then name it.
- 3In one instruction, ask Notis to identify launch requests and summarize the matching DeployHQ project details, calling out missing identifiers.
- 4Pick Jira New Issue as the trigger and choose where run reports go.
- 5Test with one real launch request and confirm the project summary is useful.
Questions about this workflow
Does this create a DeployHQ project?
No. It retrieves project details and reports them. Creating a project requires a separate automation using DeployHQ Create Project.
What if the issue does not identify a DeployHQ project?
Notis can report that the identifier is missing instead of guessing which project to inspect.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to DeployHQ. A trigger fires from one place; an action lands in another.
Jira triggers
DeployHQ actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Command
Tool to delete a command from a specified project. Use when you need to remove an SSH command from a project's configuration.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Project
Tool to delete a project from DeployHQ. Use when you need to permanently remove a project by its permalink or identifier.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Delete Build Cache File
Tool to delete an existing build cache file from a project. Use when you need to remove a cached build artifact from the project's build cache storage.
New Project
Triggered when a new project is added in Jira
Delete Excluded File Rule
Tool to delete an existing excluded file rule from a project. Use when you need to remove an excluded file pattern from deployment configuration.
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 Server Group
Tool to delete a server group from a project using the DeployHQ API. Use when you need to remove a server group from deployment configuration.
Delete Template
Tool to delete a template by its unique permalink. Use when you need to permanently remove a template from DeployHQ.
Get Projects
Tool to retrieve all projects from DeployHQ account. Use when you need to list all available projects and their configurations.
Get Project
Tool to view an existing project in DeployHQ. Use when you need to retrieve details about a specific project by its permalink or identifier.
Connect any two apps with Notis in the middle.
Jira and DeployHQ, 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 DeployHQ.