Make collaborator onboarding easier to repeat
A new collaborator should receive context before they need to ask for it.
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
List templates
This tool retrieves a list of all available templates in the echtpost account. templates serve as the base design for postcards and are essential for creating cards. the action operates independently using only an authentication token and returns detailed template information including id, name, description, preview url, type, and creation time. this action is crucial for viewing templates before creating cards and obtaining the necessary template ids for subsequent actions.
Why this helps
Access can be granted quickly while onboarding context remains scattered across memory and messages.
- Creates a repeatable onboarding cue
- Encourages secure sharing of relevant context
- Reduces early confusion for new collaborators
Setup
Build it in a few focused steps.
- 1Connect GitHub and Echtpost to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it in plain language.
- 3Use this instruction: When a new GitHub collaborator is added, list Echtpost templates suitable for a secure welcome and concise onboarding note based on the collaborator role.
- 4Select the new collaborator trigger, choose the reporting channel, and test with one collaborator event.
Questions about this workflow
Can it adapt to permission level?
Yes. Ask Notis to recommend different templates for read, write, maintain, or admin access.
Does it share credentials?
No. Never include secrets in the prompt or message.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Echtpost. A trigger fires from one place; an action lands in another.
GitHub triggers
Echtpost actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List templates
This tool retrieves a list of all available templates in the echtpost account. templates serve as the base design for postcards and are essential for creating cards. the action operates independently using only an authentication token and returns detailed template information including id, name, description, preview url, type, and creation time. this action is crucial for viewing templates before creating cards and obtaining the necessary template ids for subsequent actions.
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 Echtpost, 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 Echtpost.