Keep campaign ideas grounded in available page modules
Review the modules your team can use and connect their capabilities to the themes emerging from competitor ad research.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Page Modules
Retrieves the available page module definitions.
Why this helps
Promising campaign ideas can create planning churn when teams discover late that the needed page modules are not available.
- Keep module options visible during campaign planning
- Relate available page structures to current themes
- Reduce late discovery of implementation constraints
Setup
Build it in a few focused steps.
- 1Connect Adyntel and Agility CMS once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for module campaign fit review.
- 3Tell Notis to retrieve all Agility CMS page modules and summarize which ones may support the current Adyntel campaign themes.
- 4Pick a recurring schedule as the trigger and choose where run reports should go.
- 5Test with one real campaign theme set and review the module summary.
Questions about this workflow
How does this differ from retrieving content models?
Get Page Modules retrieves module definitions only, while Get Content Models retrieves content models and page modules.
Will it build pages using these modules?
No. The listed action retrieves module definitions and does not build or publish pages.
Can the workflow determine campaign fit from module names alone?
Ask it to distinguish direct evidence from assumptions, and provide any extra module documentation it should use.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Adyntel to Agility cms. A trigger fires from one place; an action lands in another.
Adyntel triggers
Agility cms actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get API Types
Retrieve the available enum values used across the content management API.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Content Item
Retrieves details about a content item.
Get Content List
Retrieves a paginated list of content items.
Get Content Models
Retrieves content models and page modules.
Get Logs
Retrieves content change logs for initial or incremental synchronization.
Get Page
Retrieves a page’s details, content zones, and components.
Get Page Modules
Retrieves the available page module definitions.
Get Sitemap Flat
Retrieves the flat sitemap for a channel and locale.
Connect any two apps with Notis in the middle.
Adyntel and Agility cms, 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 Agility cms.