Keep pipeline configuration in view during release reviews
Get the pipeline configuration on a regular schedule so your release process review starts with the current build setup.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Pipeline Config
Retrieves the source or compiled configuration for a pipeline.
Why this helps
Release instructions can drift from pipeline setup, and checking the configuration often gets postponed until a change causes confusion.
- Retrieve the configuration for the specified pipeline on a recurring schedule.
- Give release process reviews a current configuration reference.
- Surface differences for a person to review before updating documentation or build settings.
Setup
Build it in a few focused steps.
- 1Connect ActiveMerge and CircleCI once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Describe which pipeline configuration to retrieve and how the report should support review of the related release documentation.
- 4Choose a recurring Notis schedule as the trigger.
- 5Choose a report channel, then test with one real pipeline and confirm the retrieved configuration is the one you intended.
Questions about this workflow
Will this automatically update the ActiveMerge documents?
No. The available CircleCI action retrieves pipeline configuration. A person can review the report and update documentation as needed.
What does the configuration response contain?
The action fetches the source or compiled YAML for a specific pipeline. The automation needs enough information to identify that pipeline.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link ActiveMerge to Circleci. A trigger fires from one place; an action lands in another.
ActiveMerge triggers
Circleci actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Job Artifacts
Retrieves files produced by a job.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Context
Creates a context for sharing environment variables securely across projects.
Get Job Details
Retrieves status, timing, and executor details for a job.
Create Context (GraphQL)
Creates a context for storing environment variables; returns an error if creation fails.
Get Pipeline Config
Retrieves the source or compiled configuration for a pipeline.
Create Context Restriction
Creates a context restriction to limit access by project, rules, or group.
Get Test Metadata
Retrieves test results, run times, and failure details for a job.
Create Organization Orb Allowlist
Allows URL-based orb references with matching prefixes in an organization’s pipelines.
Connect any two apps with Notis in the middle.
ActiveMerge and Circleci, 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 Circleci.