Make Control D profile analytics a recurring task
Let a scheduled run bring profile analytics into the report channel you already check.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Profile Analytics
Tool to retrieve analytics data for a specific profile. Use after the profile has accrued usage data to fetch analytics.
Why this helps
Profile analytics can be missed when checking them depends on an open-ended reminder.
- Reduce the effort of starting each analytics review
- Set a dependable check-in for one profile
- Summarize available returned data in plain language
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.
- 3In one instruction, ask Notis to retrieve analytics for the chosen profile and summarize the available data, noting any missing reporting window or context.
- 4Pick a recurring schedule trigger and choose where run reports should go.
- 5Test with one profile that has accrued usage data.
Questions about this workflow
How is this different from an analytics summary?
This retrieves profile analytics data for review. If you want a date-specific summary, specify the desired date range and use the summary action.
What if the profile has no data yet?
Ask Notis to report that no usable analytics data was returned and avoid presenting an empty result as a trend.
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.