Skip to content
Notis

Connect iLovePDF to Sourcegraph

When something happens in iLovePDF, Notis takes the next step in Sourcegraph. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Examples

Ways Notis can move work from iLovePDF to Sourcegraph

View example

Turn PDF bug reports into code context

When an iLovePDF workflow sends a processed bug report, fetch the relevant source file from Sourcegraph so investigation starts with code in view.

View example

Compare commits cited in release PDFs

When an iLovePDF-processed release document includes two commit references, ask Sourcegraph to compare those commits and return their file diffs.

View example

Check commit details for signed specifications

After an iLovePDF signing process sends a specification reference, retrieve the corresponding Sourcegraph commit details for a quick implementation check.

View example

Inventory files named in technical audit PDFs

When a processed audit PDF names a repository path, list its files in Sourcegraph to give the review a clear scope.

View example

Check repository languages from architecture PDFs

Use a language or repository reference in an iLovePDF-processed architecture document to retrieve the repository's language list from Sourcegraph.

View example

Find repositories referenced in vendor handoffs

When a processed vendor handoff PDF identifies a codebase, list repositories in Sourcegraph to help confirm the correct home for follow-up.

View example

Pull code context for PDF security findings

When an iLovePDF-processed security finding includes a repository and file path, fetch that file from Sourcegraph for focused review.

View example

Compare commits cited in incident timelines

When an incident timeline processed through iLovePDF names two commits and a repository, retrieve their Sourcegraph diff for investigation.

View example

Retrieve commit details for approval records

After an iLovePDF approval document reaches the webhook, look up its referenced commit in Sourcegraph to make the technical sign-off traceable.

Supported Triggers and Actions

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

iLovePDF triggers

Sourcegraph actions

Recurring trigger

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

TriggerScheduled

Check Site Settings Edit Permission

Tool to check whether site settings can be edited through the api. use when you need to confirm the api allows site settings edits before attempting configuration changes.

ActionInstant

Webhook trigger

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

TriggerInstant

Compare Commits

Tool to compare two commits in a repository and retrieve their file diffs. use after confirming the repository name and commit shas to inspect differences.

ActionInstant

Get Commit Details

Get detailed information about a specific commit in a repository.

ActionInstant

Get Current User

Tool to retrieve information about the currently authenticated user. use when needing confirmation of identity via sourcegraph graphql api.

ActionInstant

Get File Contents

Tool to fetch the contents of a specified file on the default branch. use when you need raw file text without cloning the repo or using a slower code-host api.

ActionInstant

List Repositories

Tool to list repositories on the sourcegraph instance. use when you need to paginate through all available repositories.

ActionInstant

List Repository Files

Tool to list all files and directories in a repository path. use when you need to enumerate files in a repository without cloning.

ActionInstant

List repository languages

Tool to list languages used in a repository. use when you need to determine the primary and all languages of a given repository; call after you have the repository name.

ActionInstant
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.

Notis

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.

  • 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

All12Manager5Telegram1Messages0Whatsapp2Email4Slack8

Migrate background jobs to a durable queue You can cancel it through Stripe

3 days

Notis v3 release update This one’s v3: Notis Manager (desktop app with …

8 days

Add multi-tenant RBAC User initiates a voice call

13 days

Draft pricing v (tiers, limits, overages) and sanity-check margins

2 weeks

Verify analytics events for new features That’s a really interesting automat…

1 month

Everything 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.

iLovePDF and Sourcegraph, 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 Sourcegraph.