Test builds ready when reviewers are
Code moves to review? Appcircle immediately starts building it. Reviewers don't wait for builds, testers have fresh candidates, everyone stays unblocked.
Trigger
Public Team Issue Properties Updated
Fires when properties on a *public-team* Linear issue change (status, assignee, priority, labels, etc.). For private teams (lock icon in Linear's sidebar) use `LINEAR_PRIVATE_TEAM_ISSUE_PROPERTIES_UPDATED`.
Action
Standard Repo Webhook Callback
Trigger Appcircle builds via Git provider webhook callbacks. This action forwards webhook payloads from GitHub, GitLab, Bitbucket, or Azure DevOps to Appcircle's build webhook endpoint to automatically trigger builds when code is pushed. Use this action when: - Simulating or testing webhook-triggered builds - Programmatically triggering builds using webhook payloads - Integrating custom CI/CD workflows that need to trigger Appcircle builds - Replaying or debugging webhook events Requirements: - The organization must exist and have webhook integration configured in Appcircle - Build profiles must be set up with repository connections - The webhook URL pattern is: https://api.appcircle.io/build/v1/callback/hooks/{provider}/{org_id}/V7 Note: The action returns the raw HTTP response including status code and response body, allowing you to handle success, validation errors, or authentication issues appropriately.
Why this helps
Code goes to review, but the test build doesn't start until someone remembers to trigger it. Reviewers sit idle. Testers wait. That gap grows missed context.
- Test builds ready the moment code enters review
- Reviewers and testers always have fresh candidates
- Reduce wait time between code and testing
- Nobody has to remember the manual trigger step
Setup
Build it in a few focused steps.
- 1Connect Linear and Appcircle to Notis.
- 2Tell Notis: 'When an issue status changes to In Review, trigger a test build in Appcircle.'
- 3Choose where build status gets reported.
- 4Select 'Issue Updated' as your trigger.
- 5Move a test issue to 'In Review' and verify the build starts immediately.
Questions about this workflow
Should I use In Review or In QA?
Either works. Tell Notis whichever status comes first in your workflow. You can also create separate automations for both if they build different targets.
Does this replace my normal CI/CD on git push?
No, they complement each other. This triggers on workflow status, so you can get builds even without pushing code, or re-trigger existing code.
Can I trigger different builds for different issue types?
Yes. Set separate automations for different issue labels or projects if some need staging builds and others need production builds.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Appcircle. A trigger fires from one place; an action lands in another.
Linear triggers
Appcircle actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Standard Repo Webhook Callback
Trigger Appcircle builds via Git provider webhook callbacks. This action forwards webhook payloads from GitHub, GitLab, Bitbucket, or Azure DevOps to Appcircle's build webhook endpoint to automatically trigger builds when code is pushed. Use this action when: - Simulating or testing webhook-triggered builds - Programmatically triggering builds using webhook payloads - Integrating custom CI/CD workflows that need to trigger Appcircle builds - Replaying or debugging webhook events Requirements: - The organization must exist and have webhook integration configured in Appcircle - Build profiles must be set up with repository connections - The webhook URL pattern is: https://api.appcircle.io/build/v1/callback/hooks/{provider}/{org_id}/V7 Note: The action returns the raw HTTP response including status code and response body, allowing you to handle success, validation errors, or authentication issues appropriately.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Custom Integration Webhook Callback
Triggers Appcircle builds via custom integration webhook endpoint by forwarding Git provider webhook payloads. This action is designed to receive and forward webhook payloads from Git providers (GitHub, GitLab, Bitbucket, Azure DevOps) to Appcircle's build system. The webhook URL format and parameters (organization_id, integration_id, version) are provided by Appcircle when you configure custom integrations for repositories connected via SSH or public URL in the build profile settings. Use this action when: - You need to programmatically trigger Appcircle builds from Git provider webhook events - Testing webhook integrations with different payload structures - Implementing custom CI/CD workflows that forward webhook events to Appcircle Note: The organization_id and integration_id values must correspond to actual configurations in Appcircle. Test payloads will typically return 400/404 errors indicating no valid configuration exists for the provided IDs.
Comment Received Trigger
Triggered when a comment is received.
List Distribution Profiles
List all distribution profiles for the authenticated organization. Distribution profiles are used to manage and distribute app builds to testers. This endpoint supports pagination, sorting, and filtering by profile name. Use this when you need to retrieve available distribution profiles.
Issue Created Trigger
Triggered when a new issue is created.
Get Distribution Sent Profiles
Get distinct profile names for App Sharing Report filter. Returns a list of unique profile names that can be used to filter app sharing reports within the specified date range and organization. Use this to discover available profile names before querying detailed sharing reports.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Get Publish Activity Report
Retrieve the publish activity report for your organization. Returns paginated list of publish activities with filtering options by date range, platform, action type, and organization. Use this to monitor and audit publish operations across profiles.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
List Build Profiles
List all build profiles for the authenticated organization. Build profiles define the configuration for building mobile applications. Use this to discover available build profiles and their IDs before triggering builds or configuring webhooks.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
List Bundle Identifiers
List all bundle identifiers in Appcircle. Returns all bundle identifiers configured in your organization, including their platforms, capabilities, and associated credentials. Use this to discover available bundle identifiers before managing signing identities or app configurations.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
List Organizations
List organizations accessible to the authenticated user. Returns a paginated list of organizations with their details including ID, name, logo URL, and SSO status. Supports search filtering and pagination controls. Use this to discover available organizations before performing organization-specific operations like managing builds, distributions, or webhooks.
Connect any two apps with Notis in the middle.
Linear and Appcircle, 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 Appcircle.