Keep outreach lists aligned with reality
When a relationship changes, your mailing list should catch up without a cleanup project.
Trigger
Issue State / Properties Changed
Triggers when a specific GitHub issue changes any of its tracked properties. Monitored properties: state (open/closed), state_reason, title, body, assignees, labels, milestone, lock status, active_lock_reason, comment count, and closed_at timestamp. When a change is detected, the payload includes the full current issue details, the list of changed field names, and their previous values.
Action
Delete Recipient from Mailing List
Tool to remove a recipient from a mailing list. use after confirming the recipient's id.
Why this helps
Old contacts stay on outreach lists because list maintenance competes with product work.
- Reduces outdated outreach
- Prevents forgotten list cleanup
- Keeps operational records trustworthy
Setup
Build it in a few focused steps.
- 1Connect GitHub and Thanks io to Notis once.
- 2Create the automation in the portal or ask Notis to create it.
- 3Tell Notis to remove the matching recipient from the specified Thanks io mailing list when the configured issue property change indicates outreach should stop.
- 4Choose the issue-properties trigger, select the report channel, and test with one qualifying issue.
Questions about this workflow
Can the workflow require a specific label?
Yes. Describe the label or property that should authorize removal.
What if there is no confident recipient match?
Ask Notis to skip the deletion and report the mismatch.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Thanks io. A trigger fires from one place; an action lands in another.
GitHub triggers
Thanks io actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Recipient to Mailing List
Tool to add a new recipient to a mailing list. use after confirming recipient and list ids.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Mailing List
Tool to create a new mailing list. use when you need to group contacts under a fresh list before adding recipients.
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 Mailing List
Tool to delete a mailing list. use when you need to remove an entire mailing list by its id. confirm the list id before calling. example: "delete the mailing list with id 123e4567-e89b-12d3-a456-426614174000".
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 Recipient from Mailing List
Tool to remove a recipient from a mailing list. use after confirming the recipient's id.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Delete Sub-Account
Tool to delete a specific sub-account by id. use when you need to remove an existing sub-account. confirm the id before calling.
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.
Execute Stored Send
Tool to execute a previously created stored send. use after creating a stored send to trigger delivery. the response body is empty; success is indicated by a 200 or 204 status.
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.
List Handwriting Styles
Tool to retrieve available handwriting styles. use when selecting a style for handwritten personalization.
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.
List Image Templates
Tool to retrieve a list of available image templates. use when you need to browse or select a template for mailings.
Connect any two apps with Notis in the middle.
GitHub and Thanks 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 Thanks io.