ceven

Appcircle

Triggers mobile app builds, manages distribution groups, and monitors CI CD pipeline health from your chat interface to accelerate release cycles.

Try Appcircle in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Appcircle integration

    • Describe the outcome and Ceven picks the right Appcircle calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Appcircle data, across all 14 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Appcircle access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Appcircle, when, and on whose behalf.
    • The agent pauses and asks when Appcircle is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Appcircle.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Appcircle action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Appcircle, and when to use it.

Start build
Use this to trigger a new build for a specific app and workflow profile. Specify the branch or commit hash to start the process.
Get build status
Pull the current state of a build to see if it is queuing, running, succeeded, or failed.
List builds
Pull a history of recent builds for a project, filtered by status or branch to audit release frequency.
Get build logs
Pull the raw console output for a failed build to identify the exact line where the compiler or test suite failed.
Create distribution group
Set up a new group of testers for a specific app version. Use this to separate alpha and beta testers.
Add user to group
Add a developer or tester to a distribution group via email to grant them access to a build binary.
Remove user from group
Revoke access for a user from a distribution group to secure a pre release build.
List distribution groups
Pull all existing tester groups for a project to manage access levels.
Update build profile
Modify the configuration or environment variables for a specific build workflow.
Get app details
Pull the general configuration and metadata for a mobile application project.
Search apps
Query for apps by name or bundle ID to find the correct project ID for a workflow.
Cancel build
Stop a running build immediately to save build minutes or stop a faulty deployment.

12 actions · scroll to see them all

Frequently asked questions

When a build fails in Appcircle, the agent can be configured to detect the failure event immediately. It pulls the build logs and uses the model to summarize the error, distinguishing between a code syntax error, a dependency failure, or a provisioning profile issue. The agent then posts this summary to your chosen communication channel and can even suggest a fix based on the log output. This prevents the team from having to dig through thousands of lines of raw console output to find a single missing semicolon or an expired certificate, turning a manual debugging process into an automated alert system.
Ceven can trigger workflows that rely on existing provisioning profiles and certificates stored within Appcircle. While the agent does not generate the Apple certificates itself, it can verify if the current profile is active and trigger a new build once you have updated the credentials in the Appcircle dashboard. If a build fails specifically due to a signing error, the agent will flag the exact certificate that is missing or expired so you can replace it quickly. This ensures that the pipeline remains fluid without the agent needing direct access to your Apple Developer account secrets.
Appcircle enforces rate limits on its API to ensure platform stability. If a Ceven workflow attempts to poll for build status too frequently, you may encounter a 429 Too Many Requests error. To mitigate this, Ceven uses an exponential backoff strategy for polling and prefers webhook events where available. Users on lower tier plans may notice this more often during high activity periods. We recommend grouping multiple status checks into a single summary request rather than having multiple agents poll the same build ID every few seconds to avoid hitting these limits.
Yes. Once a build reaches a successful state in Appcircle, Ceven can automatically trigger the distribution process. The agent can assign the build to a specific distribution group, such as your QA team or external stakeholders. It can also send a notification to those users via email or Slack with the download link. This removes the manual step of marking a build as ready for testing, ensuring that your testers get the latest version the moment it is available, which significantly reduces the feedback loop for mobile feature development.
Ceven provides full support for both platforms. The agent can distinguish between an iOS workflow and an Android workflow by referencing the project ID and the specific build profile. You can create a single workflow that triggers both a.ipa and an.apk build simultaneously and then tracks their progress in parallel. This is particularly useful for cross platform teams using frameworks like Flutter or React Native who need to ensure that a single commit works across both operating systems before proceeding to the testing phase.
The agent can read and update environment variables within your Appcircle build profiles. This allows you to change API endpoints or feature flags for a build without leaving your chat interface. For example, you can tell the agent to switch the build to use the staging database instead of the production database. The agent updates the variable in the Appcircle profile and then triggers a new build to apply the changes, ensuring that the environment is consistent across all binaries distributed to your testing groups.
Ceven can be used to manage your build history by identifying and deleting old or unsuccessful builds. You can set up a recurring workflow that searches for builds older than thirty days that were not marked as a release and deletes them to keep your workspace clean. This is a helpful way to maintain a tidy project environment and make it easier for developers to find the relevant successful builds without scrolling through hundreds of failed attempts from early development stages.
Yes. Because Ceven acts as a bridge, you can trigger Appcircle builds based on events from other tools. For example, when a specific label is added to a GitHub issue or a Jira ticket is moved to the Done column, Ceven can call the Appcircle API to start a build. This allows you to create a highly customized CI CD trigger system that goes beyond the standard git hook, enabling business logic to dictate when a mobile binary should actually be produced and distributed.

Alternatives to Appcircle

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Bitrise logoBitriseCodemagic logoCodemagicCircleCI logoCircleCIGitHub Actions logoGitHub Actions

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Appcircle and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free