Skip to content
Notis

Find repository wiki topics relevant to Akta account questions

Start from the accounts you care about and see which topics in your repository wiki could help answer your questions.

Trigger

Recurring schedule

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

Action

Read wiki structure

View the documentation topics for a GitHub repository.

Why this helps

Teams often know which companies matter but not which repository documents can support a useful account conversation.

  • List available documentation topics for a specified repository.
  • Compare those topics with account questions you supply.
  • Spot documentation gaps without claiming the wiki covers topics it does not.

Setup

Build it in a few focused steps.

  • 1Connect Akta and Devin MCP once in the Notis portal.
  • 2Create an automation in Automations, New Automation, or tell Notis from your usual channel.
  • 3Describe the outcome: on each run, list the wiki topics for the specified repository, compare them with my supplied Akta account questions, and report matching topics and apparent gaps.
  • 4Pick a recurring schedule and choose where run reports should go.
  • 5Test with one repository and a short list of real account questions.

Questions about this workflow

Does this generate a wiki or add missing topics?

No. It reads the structure of an existing wiki and compares its topics with the questions you supply.

Can it tell whether a topic fully answers a question?

A topic list can indicate a possible match, but it does not establish that the documentation fully answers the question. The report should label matches as leads to inspect.

Does Akta supply the account questions automatically?

No. Provide the relevant account questions in the automation instructions. The listed Devin MCP action returns repository wiki topics.

When this happens · Trigger

Do this · Action

View the documentation topics for a GitHub repository.

Supported Triggers and Actions

Notis builds workflows that link Akta to Devin MCP. A trigger fires from one place; an action lands in another.

Akta triggers

Devin MCP actions

Recurring trigger

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

TriggerScheduled

Ask wiki question

Answers questions about a repository’s code using its DeepWiki.

ActionInstant

Webhook trigger

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

TriggerInstant

Devin automation manage

Manages Devin automations that run in response to events or schedules.

ActionInstant

Read wiki contents

View documentation for a GitHub repository.

ActionInstant

Devin billing tag manage

Manages billing tags used to group Devin sessions for usage tracking.

ActionInstant

Read wiki structure

View the documentation topics for a GitHub repository.

ActionInstant

Devin blueprint test

Tests a candidate blueprint by initializing it, fixing issues, and running maintenance.

ActionInstant

Devin code scan manage

Manage organization code scans; security profile edits take effect only after approval.

Conditions and details

Targets the authenticated organization. Code scanning must be enabled. Read actions require code scan view permission; creating or remediating scans requires code scan use permission. Creating a profile changes the organization’s scan configuration. Updating a profile changes only fields provided; omitted fields remain unchanged. Security profile edits are submitted for user approval and do not take effect until approved; a newer suggestion for the same profile replaces the pending one. Scans use only types enabled for the organization; organizations without general scans enabled can use only security scans. Non-security scans require a profile defining their objective. Scan creation requires the user to approve the exact proposed scan setup; a request to set up a scan is not approval to launch it. Remediation launches a session that modifies code and attempts to open pull requests, and is only for findings the user explicitly asked to remediate. Incremental scans add findings to the existing scan; they are available only after a completed run and cannot start while a run is active or before the first completed run. Changing a scan’s profile affects future incremental runs only; completed runs and findings are unaffected. Profile changes cannot be applied while a run is active. Creation effort is fixed. Scans do not carry their own MCP server grants; automation-launched scans use the automation’s grants and scan settings.

ActionInstant

Devin find setting

Finds a setting and returns a link to it in the Devin web app.

ActionInstant

Connect any two apps with Notis in the middle.

Akta and Devin MCP, or any other combination from 1,600+ 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 Devin MCP.