Connect 1password to Control d
When something happens in 1password, Notis takes the next step in Control d. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from 1password to Control d
Provision a Control D device from a 1Password request
Turn an approved 1Password device request into a new Control D device.
Audit Control D devices against a 1Password register
Run a scheduled inventory check and compare Control D devices with your 1Password register.
Clone a Control D profile for a new environment
Use an approved 1Password launch request to create a cloned Control D profile.
Review Control D profiles on a schedule
Get a recurring list of Control D profiles with notes from your 1Password operating register.
Apply approved domain rules from a 1Password change request
Create Control D custom rules from a reviewed domain change request.
File approved rules in a Control D folder
Create reviewed custom rules inside the correct Control D folder from a 1Password request.
Review Control D custom rules against documented exceptions
List Control D custom rules and flag differences from your 1Password exception log.
Update a Control D rule after security approval
Apply an approved change to an existing Control D rule by ID.
Check Control D schedules against the operating calendar
Review profile schedules and compare them with schedule records kept in 1Password.
Supported Triggers and Actions
Notis builds workflows that link 1password to Control d. A trigger fires from one place; an action lands in another.
1password 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.
Delete Profile Rule by Hostname
Tool to delete a specific custom rule by hostname from a profile. Use after confirming profile_id and hostname.
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.
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.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect 1password and Control d
Connect any two apps with Notis in the middle.
1password 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.