Keep content context close to changing issues
A changed status, label, or other issue detail can alter what content matters. Notis checks Contentful and reports related entries.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
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
A meaningful issue update can go unnoticed by people who maintain related content.
- Make changes easier to connect with existing content.
- Reduce manual follow-up searches.
- Give teammates a focused review prompt.
Setup
Build it in a few focused steps.
- 1Connect Linear and Contentful graphql to Notis once in the portal.
- 2Create an automation in the portal or describe it to Notis in plain language.
- 3In one instruction, ask Notis to query Contentful for entries related to an updated issue and summarize possible implications.
- 4Select the Linear Issue Updated trigger and choose a channel for run reports.
- 5Test by updating one real issue and reviewing the report.
Questions about this workflow
Does every issue update cause a lookup?
The selected trigger is an issue update. Describe in your instruction which updates merit a Contentful lookup, based on the event details available to Notis.
Will Contentful content be changed?
No. The specified Contentful action runs a GraphQL query to fetch content.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Contentful graphql. A trigger fires from one place; an action lands in another.
Linear 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.
Comment Received Trigger
Triggered when a comment is received.
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.
Issue Created Trigger
Triggered when a new issue is created.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear 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.