Connect GitHub to Tally
When something happens in GitHub, Notis takes the next step in Tally. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from GitHub to Tally
Turn new GitHub issues into focused intake forms
Create a Tally form for each new issue so founders can gather missing context without an inbox chase.
Create review forms for new pull requests
Open a short Tally review form whenever a pull request is created, keeping feedback structured and easier to act on.
Create triage forms for code scanning alerts
When a new code scanning alert appears, create a Tally triage form so the response is deliberate instead of stressful.
Create response forms for secret scanning alerts
Create a Tally incident response form when GitHub detects a possible exposed secret.
Update deployment feedback forms when status changes
Keep a release feedback form current as a GitHub deployment moves through its status changes.
Create follow-up forms after pull request reviews
Create a concise Tally follow-up form when a PR review is submitted, so requested changes become a visible plan.
Create discovery forms for new issues
When a new GitHub issue arrives, create a Tally discovery form to capture impact, urgency, and user evidence.
Refresh review forms for inline pull request feedback
Update an existing Tally review form when a new inline PR comment reveals a specific concern.
Create retrospective forms when checks fail
Create a short Tally learning form when a GitHub check run changes to a failed conclusion.
Supported Triggers and Actions
Notis builds workflows that link GitHub to Tally. A trigger fires from one place; an action lands in another.
GitHub triggers
Tally 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 after preparing block definitions and optional settings.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Webhook
Tool to create a new webhook for a form. use after confirming you have the form id and the callback url.
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.
Delete Form
Tool to delete a specific form identified by its id. use after confirming the form should be permanently removed.
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 Webhook
Tool to delete a specific webhook. use after confirming the webhook id.
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 Details
Tool to retrieve details of a specific form. use when you need comprehensive form metadata by id. use after confirming the form id to fetch its full configuration, blocks, and stats.
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 Form Fields
Tool to retrieve the fields of a specific form. use when you need the form's field definitions after obtaining its id.
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 Form Responses
Tool to retrieve the responses of a specific form. use after confirming the form id and when paginated data is needed.
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 Form Settings
Tool to retrieve the settings of a specific form. use after confirming the form id. example: "get settings for form abc123."
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect GitHub and Tally
Connect any two apps with Notis in the middle.
GitHub and Tally, 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 Tally.