Keep collaborator properties current in Amplitude
Capture repository access changes in user properties, using a GitHub username as the Amplitude user ID.
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
Update User Properties in Amplitude
Update user properties using amplitude's identify api. this action allows you to: - set or update the user id for a device id - update user properties without sending an event - perform operations on user properties (set, append, etc.) - update user attributes like device info and location
Why this helps
Collaborator details can become stale when repository access changes are not reflected in the analytics profile you use.
- Update user properties when a collaborator is added.
- Use GitHub username as the Amplitude user ID for identification.
- Keep repository access context with the collaborator profile.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Amplitude once in the Notis portal.
- 2Create an automation and tell Notis to use the collaborator's GitHub username as the Amplitude user ID and update the relevant properties.
- 3Choose the New Repository Collaborator Added trigger.
- 4Choose where run reports go, then test with one real collaborator addition.
Questions about this workflow
What user ID will Amplitude use?
This workflow uses the collaborator's GitHub username as the Amplitude user ID, as specified in the instruction.
Will it remove a collaborator's access?
No. The trigger detects newly added collaborators and the Amplitude action updates user properties. It does not manage GitHub permissions.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Amplitude. A trigger fires from one place; an action lands in another.
GitHub triggers
Amplitude actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check Amplitude Cohort Status
Check the status of a cohort export request. this action allows you to: - poll the status of an in-progress cohort download request - determine if a cohort is ready for download
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Amplitude Event Category
Create a new event category in amplitude. this action allows you to: - create a new event category to organize event types - validate category name before creation key features: - creates event categories for organizing events - returns success/failure status
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.
Create Amplitude Event Type
Create a new event type in amplitude. this action allows you to: - define a new event type with various properties - associate the event with a category - add metadata like description, tags, and owner key features: - creates trackable events in your amplitude project - supports full event type configuration
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 Amplitude Event Category
Delete an event category from amplitude. this action allows you to: - delete an existing event category - remove category organization from events key features: - permanently removes event categories - returns success/failure status
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 Amplitude Event Type
Delete an event type from amplitude. this action allows you to: - remove an event type from your project - mark live events as deleted - remove planned events from the tracking plan key features: - different behavior based on event status (live, planned, etc.) - returns success/failure status
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.
Request Amplitude Cohort
Get a single cohort by id and initiate download. this action allows you to: - request a specific cohort from amplitude - optionally include user properties in the response - start the asynchronous download process key features: - supports filtering by specific user properties - returns a request id used for polling status and downloading - supports eu data residency
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.
Get Amplitude Event Categories
Get event categories from amplitude. this action allows you to: - get all event categories in your project - get a specific category by name
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.
Get Amplitude Event Type
Get a specific event type from amplitude by name. this action allows you to: - retrieve detailed information about a single event type - get all properties and metadata for the event key features: - retrieves comprehensive event type details - returns metadata like category, description, and settings - supports lookup by exact event name
Connect any two apps with Notis in the middle.
GitHub and Amplitude, 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 Amplitude.