Appcircle is an enterprise-grade mobile CI/CD platform that enables developers to build, test, and publish mobile applications efficiently, offering both cloud-based and self-hosted deployment options.
Appcircle is an enterprise-grade mobile CI/CD platform that enables developers to build, test, and publish mobile applications efficiently, offering both cloud-based and self-hosted deployment options. On Nagent, Appcircle is exposed as a fully-configurable developer tools integration that any agent can call — 14 actions, and API key authentication. No code is required to wire Appcircle into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Appcircle to automate the kinds of tasks developer tools teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Appcircle into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Appcircle, with input parameters and output schema. Drop these into any step of an agent built in Helix.
APPCIRCLE_BUILD_REPO_WEBHOOK_CALLBACK_STANDARDTrigger 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.
Input parameters
Complete webhook payload from the Git provider. This should be the unmodified JSON body sent by GitHub (push event), GitLab (push/merge event), Bitbucket (repo:push event), or Azure DevOps (git.push event). The payload structure varies by provider but typically includes repository details, commit information, author data, and branch references.
Git provider segment from the webhook URL. Must match the provider that will send the webhook. Valid values: 'github' for GitHub, 'gitlab' for GitLab, 'bitbucket' for Bitbucket Cloud/Server, 'azuredevops' for Azure DevOps.
Appcircle organization ID (UUID format) that identifies which organization's build profiles should be triggered. This must match the organization ID in your Appcircle webhook URL.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
APPCIRCLE_BUILD_WEBHOOK_CUSTOM_INTEGRATIONTriggers 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.
Input parameters
The complete webhook payload received from the Git provider (GitHub, GitLab, Bitbucket, or Azure DevOps). This should be the raw JSON object sent by the Git provider containing commit information, repository details, pusher data, and other event-specific fields. The payload structure varies by Git provider but typically includes fields like 'ref', 'commits', 'repository', 'pusher', and 'sender'.
The API version identifier from the webhook URL. Typically 'V' for standard webhooks or 'V7' for newer versions. This value is specified in the webhook URL provided by Appcircle.
The Git provider type for the webhook endpoint. Must be one of: 'github', 'gitlab', 'bitbucket', or 'azure-devops'. This value is part of the webhook URL provided by Appcircle when setting up custom integrations.
The custom integration ID (UUID format) for your repository connection. This ID is part of the webhook URL provided by Appcircle when configuring custom integrations for repositories connected via SSH or public URL. Example format: 'abcdef12-3456-7890-abcd-ef1234567890'
The unique Appcircle organization ID (UUID format). This ID is embedded in the webhook URL generated by Appcircle for your organization. Example format: '123e4567-e89b-12d3-a456-426614174000'
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
APPCIRCLE_DISTRIBUTION_LIST_PROFILESList 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.
Input parameters
Page number for pagination (1-indexed). Must be >= 1.
Number of items per page. Must be >= 1.
Sorting parameter for the profiles list. Example: 'name', '-createDate'
Search term to filter profiles by name.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
APPCIRCLE_GET_DISTRIBUTE_SENT_PROFILESGet 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.
Input parameters
End date for filtering profiles. Format: ISO 8601 date string (e.g., '2024-12-31T23:59:59Z').
Start date for filtering profiles. Format: ISO 8601 date string (e.g., '2024-01-01T00:00:00Z').
Organization ID to filter profiles. If not provided, uses the authenticated user's organization.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
APPCIRCLE_GET_PUBLISH_ACTIVITY_REPORTRetrieve 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.
Input parameters
Page number for pagination. Must be >= 1.
Number of items per page. Must be >= 1.
Sort order for results. Use field name with optional prefix '+' for ascending or '-' for descending.
Filter by user email address who performed the action.
Publish action type enumeration.
Filter activities up to this date. Use ISO 8601 format (e.g., '2024-12-31T23:59:59Z').
Platform type enumeration.
Filter activities starting from this date. Use ISO 8601 format (e.g., '2024-01-01T00:00:00Z').
Filter by profile name. Supports partial matching.
Filter by organization ID (UUID format).
Filter by organization name. Supports partial matching.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
APPCIRCLE_LIST_BUILD_PROFILESList 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.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
APPCIRCLE_LIST_BUNDLE_IDENTIFIERSList 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.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
APPCIRCLE_LIST_ORGANIZATIONSList 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.
Input parameters
Page number for pagination. Must be >= 1. Default is 1.
Search query string to filter organizations by name. Supports Unicode characters.
Number of items per page. Must be >= 1. Default is 200.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
APPCIRCLE_LIST_STORE_PROFILESList all Enterprise App Store profiles for the authenticated organization. Enterprise App Store profiles are used to distribute apps internally. Use this to discover available store profiles and their IDs before listing app versions or managing store content.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
APPCIRCLE_RENAME_VARIABLE_GROUPTool to rename an environment group (variable group) in Appcircle. Use when you need to update the name of an existing variable group to better reflect its purpose or environment.
Input parameters
New name for the variable group. If not provided, the group name will remain unchanged.
Unique identifier of the variable group to rename. Must be a valid UUID format.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
APPCIRCLE_STORE_IN_APP_AUTH_TOKENTool to fetch an access token for Enterprise App Store in-app updates. Use when you have the enterprise store profileId and secret and need to obtain a bearer token for subsequent update requests.
Input parameters
In-App Update Secret key for authenticating with the Enterprise Store. Obtain this from your Enterprise App Store Profile settings.
Base URL of the Enterprise App Store (e.g., https://store.mycompany.com). This is the domain where in-app update APIs are served.
Enterprise Store Profile ID in GUID/UUID format (e.g., '12345678-1234-1234-1234-123456789012'). Find this in your Enterprise App Store Profile settings under the Info tab.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
APPCIRCLE_STORE_IN_APP_DOWNLOAD_VERSION_WITH_USERTool to download a specific in-app store version and attribute the download to a user for reporting. Use when triggering an in-app update download after obtaining an access token.
Input parameters
Base URL of the Enterprise App Store (e.g., https://store.mycompany.com)
End-user email to attribute the download for reporting
App version identifier (AppVersion.Id)
In-app update access token obtained via /api/auth/token
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
APPCIRCLE_STORE_INAPP_LIST_APP_VERSIONSTool to list available app versions for the Enterprise App Store profile. Use when fetching available in-app update versions.
Input parameters
Base URL of the Enterprise App Store (e.g., https://store.mycompany.com). This is the domain where in-app update APIs are served.
Bearer access token obtained via /api/auth/token. If provided, will be set as Authorization header.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
APPCIRCLE_STORE_LIST_PROFILE_APP_VERSIONS_V2Tool to list app versions under a given store profile. Use when you need to fetch all versions for a specific Enterprise App Store profile after obtaining its ID.
Input parameters
Optional Accept header override (default application/json).
Enterprise App Store profile ID in UUID format. Find this in your Enterprise App Store Profile settings under the Info tab, or extract it from the profile URL.
Optional Authorization header value to use for the request.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 99 agents privately built on Nagent that already use Appcircle.
Build on Nagent
Connect Appcircle to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Appcircle, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Appcircle is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Appcircle is connected, you configure its 14 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Appcircle steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Appcircle event fires, the agent kicks off automatically.
Every Appcircle action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Appcircle ships with 14 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Appcircle together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Appcircle-based workflows tailored to your business.