Skip to content
Notis

Turn an Ably incident signal into a Control D profile update

When an incident signal arrives, give Notis the response you want and let it update the relevant Control D profile.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

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

During an incident, switching between an event stream and DNS policy settings can slow down a response.

  • Start a profile change from an incoming HTTP request carrying an Ably incident signal.
  • Keep the response instruction and the Control D change in one automation.
  • Send a run report to a channel you already check.

Setup

Build it in a few focused steps.

  • 1Connect Ably and Control D once in the Notis portal.
  • 2Create an automation in the portal or tell Notis from any channel to create one.
  • 3Describe the profile change Notis should make when the incident signal arrives.
  • 4Pick the webhook trigger and choose where run reports go.
  • 5Test with one real example, confirming the target profile and requested change.

Questions about this workflow

Does Ably provide a native trigger for this automation?

No. Ably has no trigger event in this setup. An HTTP request starts the automation, and the request can carry the incident details.

Can Notis infer which profile to update?

Include the intended profile or enough identifying context in the request or instruction. Notis should not guess a profile.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Ably to Control d. A trigger fires from one place; an action lands in another.

Ably triggers

Control d actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

Delete Profile Rule by Hostname

Tool to delete a specific custom rule by hostname from a profile. Use after confirming profile_id and hostname.

ActionInstant

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.

ActionInstant

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.

ActionInstant

Delete Profile Schedule

Tool to delete a specific schedule within a profile. Use after confirming profile_id and schedule_id.

ActionInstant

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.

ActionInstant

Get Analytics Endpoints

Tool to list analytics storage regions and their endpoints. Use after authenticating to retrieve available analytics regions.

ActionInstant

Connect any two apps with Notis in the middle.

Ably 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.