Keep Control D profile details aligned with Jira changes
When the source request changes, carry its explicitly stated profile updates through to Control D.
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
Update Profile by ID
Tool to modify an existing profile by ID. Use when you need to update profile fields after confirming the current profile. Example: Update profile '123abc' with new name and settings.
Why this helps
A changed Jira request can leave the network profile reflecting old policy details unless someone notices and revisits it.
- Catch policy updates on existing Jira issues
- Reduce manual checking for changed requirements
- Require clear profile identity and new values before updating
Setup
Build it in a few focused steps.
- 1Connect Jira and Control D once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel to create one.
- 3In one instruction, have Notis update only the identified Control D profile fields explicitly changed in an approved Jira request, and ask for missing values.
- 4Pick the Jira Updated Issue trigger for the configured project and choose where run reports should go.
- 5Test with one real issue update and verify the resulting profile details.
Questions about this workflow
Will every Jira edit update a profile?
The trigger fires when an issue in the configured project changes. Instruct Notis to act only when the change is an approved policy update with a clear profile and intended values.
Does Jira provide the Control D profile identifier automatically?
Not necessarily. Include the profile identity in the issue or provide a reliable way for Notis to identify it. Have Notis ask when it cannot do so confidently.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Control d. A trigger fires from one place; an action lands in another.
Jira triggers
Control d actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Device by ID
Tool to delete a Control-D device. Use when you need to remove a device by its identifier after confirming the device_id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Profile by ID
Tool to delete a profile. Use when you need to remove a profile by its ID after ensuring it is not enforced by any device.
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 Profile Rule by Hostname
Tool to delete a specific custom rule by hostname from a profile. Use after confirming profile_id and hostname.
New Project
Triggered when a new project is added in Jira
Delete Profile Rule by Rule ID
Tool to delete a specific custom rule by its ID within a profile. Use after confirming profile_id and rule_id.
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 Profile Rule in Folder
Tool to delete a specific custom rule within a folder. Use after confirming profile_id, rule_id, and folder_id.
Delete Profile Schedule
Tool to delete a specific schedule within a profile. Use after confirming profile_id and schedule_id.
List Known Access IPs
Tool to list known IPs associated with the account. Use when you need to retrieve recent access IPs for device resolver queries.
Get Analytics Endpoints
Tool to list analytics storage regions and their endpoints. Use after authenticating to retrieve available analytics regions.
Connect any two apps with Notis in the middle.
Jira and Control d, 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 Control d.