When a new SaaS sub-account (Location) is created, there should be an Agency-level workflow trigger that exposes full metadata and allows execution within a designated Agency sub-account.

Required capabilities:

• Trigger fires on: New Sub-Account Created

• Outputs include:

• location.id

• location.name

• company.id

• snapshot.id

• plan.name

• user.email

• billing.subscription_id (if applicable)

Critical requirement:

The workflow must allow execution inside a specified Agency sub-account (e.g., the main SaaS control account), so we can:

• Automatically create/update a contact inside the Agency sub-account

• Stamp the new location.id into a custom field

• Maintain centralized cross-location tracking

• Sync external databases or analytics systems

Use Case:

SaaS operators managing many sub-accounts need centralized control, attribution, and scalable onboarding automation without manual copying of Location IDs.

This would significantly improve SaaS scalability and reduce operational friction for agencies.