Skip to content
Notis

Keep changing issues tied to real-world context

When an issue changes, the person behind it may matter more than the label. Refresh the context automatically.

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

Enrich Person or Company

Enrich person or company data using LinkedIn URLs, emails, domains, or names. Returns enriched data including: contact information, LinkedIn profiles, company details, work experience, education, phone numbers (with phoneFull), and company metrics. Input types: LinkedIn profile URL (~100% success), email (~60% success), name+company (~90% success), company domain/name, or SIREN number (French companies).

Why this helps

Issue priorities shift, but the founder often lacks the requester context needed to make a confident decision.

  • Make better reprioritization decisions
  • Notice important stakeholder changes
  • Reduce repeated investigation

Setup

Build it in a few focused steps.

  • 1Connect GitHub and Datagma to Notis once through the portal.
  • 2Create the automation in the portal or ask Notis to create it conversationally.
  • 3Tell Notis: When a GitHub issue's tracked properties change, enrich the issue author and explain any context relevant to reprioritizing it.
  • 4Pick the issue properties trigger, choose the run-report channel, and test with one updated issue.

Questions about this workflow

Which issue changes can start it?

The trigger covers tracked changes such as state, title, body, assignees, labels, milestone, and comment count.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link GitHub to Datagma. A trigger fires from one place; an action lands in another.

GitHub triggers

Datagma 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.

TriggerPolling

Detect Job Change

Tool to detect if a contact changed jobs. Use when verifying a contact’s current employment details by email.

ActionInstant

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.

TriggerPolling

Enrich Person or Company

Enrich person or company data using LinkedIn URLs, emails, domains, or names. Returns enriched data including: contact information, LinkedIn profiles, company details, work experience, education, phone numbers (with phoneFull), and company metrics. Input types: LinkedIn profile URL (~100% success), email (~60% success), name+company (~90% success), company domain/name, or SIREN number (French companies).

ActionInstant

New Branch Created

Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.

TriggerPolling

Find Work Email

Find verified work email address for a person using their name and company. Returns a professionally verified email address with validation metadata including SMTP checks and MX records. Requires either fullName or firstName+lastName, plus company domain or LinkedIn company slug.

ActionInstant

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.

TriggerPolling

Get Credits

Get the current credit balance for the authenticated Datagma API account. Use this to check how many API credits remain before making enrichment calls.

ActionInstant

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.

TriggerPolling

Get Twitter Profile By Email

Retrieve Twitter account information associated with an email address. This action looks up Twitter username and display name for a given email address using Datagma's enrichment database. Returns Twitter username, display name, and the queried email if a match is found, or status 'NOT_FOUND' if no Twitter account is associated with the email. Use this when you need to: - Find someone's Twitter handle from their email address - Verify if an email has an associated Twitter account - Enrich contact data with social media information

ActionInstant

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.

TriggerPolling

Get Twitter Profile by Username

Enrich Twitter profile data using Datagma's database. Returns contact information (email), social media profiles (LinkedIn, Facebook, GitHub), and professional details (skills, interests, industry) associated with a Twitter username. Note: Not all usernames are in Datagma's database. A 'not found' response (code 5) indicates the username hasn't been indexed yet.

ActionInstant

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.

TriggerPolling

Reverse Phone Lookup

Tool to reverse-lookup information associated with a phone number. Use when you have a phone number and need associated details (e.g., carrier, location).

ActionInstant

Commit Event

Triggered when a new commit is pushed to a repository.

TriggerInstant

Search Phone Numbers

Find mobile phone numbers using email address and/or LinkedIn profile URL. Returns list of phone numbers with confidence scores and optional WhatsApp verification. Best results when both email and LinkedIn URL are provided.

ActionInstant

Connect any two apps with Notis in the middle.

Not just GitHub and Datagma. Any combination from 1,000+ 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 Datagma.