Connect changing support issues to existing guidance
Retrieve related Contentful support entries when a Jira issue changes, so useful context is close at hand for follow-up.
Trigger
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.
Action
GraphQL Content API Query
Tool to execute a GraphQL query against a specified space and environment. Use when fetching Contentful content via GraphQL after obtaining or providing a valid token.
Why this helps
Issue updates can prompt follow-up, but locating the guidance already available in Contentful takes extra searching.
- Bring related guidance into issue follow-up.
- Summarize entries using the latest issue details.
- Help teams notice when guidance may deserve review.
Setup
Build it in a few focused steps.
- 1Connect Jira and Contentful graphql once in the Notis portal.
- 2Create an automation for support guidance lookup.
- 3Tell Notis to search Contentful using changed issue details and report related guidance entries.
- 4Pick the Jira Updated Issue trigger and choose where run reports go.
- 5Test with one real updated support issue and review matches.
Questions about this workflow
Can it update guidance based on the issue?
No. It can query and summarize entries, but the available action does not edit Contentful.
Does the trigger include comments?
No. The Updated Issue event explicitly excludes comment activity.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Contentful graphql. A trigger fires from one place; an action lands in another.
Jira triggers
Contentful graphql actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get CMA Token
Tool to retrieve a Contentful Management API (CMA) access token. Use when making CMA calls to ensure valid authorization.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
GraphQL Content API Persisted Query
Tool to execute a persisted GraphQL query via its SHA256 hash. Use after registering a query hash to run cached queries by hash. On first call include full query text; thereafter invoke with only hash and variables.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
GraphQL Content API Query
Tool to execute a GraphQL query against a specified space and environment. Use when fetching Contentful content via GraphQL after obtaining or providing a valid token.
New Project
Triggered when a new project is added in Jira
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.
Connect any two apps with Notis in the middle.
Jira and Contentful graphql, 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 Contentful graphql.