Fetch test details when the QA page changes
Update the QA page and receive the test evidence needed for the next decision.
Trigger
Specific Coda Page Updated Trigger
Triggers when a specific page within a Coda document is updated.
Action
Get Test Metadata
Tool to fetch test metadata for a specific job. use when you need detailed test results, run times, and failure messages after a job completes.
Why this helps
QA notes and test results drift apart, making failures harder to interpret quickly.
- Bring test evidence into the review loop
- Reduce result hunting
- Support faster go or no go decisions
Setup
Build it in a few focused steps.
- 1Connect Coda and CircleCI in Notis once.
- 2Create an automation named QA Page Test Evidence.
- 3Tell Notis to retrieve CircleCI test metadata for the relevant job when the specific QA page is updated.
- 4Pick the specific Coda page updated trigger and choose the report destination.
- 5Test with one QA page update.
Questions about this workflow
What if the job number is missing?
The instruction must name where Notis can obtain the job number, or the workflow should report that it is missing.
Does this rerun tests?
No. It retrieves metadata from an existing CircleCI job.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Coda to Circleci. A trigger fires from one place; an action lands in another.
Coda triggers
Circleci actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Job Artifacts
Tool to retrieve artifacts produced by a specific job. use after a job has completed to list its output files.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Job Details
Tool to fetch details of a specific job within a project. use when you need status, timing, and executor information for a circleci job by its number.
Coda Document Deleted Trigger
Triggers when a Coda document is deleted.
Get Pipeline Config
Tool to fetch pipeline configuration by id. use when you need the source or compiled yaml of a specific pipeline.
New Coda Document Trigger
Triggers when a new Coda document is created.
Get Test Metadata
Tool to fetch test metadata for a specific job. use when you need detailed test results, run times, and failure messages after a job completes.
New Coda Page Trigger
Triggers when a new page is added to a Coda document.
Get User Information
Tool to retrieve information about a circleci user by their unique id. use when you need user profile details after obtaining the user id.
Specific Coda Page Updated Trigger
Triggers when a specific page within a Coda document is updated.
List Pipelines for Project
Tool to list all pipelines for a specific project. use when you need to retrieve the pipelines for a project (e.g., to display recent runs on a dashboard).
List Self-Hosted Runners
Tool to list available self-hosted runners. use when you need to retrieve all configured self-hosted runners for your organization.
List Workflows by Pipeline ID
Tool to list all workflows associated with a specific pipeline. use when you need to fetch or paginate through workflows by pipeline id.
Connect any two apps with Notis in the middle.
Coda 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.