Skip to content
Notis

Verify the deployment request before the build starts

Let Notis check the contact details in a deployment request, then start the pipeline only when your instruction says to proceed.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

Action

Trigger Pipeline

Starts a new CI/CD pipeline run for a project.

Why this helps

Teams can lose time chasing unclear deployment requests or starting builds before confirming who submitted them.

  • Add a contact verification step to a request-driven build.
  • Cut down on follow-up for deployment requests.
  • Keep pipeline starts connected to an explicit decision.

Setup

Build it in a few focused steps.

  • 1Connect Abstract and CircleCI once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and name it for deployment requests.
  • 3Tell Notis to verify the submitted phone number with Abstract and trigger the pipeline only when your stated criteria are met.
  • 4Choose the webhook trigger and pick a channel for run reports.
  • 5Test with one real deployment request and a phone number you can verify.

Questions about this workflow

What information should the webhook request include?

Include the deployment request and the phone number to verify. Avoid relying on details that are not supplied in the request.

Can the automation decide which requests qualify?

Yes. State the criteria in the instruction. Abstract can verify a phone number, but your prompt must define when a verified request should start a pipeline.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Abstract to Circleci. A trigger fires from one place; an action lands in another.

Abstract triggers

Circleci actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Get Job Artifacts

Retrieves files produced by a job.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Create Context

ActionInstant

Get Job Details

Retrieves status, timing, and executor details for a job.

ActionInstant

Create Context (GraphQL)

ActionInstant

Get Pipeline Config

Retrieves the source or compiled configuration for a pipeline.

ActionInstant

Create Context Restriction

ActionInstant

Get Test Metadata

Retrieves test results, run times, and failure details for a job.

ActionInstant

Create Organization Orb Allowlist

ActionInstant

Connect any two apps with Notis in the middle.

Abstract 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.