Collect onboarding feedback after README updates
Find out whether your updated setup guidance is actually easier to follow.
Trigger
GitHub Repository README Changed
Triggers when the README file in a specific repository directory changes. Monitors the README in a configurable directory and branch/tag/commit. The payload includes the current README metadata (filename, path, SHA, size, URLs), the previous and current git blob SHAs, and a list of which tracked fields changed.
Action
Send Transactional Survey
Tool to send a transactional survey to customers. use when you need to send a survey to a customer after a specific event, with an optional delay.
Why this helps
Documentation improvements are hard to validate without a deliberate customer check-in.
- Validates documentation changes
- Keeps learning lightweight
Setup
Build it in a few focused steps.
- 1Connect GitHub and Retently to Notis once.
- 2Create an automation from the portal.
- 3Write a prompt to send a survey after a tracked onboarding README changes.
- 4Pick the README-change trigger and the channel for reports.
- 5Test with one real documentation update.
Questions about this workflow
Is a portal field-mapping setup needed?
No. Describe the audience and outcome in one prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Retently. A trigger fires from one place; an action lands in another.
GitHub triggers
Retently actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Feedback Tags
Add tags to feedback items by providing feedback ids and corresponding tags.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Feedback Topics
Add topics to feedback items by providing feedback ids and corresponding topics.
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 or Update Customers
Tool to create new customers or update existing ones by providing their details, including email, name, company, tags, and properties. use this to manage your customer base in retently.
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 Customers
Delete customers from the workspace by providing their unique ids.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get Campaigns
Tool to retrieve a list of campaigns associated with the account. use when you need to get details about all campaigns.
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.
Get Customer By ID
Tool to retrieve detailed information about a specific customer by their unique id. use when you need to get all the details of a customer.
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 Customers
Retrieve a list of customers with optional parameters for pagination, sorting, and filtering by email or date range.
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 Feedback
Tool to retrieve feedback received from customers. use when you need to get a list of feedback, with optional parameters for pagination and sorting.
Connect any two apps with Notis in the middle.
GitHub and Retently, 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 Retently.