Check certificate operation permission
When a Linear issue requests a Digicert operation, check whether the connected account has the stated permission and report the result with the issue context.
When something happens in Linear, Notis takes the next step in Digicert. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Triggers when a new comment is received.
Do this · Action
Checks whether a permission is available to the authenticated user.
When a Linear issue requests a Digicert operation, check whether the connected account has the stated permission and report the result with the issue context.
When a Linear issue is updated with a new certificate operation or access requirement, check the corresponding Digicert permission and report whether it is available.
When a comment asks whether a Digicert permission is available for certificate work, check that permission and report the result in the run channel.
For a private-team Linear issue that explicitly requests an authorized new API key and includes a valid Digicert user ID and specified permissions, create the key and report the result securely.
When a private-team issue is updated to include an explicit approval, valid Digicert user ID, and permissions for a new key, create it and report the result with secure handling in mind.
When a private-team comment explicitly authorizes a new API key and gives a valid Digicert user ID and permissions, create the key and report the one-time result through the selected secure channel.
When a Linear project is created, list CertCentral account users and report the inventory so the project owner can review who may need access coordination.
When project properties change in Linear in a way that affects access planning, list CertCentral users and report the current inventory for a focused review.
When a Linear project status update calls out certificate access or ownership needs, list CertCentral users and report the inventory for follow-up.
Notis builds workflows that link Linear to Digicert. A trigger fires from one place; an action lands in another.
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Checks whether a permission is available to the authenticated user.
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Adds custom tags to certificates for categorization.
Triggers when a new comment is received.
Creates an API key with specified permissions.
Triggers when a new issue is created.
Retrieves the available API access roles.
Triggers when an issue is updated, such as when its labels or status change.
Retrieves a list of intermediate certificates.
Triggers when a comment is posted on an issue in a private team.
Creates an AuthKey that can be permanent or have a set validity period.
Triggers when an issue appears in a private team.
Retrieves users in a CertCentral account.
Triggers when an issue's properties change in a private team.
Adds an IP restriction rule to limit account access.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a schedule (recurring or one-time), and a change in one of your Notis databases.
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ apps can start a workflow.
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.
Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
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:
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.
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 monthWhatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
Every step can include an LLM call: summarise, classify, extract, rewrite.
Every run, every step, every input, all replay-able from Mission Control.
Pause for approval. Notis pings you in chat with one-tap approve.
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
Linear and Digicert, or any other combination from 1,500+ integrations.
When this happens · Trigger
Do this · Action
7-day trial of any paid plan, with $20 of usage included.
No card. Works with personal or business Digicert.