Get a Contentful space reference for each deployment
When a GitHub deployment is created, receive a current list of accessible Contentful spaces alongside the run report.
Trigger
New Deployment Created
Triggers when a new deployment is created in a GitHub repository. Fires an event for each newly created deployment detected in the configured repository. Deployments can optionally be filtered by target environment. The payload includes the deployment ID, commit SHA, ref, task, environment, creator details, and timestamps.
Action
List spaces
Lists all spaces that the authenticated user has access to in contentful. this is a fundamental operation needed before performing any other content management actions since most operations require a space id.
Why this helps
Deployment work can involve switching between repository activity and Contentful just to check which spaces are available.
- See accessible Contentful spaces when a deployment is created
- Keep the deployment event and space reference in one report
- Avoid a separate Contentful lookup for a basic access check
Setup
Build it in a few focused steps.
- 1Connect GitHub and Contentful once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, ask Notis to list accessible Contentful spaces when a new GitHub deployment is created and include the results in its run report.
- 4Pick the new deployment created trigger and choose where run reports go.
- 5Test with one real deployment event and review the report.
Questions about this workflow
Does this publish Contentful content?
No. The available action lists Contentful spaces; it does not publish entries or assets.
Does the trigger run for a deployment status change?
No. This workflow uses the GitHub event for a newly created deployment.
What does the report show?
It includes the spaces returned by Contentful for the authenticated account, alongside the automation run context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Contentful. A trigger fires from one place; an action lands in another.
GitHub triggers
Contentful actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get space
Retrieves details of a specific space by its id. this action is used to get information about a single space in contentful.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List spaces
Lists all spaces that the authenticated user has access to in contentful. this is a fundamental operation needed before performing any other content management actions since most operations require a space id.
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Update space
Updates the name of a specific space. notes: - the version number is required to ensure you're updating the latest version of the space. - you can get the current version from the sys.version field when fetching space details. - only the name of the space can be updated.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Connect any two apps with Notis in the middle.
GitHub and Contentful, 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.