Connect issue ownership with contact context
When an issue lands in your queue, Notis can check whether the person behind the request is already in Reply.io.
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
Search Contacts by Email
Tool to search contacts by email. use when you need to find existing contact ids for update tests.
Why this helps
Assigned work demands immediate context, but contact history is often another search away.
- Bring contact context into issue triage
- Reduce duplicate research
- Make urgent follow-up more deliberate
Setup
Build it in a few focused steps.
- 1Connect GitHub and Reply.io to Notis once through the portal.
- 2Create the automation with a plain-language instruction to search Reply.io for the relevant contact when an issue is assigned to you.
- 3Choose the new issue assigned to me trigger and select a reporting channel.
- 4Test with one assigned issue that has a known contact email.
Questions about this workflow
What if there is no matching contact?
Notis can report that no match was found so you know whether further research is needed.
Are pull requests included?
No. This GitHub trigger covers true issues only.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Reply io. A trigger fires from one place; an action lands in another.
GitHub triggers
Reply io actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Campaign
Tool to delete a campaign by id. use when you need to remove an existing campaign; use after confirming the campaign id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Email Account
Tool to delete a specific email account. use when you need to remove an existing email account identified by its id.
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.
Delete Sequence
Tool to delete a sequence. use after confirming the sequence exists to remove it permanently.
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.
Delete User
Tool to delete a user. use after confirming the user exists to remove them permanently.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Generate ULID
Tool to generate a ulid string. use when a unique identifier is required for creating tasks or other entities in reply.io.
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.
List Campaigns
Tool to list all campaigns (sequences). use when you need a paginated list of campaigns.
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.
Reply.io List Contacts
Tool to list all contacts. use when verifying api access and gathering contact ids for testing contact creation.
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.
Reply.io List Email Accounts
Tool to list all email accounts. use when you need to retrieve email accounts page by page.
Connect any two apps with Notis in the middle.
GitHub and Reply io, 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 Reply io.