Connect 1password to Anonyflow

When something happens in 1password, Notis takes the next step in Anonyflow. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from 1password to Anonyflow

View example

Anonymize 1Password API keys before sharing

Protect API keys from 1Password before they are sent to a collaborator or external service.

View example

Anonymize expiring vault secrets for rotation planning

Create safe placeholders from 1Password secrets that are approaching rotation.

View example

Recover approved fields from an anonymized packet

Use a webhook to send an Anonyflow packet and recover only the fields needed for a 1Password task.

View example

Recover audit fields from protected packets

On a schedule, recover approved audit fields from Anonyflow packets associated with 1Password records.

View example

Deanonymize a one-time vault value

Recover a protected string from an incoming task when a founder needs the original value briefly.

View example

Restore protected values for scheduled maintenance

Recover selected anonymized values when a recurring maintenance task needs the originals.

View example

Check Anonyflow before a secret handoff

Verify Anonyflow is reachable before a 1Password based anonymization or recovery task proceeds.

View example

Monitor Anonyflow readiness for vault operations

Run a regular connection check so scheduled 1Password privacy workflows start with a known service state.

View example

Anonymize sensitive text from shared vault notes

Protect sensitive strings extracted from 1Password notes before they are sent to an AI assistant or teammate.

Supported Triggers and Actions

Notis builds workflows that link 1password to Anonyflow. A trigger fires from one place; an action lands in another.

1password triggers

Anonyflow actions

Recurring trigger

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

TriggerScheduled

Anonymize Value

Tool to anonymize a string or array of string values. use when you need to conceal sensitive text before storage or transmission. example: `anonymizevalue().execute(anonymizevaluerequest(data=['secret']))` limitations: only supports list of strings, not nested structures.

ActionInstant

Webhook trigger

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

TriggerInstant

Deanonymize Packet

Tool to deanonymize a json data packet using your private key. use after receiving an anonymized packet to recover specific fields.

ActionInstant

Deanonymize Value

Tool to deanonymize one or more anonymized string values. use when you need to recover the original plaintext values after encryption-based anonymization. example: `deanonymizevalue().execute(deanonymizevaluerequest(data=["<anonymized string>"]))`

ActionInstant

Test Connection

Tool to test the connection to the anonyflow api. use when verifying that the anonyflow service is reachable and operational before performing anonymization tasks. example: `testconnection().execute(testconnectionrequest())`

ActionInstant

Trigger Types

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.

New Notion pageStripe chargeCalendar event

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.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

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.

Row insertedValue > limitQuery match

Why AI automation

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.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

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:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

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.