Keep track of Cincopa integration pull requests
Let Notis check a known pull request and report whether its integration change has merged.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Check if pull request merged
Checks if a specified github pull request has been merged, indicated by a 204 http status (merged) or 404 (not merged/found).
Why this helps
Important integration changes can be easy to forget when reviews and publishing work compete for attention.
- Keep a pending integration change visible
- Avoid repeated manual repository checks
- Get a simple status in your chosen report channel
Setup
Build it in a few focused steps.
- 1Connect Cincopa and GitHub once in Notis.
- 2Create an automation in the portal or tell Notis to create one in plain language.
- 3Ask Notis to check whether the specified GitHub pull request for the Cincopa integration has merged and report the result.
- 4Choose a recurring Notis schedule as the trigger.
- 5Choose where run reports go and test with one real pull request.
Questions about this workflow
Can this check any pull request automatically?
The instruction needs a specific repository and pull request, or another reliable way to identify the one to check.
Does the check merge the pull request?
No. It checks whether a specified pull request has already merged and reports the status.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Cincopa to GitHub. A trigger fires from one place; an action lands in another.
Cincopa triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Cincopa and GitHub, 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 GitHub.