Keep collaborator communications organized as access changes
A new repository collaborator can trigger a contact update for your approved internal communication process.
Trigger
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Action
Upload Contacts Batch
Tool to upload or update multiple contacts in batch. use when you need to import or synchronize many contacts at once.
Why this helps
Access changes create communication follow-ups that are easy to defer.
- Keeps internal lists current
- Removes a manual handoff
Setup
Build it in a few focused steps.
- 1Connect GitHub and Remarkety to Notis once.
- 2Create a new automation in the portal.
- 3Tell Notis to upload or update the approved Remarkety collaborator contact batch after access is granted.
- 4Select the new-collaborator trigger and an internal report channel.
- 5Test it with one real collaborator addition.
Questions about this workflow
Can this be used for internal lists only?
Yes. State the approved contact group and communication purpose in the prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Remarkety. A trigger fires from one place; an action lands in another.
GitHub triggers
Remarkety actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Remarkety Campaigns
Tool to retrieve a list of marketing campaigns. use when you need to page through campaigns with optional limit and skip.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Remarkety Customers
Tool to retrieve customers. use when you need to fetch a paginated list of customers from a remarkety store.
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.
Get Remarkety Products
Tool to retrieve products. use when you need to fetch a paginated list of products from a remarkety store.
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.
Track Remarkety Cart
Tool to track cart events in remarkety. use after a customer updates their cart to sync cart data for remarketing.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Upload Contacts Batch
Tool to upload or update multiple contacts in batch. use when you need to import or synchronize many contacts at once.
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 Remarkety, 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 Remarkety.