Connect Linear to Tinyurl

When something happens in Linear, Notis takes the next step in Tinyurl. 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 Linear to Tinyurl

View example

Create a short link for each new Linear issue

When a Linear issue is created, shorten its URL and return the TinyURL for easy sharing.

View example

Shorten links shared in Linear comments

When a Linear comment arrives, have Notis identify a URL in it and create a short link for quick sharing.

View example

Create a short link when a Linear issue changes

When an issue is updated, shorten its URL if the issue now contains a link that your instruction identifies for sharing.

View example

Review your TinyURL links on a schedule

Have Notis periodically retrieve available or archived TinyURLs so you can review the links relevant to Linear work.

Supported Triggers and Actions

Notis builds workflows that link Linear to Tinyurl. A trigger fires from one place; an action lands in another.

Linear triggers

Tinyurl actions

Recurring trigger

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

TriggerScheduled

Create short url

Create a shortened version of a URL.

ActionInstant

Webhook trigger

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

TriggerInstant

List TinyURLs

ActionInstant

Comment Received Trigger

Triggers when a new comment is received.

TriggerInstant

Issue Created Trigger

Triggers when a new issue is created.

TriggerInstant

Issue Updated Trigger

Triggers when an issue is updated, such as when its labels or status change.

TriggerInstant

Private Team Comment Created

Triggers when a comment is posted on an issue in a private team.

TriggerPolling

Private Team Issue Created

Triggers when an issue appears in a private team.

TriggerPolling

Private Team Issue Properties Updated

Triggers when an issue's properties change in a private team.

TriggerPolling

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.