Quickly verify the stack named in an architecture PDF
Compare the document's assumptions with the repository's reported languages.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
A stack description can become stale, and verifying it manually adds another research step.
- Check a repository's reported languages against the document.
- Make architecture review more concrete.
- Reduce manual browsing before asking implementation questions.
Setup
Build it in a few focused steps.
- 1Connect iLovePDF and Sourcegraph to Notis once in the portal.
- 2Create a new automation named Architecture PDF language check.
- 3Write one prompt asking Notis to identify the repository from the incoming webhook context and retrieve its language list from Sourcegraph.
- 4Select the incoming webhook trigger, set the report channel, and test with an architecture PDF naming a known repository.
Questions about this workflow
Does the language list prove which frameworks are used?
No. It reports languages used in the repository and should be treated as a stack clue, not a full framework inventory.
What if the PDF mentions several repositories?
Have the prompt ask Notis to identify the specific repository relevant to the architecture note, or narrow the webhook context before testing.
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.