Review saved Melo searches from assigned GitHub issues
If an issue assigned to you explicitly asks for a saved-search inventory, Notis can retrieve your Melo searches and summarize them for review.
Trigger
New Issue Assigned to Me
Triggers when a new issue is assigned to the authenticated user. Fires an event for each GitHub issue that is newly assigned to the authenticated user. Pull requests are automatically excluded -- only true issues are emitted. Issues can optionally be filtered by labels and state. The payload includes the issue number, title, body, state, labels, assignees, creator, repository details, and timestamps.
Action
List Searches
Tool to list all searches. use after authenticating to retrieve the user's searches.
Why this helps
When property research is spread across tasks, it is easy to repeat a search or forget what you already saved.
- See existing Melo searches before starting another round of research.
- Tie the inventory back to the assigned issue that prompted the review.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Melo to Notis once in the portal.
- 2Create an automation in the portal or ask Notis for one in plain language.
- 3Tell Notis to list your Melo searches only when an assigned issue explicitly requests an inventory of saved property searches.
- 4Select the GitHub New Issue Assigned to Me trigger and choose where run reports should go.
- 5Test with one assigned issue that requests the saved-search inventory.
Questions about this workflow
Will this create or change a Melo search?
No. The List Searches action retrieves the user’s searches; this workflow only reports them for review.
Will it run for every issue assigned to me?
It is intended only for an issue that explicitly asks for an inventory of saved Melo property searches. The instruction should avoid unrelated issues.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Melo. A trigger fires from one place; an action lands in another.
GitHub triggers
Melo actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Cities
Tool to retrieve a list of cities with optional filters. use when you need to fetch available cities before processing location-specific data.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Searches
Tool to list all searches. use after authenticating to retrieve the user's searches.
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Location Autocomplete
Tool to fetch location autocomplete suggestions. use when you have a partial location query and need possible matching locations from melo api. supports filtering by country and location type. use after forming the query string.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Simulate Webhook
Tool to simulate sending a webhook event. use when testing webhook integrations. call after configuring endpoint and payload.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Connect any two apps with Notis in the middle.
GitHub and Melo, 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 Melo.