Give new release teammates build profile context
Put the basic build configuration directory within reach as someone joins the release conversation.
Trigger
New Chat Member
Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.
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
New teammates often need the same setup context, and repeated explanations consume attention during busy weeks.
- Make build setup context easier to discover for new joiners.
- Reduce repeat explanations in the release group.
- Help a teammate get oriented without a separate dashboard tour.
Setup
Build it in a few focused steps.
- 1Connect Telegram and Appcircle to Notis once through the portal.
- 2Create an automation in the portal, or ask Notis to list Appcircle build profiles when a member joins the release group.
- 3Pick Telegram New Chat Member as the trigger and choose the channel for run reports.
- 4Test by adding a test member to the Telegram group.
Questions about this workflow
Does this configure a build for the new person?
No. It provides the list of profiles so the team can orient them.
Can the prompt limit the response to relevant profiles?
You can ask Notis in plain language to focus on the profiles relevant to the release group.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Telegram to Appcircle. A trigger fires from one place; an action lands in another.
Telegram 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 Message Received
Triggered when your bot receives a new message in a private chat, group, or supergroup. To receive every message in a group, Privacy Mode must be disabled for the bot in BotFather.
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 Channel Post
Triggered when a new post is published to a channel where your bot is an administrator.
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.
Callback Query Received
Triggered when a user taps an inline keyboard button attached to one of your bot's messages.
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.
Message Edited
Triggered when a message in a chat your bot can see is edited by its sender.
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.
New Chat Member
Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.
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.
Telegram 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.