Check localized Contentful entries on demand
Request a quick lookup of locale variants when localization work needs a little context from Contentful.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Finding whether localized versions exist can take repeated searching through entries and locale-specific views.
- Retrieve locale data for relevant entries.
- Highlight missing or unexpected variants for human review.
- Start the check from a request carrying entry context.
Setup
Build it in a few focused steps.
- 1Connect Contentful graphql once in the Notis portal.
- 2Create an automation for on-demand localization checks.
- 3Tell Notis to query the relevant entries and summarize the locale data returned, noting gaps against locales named in the request.
- 4Pick the Notis webhook trigger and choose where run reports go.
- 5Test with one real request that names an entry and expected locales.
Questions about this workflow
Can it infer which locales are required?
Only if the request or automation instruction supplies the expected locales. The query returns data and does not provide your localization policy.
Will it create translations?
No. This workflow checks returned locale data and reports findings.
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.