Always-Synced Issue Status Across Tools
Your team updates issues in GitHub but checks status in Airtable. When an issue is opened, closed, or reopened, Notis instantly updates the Airtable record so everyone sees the real status.
Trigger
Issue State / Properties Changed
Triggers when a specific GitHub issue changes any of its tracked properties. Monitored properties: state (open/closed), state_reason, title, body, assignees, labels, milestone, lock status, active_lock_reason, comment count, and closed_at timestamp. When a change is detected, the payload includes the full current issue details, the list of changed field names, and their previous values.
Action
Update record
Modifies specified fields of an existing record in an airtable base and table; the base, table, and record must exist.
Why this helps
Issues get closed in GitHub but remain 'open' in Airtable, creating confusion about what's actually done and what still needs work.
- Your project base always shows current status
- No stale records misleading the team
- One source of truth for issue state
Setup
Build it in a few focused steps.
- 1Connect GitHub and Airtable.
- 2Create an automation: 'When a GitHub issue's state changes (opened, closed, reopened), update the corresponding Airtable record to reflect the new status.'
- 3Select 'Issue State / Properties Changed' as the trigger.
- 4Choose your notification channel.
- 5Test by closing an issue in GitHub and checking Airtable.
Questions about this workflow
What if I manually change the status in Airtable?
Notis will overwrite it with GitHub's status next time the issue changes in GitHub. For manual Airtable-only tracking, use a separate field.
Does this sync other properties like title or description?
By default, only the status syncs. You can add 'also update title and description if they changed' to your prompt.
What about issues assigned to multiple people?
The sync works regardless of assignees. All assignees stay on the record.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Airtable. A trigger fires from one place; an action lands in another.
GitHub triggers
Airtable actions
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 base
Creates a new airtable base with specified tables and fields within a workspace; ensure field options are valid for their type.
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.
Create Comment
Creates a new comment on a specific record within an airtable base and table.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Create Field
Creates a new field within a specified table in an airtable base.
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.
Create multiple records
Creates multiple new records in a specified airtable table.
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.
Create a record
Creates a new record in a specified airtable table; field values must conform to the table's column types.
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.
Create table
Creates a new table within a specified existing airtable base, allowing definition of its name, description, and field structure.
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.
Delete Comment
Deletes an existing comment from a specified record in an airtable table.
Commit Event
Triggered when a new commit is pushed to a repository.
Delete multiple records
Deletes up to 10 specified records from a table within an airtable base.
Connect any two apps with Notis in the middle.
Not just GitHub and Airtable. Any combination from 985+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Airtable.