Check how Agility CMS content looks on the live site
Bring an Agility CMS item and its rendered page into one review flow, so you can spot content issues without jumping between tools.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get Webpage Content
Retrieve the rendered content of a webpage.
Why this helps
CMS edits can look correct in the editor but render differently on the site, leaving founders to remember a separate manual check.
- Review rendered content soon after an HTTP request starts the workflow.
- Keep the CMS item and its browser view together for easier inspection.
- Reduce the chance of publishing an unnoticed layout or content issue.
Setup
Build it in a few focused steps.
- 1Connect Agility CMS and Anchor Browser once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Tell Notis to fetch the requested Agility CMS item and retrieve its rendered page in Anchor Browser for review.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real item and webhook request.
Questions about this workflow
What starts this workflow?
A Notis webhook starts it when it receives an HTTP request. Agility CMS does not provide trigger events here.
Does this workflow publish or change the CMS item?
No. It fetches the item and retrieves webpage content for review; it does not publish or edit content.
What information must the webhook provide?
Include enough context in your request for Notis to identify the Agility CMS item and the page to inspect.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Agility cms to Anchor browser. A trigger fires from one place; an action lands in another.
Agility cms triggers
Anchor browser actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Profile
Create a browser profile from an active session to preserve its data.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Click Mouse
Click at specified coordinates in a browser session.
Delete Profile
Delete a browser profile.
Copy Selected Text
Copy the currently selected text in a browser session to the clipboard.
End All Sessions
End all active browser sessions.
Create Integration
Create an integration that is immediately available in browser sessions and profiles.
End Browser Session
End a specific browser session.
Create or Update Task Draft
Create or update a task’s draft version for development and testing.
Connect any two apps with Notis in the middle.
Agility cms and Anchor browser, 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 Anchor browser.