Connect Tinyurl to Openperplex
When something happens in Tinyurl, Notis takes the next step in Openperplex. 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 Tinyurl to Openperplex
Scan competitors from a TinyURL
Send a TinyURL to Notis and get a focused web search for competitor changes on the linked page.
Weekly market pulse from saved links
On a schedule, use TinyURL links you've supplied to Notis as starting points for a streaming search on market changes.
Make a readable brief from a TinyURL
Send a known article TinyURL to a Notis webhook and retrieve the page as markdown for a concise reading brief.
Capture a page snapshot from a TinyURL
Request a screenshot of the confirmed public destination behind a TinyURL for a quick visual check.
Daily digest of linked reading
On a schedule, extract the main text from specified public pages behind TinyURLs and prepare a compact reading digest.
Ask a question about a linked source
Submit a TinyURL and a question to Notis, then have Openperplex query the linked document for an answer.
Search your saved sources each month
Revisit selected TinyURL sources monthly with an Openperplex document search focused on a standing founder question.
Stream market changes into a morning check-in
Start the day with streaming search results for the market question you ask Notis to monitor.
Research a customer question from a link
Send a TinyURL and a customer question to Notis for a tailored search that adds outside context.
Supported Triggers and Actions
Notis builds workflows that link Tinyurl to Openperplex. A trigger fires from one place; an action lands in another.
Tinyurl triggers
Openperplex actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Custom Search
Tool to perform a custom search with optional filtering and field selection. use when you need tailored results based on query, filters, size, or fields.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Custom Search Stream
Tool to perform custom streaming search. use when you need real-time search results for given queries.
Get Website Markdown
Tool to retrieve the markdown content of a specified website. use after confirming the url. supports optional formats like 'gfm' or 'commonmark'.
Get Website Screenshot
Tool to capture a screenshot of a website. use after confirming the target url is reachable.
Get Website Text
Tool to retrieve the main text content of a specified website url. use when you need content extraction from online articles or pages. use after confirming the url is publicly accessible.
Query from URL
Tool to query documents from a url. use when you need to fetch and interrogate web-hosted content with a natural language question.
Search Documents
Tool to search documents using query parameters. use when you have a search query and optional filters ready.
Search Stream
Tool to stream search results from openperplex. use when real-time updates on search results are needed.
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.
Connect any two apps with Notis in the middle.
Tinyurl and Openperplex, 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 Openperplex.