Keep Jira procurement requests with their Coupa purchase orders
Capture the reason for a purchase in Coupa as soon as its Jira request is created.
Trigger
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
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
Procurement context gets split between Jira tickets and Coupa purchase orders, leaving buyers to chase details across tools.
- Keep request context beside the purchase order
- Reduce manual copying between Jira and Coupa
- Make buyer follow-up easier
Setup
Build it in a few focused steps.
- 1Connect Jira and Coupa once in the Notis portal.
- 2Create an automation and give it a clear name.
- 3In one instruction, ask Notis to summarize new procurement issues and add the note to the matching Coupa purchase order, using an identifier present in the issue.
- 4Pick Jira New Issue as the trigger and choose where run reports should go.
- 5Test with one real issue that identifies an existing Coupa purchase order.
Questions about this workflow
How does Notis find the purchase order?
The Jira issue must include an identifier that Notis can use to find the corresponding Coupa purchase order. Include that requirement in the instruction.
Will this create a purchase order?
No. This workflow adds a comment to an existing purchase order.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Coupa. A trigger fires from one place; an action lands in another.
Jira 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 Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
List Accounts
Tool to list accounts from Coupa. Use when you need to retrieve account IDs and codes with optional filters and pagination.
New Project
Triggered when a new project is added in Jira
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.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Get Account
Tool to retrieve a specific account by ID. Use when you need detailed account information including segments, type, and status.
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.
List Account Types
Tool to list account types in Coupa. Use when you need account type IDs and names for account creation.
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.
Jira 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.