Make deployment changes easier to interpret
A deployment change can signal a customer-facing shift. Use it to trigger the right market context.
Trigger
GitHub Deployment State Changed
Triggers when a specific GitHub deployment's fields change. Monitors the following aspects of a single deployment: - ``environment`` -- the target environment name - ``original_environment`` -- the original environment name before normalization - ``description`` -- the human-readable deployment description - ``task`` -- the deployment task name - ``sha`` -- the commit SHA being deployed - ``ref`` -- the branch, tag, or SHA reference being deployed - ``updated_at`` -- the last-updated timestamp - ``transient_environment`` -- whether the environment is temporary - ``production_environment`` -- whether this is a production deployment When any of these fields change, an event is emitted containing the full current deployment details and a list of which fields changed.
Action
Search Meta Ads
Search the meta ad library.
Why this helps
Operational changes are easy to handle technically but harder to connect back to messaging and customer impact.
- Links operational changes to customer-facing context
- Highlights relevant market claims
- Creates a consistent review prompt for sensitive changes
Setup
Build it in a few focused steps.
- 1Connect GitHub and Adyntel to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to set it up.
- 3Tell Notis: When deployment details change, search Meta ads for messaging related to the affected environment or product area and summarize relevant implications.
- 4Select the deployment state change trigger, choose the run-report channel, and test with one changed deployment.
Questions about this workflow
Which deployment changes matter most?
Describe the environments or product changes worth reviewing in the plain-language instruction.
Does this deploy anything?
No. It only performs and reports an Adyntel market search.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Adyntel. A trigger fires from one place; an action lands in another.
GitHub triggers
Adyntel actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Google Ads By Company
Retrieve all google ads for a given company domain.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Search Meta Ads
Search the meta ad library.
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.
Search TikTok Ads
Tool to search for ads on tiktok using a keyword. use when you want to find ads related to a specific topic.
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.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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 Adyntel, 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 Adyntel.