See the top domains in a Control D profile regularly
Spot the domains shaping profile activity without starting each review from scratch.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Profile Analytics Top Domains
Tool to fetch top domains accessed within a specific profile. Use after confirming profile ID.
Why this helps
Useful domain patterns can be overlooked when analytics reviews depend on someone remembering to run them.
- Make recurring domain review easier to remember
- Surface high-activity domains in a consistent report
- Focus review on a selected profile
Setup
Build it in a few focused steps.
- 1Connect Control D once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel to create one.
- 3Ask Notis in one instruction to retrieve and summarize top domains for the chosen profile and reporting window, calling out when the data lacks context.
- 4Pick a recurring schedule trigger and choose where run reports should go.
- 5Test with a profile that has analytics data and confirm the selected window.
Questions about this workflow
Does this block any of the domains it finds?
No. This workflow retrieves top domains for review. Any policy changes should be handled in a separate workflow with an explicit approved instruction.
Can it tell whether a domain is unusual?
Only if you supply a baseline or the returned data supports the comparison. Otherwise it can report the top domains without claiming they are unusual.
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.