Codex
Claude
GeminiWhat you do
- Choose one program scope, audience boundary, and review-only or apply mode.
- Review campaign, draft-email, segment, and consent changes separately.
- Approve ordinary program mutations and legal consent changes through distinct gates.
Marketing operations teams managing HubSpot campaign programs / gtm
GTM Marketing Program Lifecycle
A reviewed marketing-program plan with narrowly approved HubSpot changes, consent decisions isolated behind their own gate, and provider-safe execution evidence.
From request to resultA complete plan you can follow.
Visible planThe problem
Marketing program setup becomes unsafe when audience membership, campaign metadata, draft assets, consent state, and delivery are changed as one opaque operation.
AI can reconcile program context and prepare bounded changes while StackOS keeps provider execution, approvals, idempotency, and evidence explicit.
What the agent does
- Inspect only the HubSpot state needed for the bounded program.
- Prepare safe-ref changes and isolate conflicts, missing consent, and unavailable capabilities.
- Execute only approved actions with stable mutation keys and reconcile provider-safe evidence.
When this workflow helps
A reusable method, adapted to the request.
- A HubSpot marketing program needs coordinated audience, campaign, draft-email, or consent review and approved updates.
Before it starts
Connection required
- A HubSpot OAuth connection with the Marketing capability bundle
- A bounded program scope and safe campaign, email, segment, contact, and subscription refs where applicable
- Audience policy, legal-basis policy, and separate approval authority for consent changes
What proves it worked
Evidence, not a success claim.
- Current-state evidence and safe refs
- Reviewed program and consent change sets
- Action-call refs, provider request ids, partial failures, and retry guidance
Workflow path
The reusable stages of the work.
A real run expands these stages around the request, context, selected tools, approvals, and dependencies.
- 01Passes to next stage
Bound Marketing Program
Read the goal, bounded scope, execution mode, durable context, and prior learnings.
- 02Passes to next stage
Inspect Current Program State
Read only the campaigns, draft emails, segments, subscription definitions, and selected contact preferences needed by the plan.
- 03Passes to next stage
Prepare Reviewed Change Sets
Produce atomic program and consent change sets, expected effects, idempotency inputs, and explicit skips.
- 04Passes to next stage
Apply Approved Program Changes
Optionally create or update campaign and draft-email assets and change bounded segment membership.
- 05Passes to next stage
Apply Separately Approved Consent Changes
Optionally apply explicit contact preference changes after independent legal and evidence review.
- 06Verified outcome
Reconcile Program Evidence
Store the durable program index and final status without claiming publication, bulk delivery, or unobserved outcomes.
Safe stopping and recovery
Useful even when the whole path cannot run.
- Stop after the reviewed plan when writes are not authorized.
- Stop before consent mutation when legal basis or affirmative consent evidence is incomplete.
- If a safe ref, scope, or consent fact is missing, keep the program in review-only state.
- After a partial provider result, inspect the existing action-call evidence and retry only unresolved mutations with the same keys.
Specialists inside this workflow
Clear roles for each part of the job.
Connected work