Keep Customer Voice Connected to Your Code
Customer feedback gets buried in Monday tasks and Slack messages. Notis archives feedback as Gist comments so future developers understand user needs tied to the code they're reading.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Update Gist Comment
Tool to update a Gist comment. Use when you need to modify an existing comment after confirming the gist_id and comment_id.
Why this helps
Months later, developers ask 'why was this feature built?' but the original customer feedback is lost in archived tasks. Decision context is gone.
- Customer voice stays with the code
- Future developers understand user context
- Searchable feedback history
- Better product decisions informed by history
Setup
Build it in a few focused steps.
- 1Connect Gist and Monday to Notis in the portal
- 2Create an automation named 'Customer Feedback Archive'
- 3In the Prompt, write: 'When a Monday task about customer feedback, feature request, or user need is marked complete, extract the feedback and add it as a comment to the associated Gist with the user name and date'
- 4Set Trigger to webhook and choose your notification channel
- 5Test by completing a customer feedback task that references a Gist
Questions about this workflow
How does it know which Gist to update?
Include the feature or code Gist ID in the Monday task. Notis will link the feedback to that specific implementation.
Can it include the customer name and feedback date?
Yes. Notis automatically includes metadata like who provided the feedback and when, making the feedback history traceable.
What if feedback is negative or critical?
All feedback is archived neutrally. Both positive and critical feedback provide valuable context for why code was built a certain way or changed over time.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Monday to Gist. A trigger fires from one place; an action lands in another.
Monday triggers
Gist actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check Gist Star
Tool to check if a gist is starred. Use when you need to determine if the authenticated user has starred a specific gist.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Gist Comment
Tool to delete a comment on a gist. Use when you have both the gist_id and comment_id and want to remove that comment. Example prompt: "Delete comment 42 from gist 'aa5a315d61ae9438b18d'".
Get Gist
Tool to retrieve a specific gist by its ID. Use when you have a gist_id and need complete gist details.
Get Gist Comment
Tool to get a specific comment on a gist. Use when you need to retrieve details of a particular comment given gist_id and comment_id.
Get Gist Revision
Tool to retrieve a specific gist revision. Use when you need details of a past state for an existing gist by commit SHA.
List Gist Comments
Tool to list comments on a gist. Use after confirming the gist_id to retrieve comments for a specific gist. Example: 'List comments for gist abc123'.
List Gist Commits
Tool to list the commit history of a gist. Use after you have the gist ID to review its revisions.
List Gist Forks
Tool to list forks of a gist. Use after obtaining a gist_id to retrieve all forks for the gist.
Connect any two apps with Notis in the middle.
Monday and Gist, 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 Gist.