Connect Linear to Loops.so
When something happens in Linear, Notis takes the next step in Loops.so. 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 Linear to Loops.so
Create a Loops contact from a Linear onboarding issue
When a new customer onboarding issue appears in Linear, create a Loops contact using the customer details present in the issue so the welcome process can start without re-entering information.
Trigger a Loops release-ready email event
When a Linear issue moves into a release-ready state, send a Loops event so an existing email workflow can notify the right customers about the product change.
Route customer feedback into a Loops follow-up event
When a comment on a Linear issue contains customer feedback or a requested follow-up, send a Loops event that can start the appropriate response email workflow.
Update contact context after a Linear account issue changes
When a customer-related Linear issue changes, update the matching Loops contact with the account context needed for customer success follow-up.
Start a Loops event when a customer milestone shifts
When Linear project properties change in a way that affects a customer milestone, send a Loops event to kick off the relevant status or expectation-setting message.
Send a Loops event from a Linear project update
When a Linear project update is posted, send a Loops event that can trigger a concise customer progress message for the audience tied to that project.
Start a customer follow-up when a Linear issue completes
When a customer-linked issue reaches completion in Linear, send a Loops event to start a resolution or next-steps email workflow.
Refresh a Loops contact after a customer issue priority change
When a Linear customer issue changes priority, update the matching Loops contact with the current support context so outreach reflects the latest urgency.
Signal a blocked customer issue to Loops
When a customer-impacting Linear issue becomes blocked, send a Loops event to trigger an internal escalation or carefully tailored status workflow.
Supported Triggers and Actions
Notis builds workflows that link Linear to Loops.so. A trigger fires from one place; an action lands in another.
Linear triggers
Loops.so actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Contact
Tool to add a new contact to your Loops audience. Use when you need to create a contact with email and optional properties like name, subscription status, or custom attributes. Returns 409 if contact already exists.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Contact Property
Tool to add a custom contact property to your Loops team. Use when you need to store additional contact data beyond default fields. Properties must have unique names in camelCase format and a specified data type (string, number, boolean, or date).
Comment Received Trigger
Triggered when a comment is received.
Delete Contact
Tool to delete a contact by email address or user ID. Use when you need to remove a contact from Loops. Either email or userId must be provided to identify the contact.
Issue Created Trigger
Triggered when a new issue is created.
Find Contact
Tool to search for a contact by email or userId. Use when you need to find a specific contact's details including subscription status and custom properties. Exactly one of email or userId must be provided per request.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Get Contact Properties
Tool to retrieve a list of your account's contact properties from Loops.so. Use when you need to view all available contact properties or filter to only custom properties created by your team.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Get Dedicated Sending IPs
Tool to retrieve a list of Loops' dedicated sending IP addresses. Use when you need to get IP addresses for whitelisting purposes.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Get Mailing Lists
Tool to retrieve all mailing lists associated with your Loops account. Use when you need to browse or manage mailing list information.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
List Custom Fields
Tool to retrieve a list of custom contact properties. Use when you need to view available custom fields for contacts. Note: This endpoint is deprecated in favor of 'List contact properties'.
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 Linear and Loops.so
Connect any two apps with Notis in the middle.
Linear and Loops.so, 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 Loops.so.