Investigate Alchemy contract alerts with Devin
When an Alchemy alert arrives, give Devin the contract context and a repository question so you can see relevant code without switching tools.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Ask question
Why this helps
A contract alert can be hard to assess when its on-chain details and the code that might explain them live in separate places.
- Ask a focused question about a contract event and a named repository in one workflow.
- Surface relevant code context while the alert is fresh.
- Keep the investigation grounded in the event details and repository you provide.
Setup
Build it in a few focused steps.
- 1Connect Alchemy and Devin MCP once in the Notis portal.
- 2Create an automation in Automations, New Automation, or describe it to Notis from any channel.
- 3Tell Notis to pass the incoming contract address, network, event details, and your question to Devin for the specified repository.
- 4Choose Webhook as the trigger and select where run reports should go.
- 5Test with one real alert and confirm the repository and question are clear.
Questions about this workflow
Does Alchemy start this workflow directly?
Alchemy has no listed trigger event here. Notis starts it when an HTTP request reaches its Webhook, such as from an external alerting setup that sends the Alchemy event details.
What should I include in the request?
Include the network, contract address, relevant event details, the GitHub repository in owner/repo format, and a specific question. Notis cannot infer a link between a contract and a repository.
Can Devin confirm what happened on-chain?
This action asks Devin about repository code. Include the on-chain details from Alchemy in the question; the action does not query Alchemy itself.
When this happens · Trigger
Do this · Action
Answers questions about a repository’s code using its DeepWiki.
Supported Triggers and Actions
Notis builds workflows that link Alchemy to Devin MCP. A trigger fires from one place; an action lands in another.
Alchemy triggers
Devin MCP actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Ask wiki question
Answers questions about a repository’s code using its DeepWiki.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Devin automation manage
Manages Devin automations that run in response to events or schedules.
Read wiki contents
View documentation for a GitHub repository.
Devin billing tag manage
Manages billing tags used to group Devin sessions for usage tracking.
Read wiki structure
View the documentation topics for a GitHub repository.
Devin blueprint test
Tests a candidate blueprint by initializing it, fixing issues, and running maintenance.
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.
Devin find setting
Finds a setting and returns a link to it in the Devin web app.
Connect any two apps with Notis in the middle.
Alchemy 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.