Turn approved Linear contact requests into Campayn contacts
When a Linear issue contains an approved subscriber request with the required contact details and destination list, create that contact in Campayn and report the result.
When something happens in Linear, Notis takes the next step in Campayn. 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
Creates a new contact in a list.
When a Linear issue contains an approved subscriber request with the required contact details and destination list, create that contact in Campayn and report the result.
When a Linear comment asks for a contact check and gives a Campayn contact ID, retrieve the contact details and report them in the run channel.
When a Linear issue is updated to indicate an explicitly approved removal and identifies the Campayn contact, delete that contact and report the outcome.
When a Linear issue update records approval for a list rename and identifies the Campayn list and new name, update that list and report the result.
When a Linear comment asks about a specific Campayn list and includes its ID, retrieve its details for the run report.
When a new Linear issue requests an audience review and names a Campayn list, retrieve its contacts and report the result for review.
When a new Linear project is created for an email launch, retrieve the available Campayn lists so the team can identify the intended audience.
When a Linear launch project's target date changes, retrieve Campayn email report metadata for the relevant date range and share the results in the run channel.
When a Linear project update identifies a Campayn message and asks for a detail check, retrieve the message details for the run report.
Notis builds workflows that link Linear to Campayn. 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.
Creates a new contact in a list.
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Permanently deletes a contact.
Triggers when a new comment is received.
Deletes a contact list.
Triggers when a new issue is created.
Deletes a webform from a Campayn contact list; the API may report success if it does not exist.
Triggers when an issue is updated, such as when its labels or status change.
Retrieves the details of a specific contact.
Triggers when a comment is posted on an issue in a private team.
Retrieves contacts from a contact list.
Triggers when an issue appears in a private team.
Retrieves all available contact lists.
Triggers when an issue's properties change in a private team.
Retrieves an email message's engagement statistics, or reports an error if all are absent.
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 Campayn, 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 Campayn.