Make collaboration feel connected from day one
Access is only the beginning. Give new collaborators a clear view of the impact they are helping build.
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
Get Total Carbon Offset
This tool retrieves the total carbon offset and other forest-related information for the authenticated user. it provides comprehensive data about the user's forest, including the total co₂ captured, number of trees planted, gifted, and received. authentication is provided via an api key in the headers (x-api-key) and no additional parameters are needed as it fetches data for the authenticated user.
Why this helps
Onboarding often focuses on permissions and tools while the team's shared purpose remains implicit or easy to miss.
- Adds mission context to an existing onboarding event
- Reduces the chance of forgetting welcome follow-up
- Helps collaborators understand the broader outcome of their work
Setup
Build it in a few focused steps.
- 1Connect GitHub and More trees to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it by chat.
- 3Use this instruction: When a new GitHub collaborator is added, retrieve my More trees forest totals and send me a welcome note with the collaborator and repository details.
- 4Select the new collaborator added trigger and choose the reporting channel.
- 5Test it when adding a trusted collaborator.
Questions about this workflow
Does it grant access to More trees?
No. It only retrieves your authenticated More trees totals for the welcome report.
Can the note include the person's role?
Yes. Ask Notis to include the available collaborator permission context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to More trees. A trigger fires from one place; an action lands in another.
GitHub triggers
More trees actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Total Carbon Offset
This tool retrieves the total carbon offset and other forest-related information for the authenticated user. it provides comprehensive data about the user's forest, including the total co₂ captured, number of trees planted, gifted, and received. authentication is provided via an api key in the headers (x-api-key) and no additional parameters are needed as it fetches data for the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
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.
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 More trees, 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 More trees.