Connect Linear to Headout
When something happens in Linear, Notis takes the next step in Headout. 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 Headout
Find destination options for a new offsite
When a Linear issue requests an offsite location, look up active Headout cities and share a concise shortlist for planning.
Show activity categories for the offsite city
When a Linear planning issue gains a city or location detail, retrieve Headout activity categories for that city and report them with the issue context.
Browse Headout collections for an offsite
For a new Linear issue planning an offsite, fetch Headout collections in the named city and share relevant collections with the organizer.
Narrow city activities into subcategories
When a Linear trip-planning issue is updated with a city, retrieve Headout subcategories there to make activity discovery more focused.
List experiences for a new destination request
When a Linear issue requests team activities in a named city, retrieve Headout product listings for that city to give the planner options to review.
Pull listings after an activity category is chosen
When a Linear issue is updated to identify an activity category, retrieve Headout products for that category so the planner can review concrete options.
Check inventory when someone asks in Linear
When a comment on a Linear planning issue asks whether a selected Headout variant is available, retrieve its inventory and pricing for review.
Fetch product details from a Linear comment
When a Linear comment asks for details about a specified Headout product, retrieve its product information and post a concise summary for the discussion.
Retrieve product facts for a private planning thread
When a private-team Linear comment requests details about a Headout product, retrieve its available product information for the team's review.
Supported Triggers and Actions
Notis builds workflows that link Linear to Headout. A trigger fires from one place; an action lands in another.
Linear triggers
Headout actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Product By ID
Tool to retrieve detailed product information by product ID. Use when you need comprehensive product details including pricing, images, location, variants, and availability.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Categories V2
Tool to fetch all available activity categories for a specific city using V2 API. Use when you need to list categories of activities available in a particular city location.
Comment Received Trigger
Triggered when a comment is received.
List Cities
Tool to list all active cities with pagination support. Use when you need to retrieve available cities from the Headout platform. Supports pagination through offset and limit parameters.
Issue Created Trigger
Triggered when a new issue is created.
List Collections V2
Tool to fetch all collections for a specific city using V2 API with pagination support. Use when you need to browse collections available in a particular city, with optional language-specific content and pagination controls.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
List Inventory by Variant
Tool to retrieve available inventory and pricing for a specific product variant. Use when you need to check availability and pricing details for booking.
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).
List Products By Category
Tool to list product listings filtered by category ID with pagination support. Use when you need to retrieve products for a specific category.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
List Products V2
Tool to fetch products using Headout V2 API with filtering by city, collection, category, or subcategory. Use when you need to retrieve product listings for specific locations or categories with pagination support.
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 Subcategories V2
Tool to fetch all subcategories for a specific city using V2 API. Use when you need to list subcategories of activities available in a particular city location.
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 Headout
Connect any two apps with Notis in the middle.
Linear and Headout, 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 Headout.