Automatically Approve GitHub Workflows When Deals Close
Sales wins should unblock your engineering. When a deal closes in Hubspot, Notis automatically approves the pending GitHub workflow runs that were waiting for your green light.
Trigger
Deal Stage UpdatedTrigger
Deal Stage UpdatedTrigger
Action
Approve a workflow run for a fork pull request
Approves a workflow run from a forked repository's pull request; call this when such a run requires manual approval due to workflow configuration.
Why this helps
Workflow approvals sit waiting in GitHub while your sales team celebrates a closed deal. Your engineers don't know a deal closed, so deployment gets delayed.
- Deployments move automatically when deals close, not weeks later
- Your team sees immediate linkage between sales wins and code shipping
- Eliminates forgotten approval steps that block releases
- Keeps engineering momentum aligned with revenue milestones
Setup
Build it in a few focused steps.
- 1Connect Hubspot and GitHub to Notis.
- 2Ask Notis: 'When a deal moves to Closed Won, approve any pending GitHub workflow runs in [repository].'
- 3Select Deal Stage Updated as your trigger and specify 'Closed Won' stage.
- 4Choose your notification channel.
- 5Create a test workflow run and move a test deal to Closed Won to verify the approval fires.
Questions about this workflow
Does this approve all workflows or just specific ones?
You can specify. For example, 'approve workflows named Deploy Production' or 'approve any workflow with a specific label'.
What if there's no pending workflow?
Notis safely does nothing and logs that no approval was needed. No errors occur.
Can I pair this with other GitHub Actions?
Yes. Approved workflows can trigger downstream Actions like notifications, deployments, or rollouts.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Hubspot to GitHub. A trigger fires from one place; an action lands in another.
Hubspot triggers
GitHub actions
Contact Created Trigger
Contact Created Trigger
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Deal Stage UpdatedTrigger
Deal Stage UpdatedTrigger
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.
Not just Hubspot and GitHub. 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 GitHub.