Check app platform configuration from the campaign request
Get the relevant app identifiers and platforms into the launch conversation before release planning goes further.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
List Bundle Identifiers
Lists configured bundle identifiers, platforms, capabilities, and credentials.
Why this helps
A campaign owner may not know which platform configuration applies, leading to extra questions and avoidable delay in release coordination.
- Surface configured platforms during launch handoff.
- Give release owners identifier context sooner.
- Reduce back and forth about which app configuration applies.
Setup
Build it in a few focused steps.
- 1Connect Adtraction and Appcircle once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3In one instruction, ask Notis to list Appcircle bundle identifiers and platform details relevant to the campaign launch request.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real launch request and confirm the details help the receiving owner.
Questions about this workflow
Does this validate platform readiness?
No. It reports configured bundle identifiers and platform details. It does not validate a release build.
Can the action reveal credentials?
The action description includes associated credentials as part of the returned configuration. Keep report destinations appropriate for that information.
Does the webhook come from an Adtraction event?
No. Adtraction exposes no trigger events here, so a Notis webhook starts the run.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Adtraction to Appcircle. A trigger fires from one place; an action lands in another.
Adtraction triggers
Appcircle actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Standard Repo Webhook Callback
Forwards a Git provider webhook to trigger a build.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Custom Integration Webhook Callback
Forwards a Git provider webhook to trigger a build from a custom integration.
List Distribution Profiles
Lists distribution profiles used to share app builds with testers.
Get Distribution Sent Profiles
Lists profile names available as filters for app sharing reports.
Get Publish Activity Report
Retrieves a paginated report of publishing activity for an organization.
List Build Profiles
Lists build profiles configured for an organization.
List Bundle Identifiers
Lists configured bundle identifiers, platforms, capabilities, and credentials.
List Organizations
Lists organizations the signed-in user can access.
Connect any two apps with Notis in the middle.
Adtraction 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.