Review Appcircle build profiles when a Stripe payment fails
A failed payment can point to a release issue that needs a closer look. Have Notis retrieve the available Appcircle build profiles and summarize them alongside the Stripe failure.
Trigger
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
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
Payment failures and release configuration live in separate tools, making it easy to miss the connection while investigating.
- Keep payment incident context with release configuration details
- Reduce manual switching between Stripe and Appcircle
- Give the team a concise starting point for investigation
Setup
Build it in a few focused steps.
- 1Connect Stripe and Appcircle once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3In one instruction, ask Notis to retrieve Appcircle build profiles and summarize them with the failed payment context.
- 4Pick the Stripe Payment Intent Failed trigger and choose where run reports should go.
- 5Test with one real failed payment example.
Questions about this workflow
Does this workflow change or start an Appcircle build?
No. It lists Appcircle build profiles and provides a summary for investigation.
What details are included in the report?
Notis can use details provided by the Stripe failure and the build profiles returned by Appcircle. Missing context should be supplied in your instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Appcircle. A trigger fires from one place; an action lands in another.
Stripe 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.
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
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.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
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.
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
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.
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
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.
Product Created Trigger
Triggered when a product is created in Stripe
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.
Subscription Added Trigger
Triggered when a subscription is added in Stripe
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.
Stripe 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.