Surface your Byteforms forms when a pull request gets reviewed
Make your existing forms easier to find during code review, when a workflow or integration change may affect how people submit information.
Trigger
Pull Request Review Submitted
Triggers when a new review is submitted for a GitHub pull request. Emits an event for each newly submitted review on the monitored pull request, covering all review types: APPROVED, CHANGES_REQUESTED, COMMENTED, and DISMISSED.
Action
Get all forms
Tool to fetch all forms created by the authenticated user. use after authentication to list existing forms.
Why this helps
A reviewer may need to check which forms exist, but finding them means leaving the review and searching a separate tool.
- Bring the current form list into a review workflow.
- Reduce context switching between GitHub and Byteforms.
- Make it easier to notice form-related changes during review.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Byteforms once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3In one instruction, ask Notis to fetch your Byteforms forms and summarize them for the submitted review context.
- 4Pick the Pull Request Review Submitted trigger.
- 5Choose a report channel, then test with one real review.
Questions about this workflow
Does the workflow change any forms?
No. This workflow fetches the forms list and reports it for context. The selected Byteforms action is Get all forms.
Can it identify forms related to a particular code change?
Notis can summarize the returned form list in the context of the review. Any link between a code change and a form must be apparent from the available information or supplied in your instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Byteforms. A trigger fires from one place; an action lands in another.
GitHub triggers
Byteforms actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create form
Tool to create a new form. use when you need to define and store a form structure.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Form
Tool to delete a form by its id. use when you need to remove an existing form permanently.
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.
Get all forms
Tool to fetch all forms created by the authenticated user. use after authentication to list existing forms.
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.
Get Form By ID
Tool to retrieve a specific form using its id. use when you need to fetch form details by providing the form's unique identifier.
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 Form Responses
Tool to retrieve responses for a specific form with optional pagination and filtering. use when the form has collected submissions and you need to navigate large result sets.
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 Byteforms, 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 Byteforms.