Refresh build profile context as mobile issues change
Keep investigation context current as a mobile issue moves forward. Notis fetches Appcircle build profiles after an issue update and summarizes the results.
Trigger
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Action
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.
Why this helps
Teams lose time repeating build configuration lookups as mobile issues change status, assignee, or other details.
- Refresh the available build profile list after a relevant issue change.
- Keep investigation context close to the issue workflow.
- Share a consistent summary through run reports.
Setup
Build it in a few focused steps.
- 1Connect Jira and Appcircle once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to retrieve Appcircle build profiles when a mobile investigation issue changes and summarize the results in the run report.
- 4Pick the Jira Updated Issue trigger and choose where run reports go.
- 5Test with one real issue update that includes the mobile app context.
Questions about this workflow
Can this rerun a build when an issue is updated?
No. It retrieves build profile information. The available build callback actions expect Git provider webhook payloads, which a Jira issue update does not provide.
Can it compare profile details over time?
The listed action returns available build profiles. A historical baseline is not provided by that action, so supply a previous snapshot if you need a comparison.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Appcircle. A trigger fires from one place; an action lands in another.
Jira 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.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
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.
New Project
Triggered when a new project is added in Jira
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.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
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.
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.
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.
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.
Jira 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.