Check recent social activity when a workflow run changes
Pair a workflow run state change with a fresh look at Ayrshare post history to review recent publishing activity in context.
Trigger
GitHub Workflow Run State Changed
Triggers when a GitHub Actions workflow run's status or conclusion changes. Monitors a single workflow run and fires an event whenever it transitions between states (e.g., queued to in_progress, or in_progress to completed) or when its conclusion is set (e.g., success, failure, cancelled).
Action
Get Post History
Tool to retrieve ayrshare post history with metrics. use when you need to fetch and filter past posts by date, status, or record count.
Why this helps
A deployment or automation run can finish while social activity stays in a separate dashboard, making a quick review harder.
- Retrieve post history when a workflow run changes state.
- Review recent posts and available metrics in the same automation run.
- Use Notis to summarize returned history without manually switching dashboards.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Ayrshare once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3In one instruction, tell Notis to retrieve Ayrshare post history after the run change and summarize the returned records and metrics.
- 4Pick GitHub Workflow Run State Changed as the trigger, then choose where run reports go.
- 5Test with one real workflow run state change and review the run report.
Questions about this workflow
Does post history include a specific time range?
The available action retrieves post history with metrics and can filter by date, status, or record count. Specify the review window you want in the instruction.
Can this tell whether a post caused a deployment result?
No. It can summarize returned post history alongside the run context, but it cannot establish causation or data the apps do not provide.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Ayrshare. A trigger fires from one place; an action lands in another.
GitHub triggers
Ayrshare actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Auto Schedule
Tool to create a new auto-post schedule with specified times and optional weekday filters. use when setting up recurring posting plans.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete a previously published Ayrshare post
Tool to delete an ayrshare post. use when you need to remove a published or scheduled post by its ayrshare post id, after confirming the correct id. note: instagram and tiktok published posts cannot be deleted via api; set `mark manual deleted=true` or remove manually.
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 Post History
Tool to retrieve ayrshare post history with metrics. use when you need to fetch and filter past posts by date, status, or record count.
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.
Set Auto Schedule
Tool to set up an auto-post schedule with specified times and optional weekday filters. use when scheduling posts around a recurring pattern.
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 Ayrshare, 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 Ayrshare.