Update Control D profile filters from Jira requests
Turn approved filter change tickets into a focused update on the intended Control D profile.
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
Modify Profile Filter
Tool to modify the enabled state of a specific filter on a profile. Use when you need to enable or disable a particular filter.
Why this helps
Filter change tickets can wait while someone locates the profile and manually applies the requested state.
- Apply a requested filter state with less context switching
- Keep the change connected to its Jira request
- Avoid guessing when profile or filter identifiers are unclear
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.
- 3Give Notis one instruction to apply approved filter requests, requiring the profile, filter identity, and enabled or disabled state before updating.
- 4Pick the Jira New Issue trigger for the configured project and choose where run reports should go.
- 5Test with one real filter request and verify the profile state.
Questions about this workflow
Can it decide whether a filter should be enabled?
Notis can interpret the request text, but your instruction should require an explicit intended state and approval before applying the change.
What if the filter is not identifiable by name?
Have Notis ask for clarification or retrieve the profile's available filters before updating. Do not let it select an uncertain filter.
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.