Check incoming content references against Contentful
A reference is only useful if it points to the right entry. Query Contentful when a request arrives and make the result easy to confirm.
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
Broken or mistaken content references can pass through intake unnoticed until someone tries to use them.
- Catch missing references early
- Reduce manual entry lookup during intake
- Return a simple confirmation for follow-up
Setup
Build it in a few focused steps.
- 1Connect Contentful graphql in the Notis portal.
- 2Create an automation for validating incoming content references.
- 3Tell Notis to query Contentful using the entry identifier or reference in the request and report whether it found a matching result.
- 4Pick the webhook trigger and choose a report destination.
- 5Test with one known valid reference and one unavailable reference.
Questions about this workflow
Does this modify the referenced entry?
No. It retrieves content through a GraphQL query and reports the result.
What if the request does not include an identifier?
The query may not be precise. Include a stable identifier or enough context in the request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Contentful graphql. A trigger fires from one place; an action lands in another.
Google Drive 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 Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
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.
File Created
Triggers when a new file is created in Google Drive.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
File Shared (Permissions Added)
Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Connect any two apps with Notis in the middle.
Google Drive 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.