Start a custom Appcircle build from a new Coda build page
Give a documented build request a direct path into your custom Appcircle integration.
Trigger
New Coda Page Trigger
Triggers when a new page is added to a Coda document.
Action
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.
Why this helps
Custom build pipelines often depend on a manual webhook handoff after planning is complete.
- Speeds custom pipeline starts
- Keeps the handoff explicit
- Reduces missed webhook steps
Setup
Build it in a few focused steps.
- 1Connect Coda and Appcircle once in Notis.
- 2Create an automation that forwards the approved Git provider payload from a new build page to the Appcircle custom integration webhook.
- 3Pick the New Coda Page trigger.
- 4Choose the run report destination.
- 5Test with one real build page and a safe payload.
Questions about this workflow
What makes this custom?
It uses Appcircle's custom integration webhook endpoint instead of the standard repository webhook action.
Can Notis validate the payload first?
Yes. Instruct Notis to check that required information is present before forwarding it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Coda to Appcircle. A trigger fires from one place; an action lands in another.
Coda 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.
Coda Document Deleted Trigger
Triggers when a Coda document is deleted.
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 Coda Document Trigger
Triggers when a new Coda document is created.
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.
New Coda Page Trigger
Triggers when a new page is added to a Coda document.
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.
Specific Coda Page Updated Trigger
Triggers when a specific page within a Coda document is updated.
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.
Coda 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.