Keep Coupa purchase orders current with GitHub updates
When a procurement issue gets a useful update, have Notis place that context on the Coupa purchase order named in the comment.
Trigger
New GitHub Issue Comment
Triggers when a new comment is added to a specific GitHub issue. Only genuinely new comments are emitted; edits to existing comments do not produce duplicate events. The payload includes the comment ID, text body, author details, timestamps, and direct links to the comment on GitHub.
Action
Add Comment to Purchase Order
Tool to add a comment to a purchase order. Use when you need to add notes, feedback, or mention users on an existing purchase order.
Why this helps
Purchase order context can be split between GitHub discussions and Coupa, leaving approvers to search across both.
- Keep procurement updates alongside the related purchase order.
- Cut down on manual copying between tools.
- Preserve a direct connection to the GitHub discussion.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Coupa once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis to add new comments from the procurement issues repository to the Coupa purchase order identified in the comment, and to ask for review when the PO cannot be identified confidently.
- 4Pick New GitHub Issue Comment as the trigger and choose where run reports should go.
- 5Test with one real comment that names a Coupa PO and includes an update appropriate to share there.
Questions about this workflow
How does Notis know which purchase order to update?
Include the Coupa PO number in the GitHub comment. The prompt should direct Notis to stop and report when it cannot confidently identify a single PO.
Will edited comments be copied too?
This trigger fires for new comments. It does not fire when an existing comment is edited.
Can I limit this to procurement discussions?
Select the repository used for procurement issues when choosing the trigger, and describe the relevant comments in the prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Coupa. A trigger fires from one place; an action lands in another.
GitHub triggers
Coupa actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Abandon Invoice
Tool to abandon an invoice. Use when an invoice is invalid and needs to be abandoned. Invoice once abandoned cannot be reversed.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Account
Tool to create a Coupa account. Use when you need to provision a new general ledger account with a specific chart-of-accounts type and code segments.
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.
List Accounts
Tool to list accounts from Coupa. Use when you need to retrieve account IDs and codes with optional filters and pagination.
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.
Get Recent Accounts
Tool to retrieve recently accessed accounts from Coupa. Use when you need to view accounts that the user has recently interacted with.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get Account
Tool to retrieve a specific account by ID. Use when you need detailed account information including segments, type, and status.
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.
Update Account
Tool to update an existing Coupa account. Use when you need to modify account information including account type, activation status, code segments, and display name.
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.
List Account Types
Tool to list account types in Coupa. Use when you need account type IDs and names for account creation.
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.
Get Account Type
Tool to retrieve a specific account type by ID. Use when you need detailed information about a chart of accounts.
Connect any two apps with Notis in the middle.
GitHub and Coupa, 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 Coupa.