Bring code context alongside every PDF bug report
Start with the report and get the likely source file ready for review.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
Bug details trapped in a PDF can mean a second search session before anyone can investigate.
- Put report details and source text together for a faster first pass.
- Reduce the need to switch between the PDF and code search.
- Give whoever picks up the issue a concrete starting point.
Setup
Build it in a few focused steps.
- 1Connect iLovePDF and Sourcegraph to Notis once in the portal.
- 2Open Automations, choose New Automation, and name it PDF bug report context.
- 3Write one prompt asking Notis to use the report details from the incoming iLovePDF webhook to identify a repository and file, then fetch that file from Sourcegraph.
- 4Select the incoming webhook trigger, choose a channel for run reports, and test with one real bug report.
Questions about this workflow
Does iLovePDF trigger this automation directly?
No. Notis starts it with an incoming webhook; an iLovePDF workflow or connected backend can send the processed report context to that webhook.
Will it change code or create an issue?
No. The Sourcegraph action fetches file contents for review; it does not modify code or create an issue.
When this happens · Trigger
Do this · Action
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.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
Get Commit Details
Get detailed information about a specific commit in a repository.
Get Current User
Tool to retrieve information about the currently authenticated user. use when needing confirmation of identity via sourcegraph graphql api.
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.
List Repositories
Tool to list repositories on the sourcegraph instance. use when you need to paginate through all available repositories.
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.
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.
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.