Example solution design · AI-assisted solution design

Campaign operations on Asana

How to run the group's ad operations on Asana: target process, architecture, agents, configuration, data flow and build plan, each element traced to a requirement and checked against Asana's documentation.

ClientMedia Agency X

FunctionAd operations

PlatformAsana Enterprise

Process mapCampaign delivery

Sources checked18 October 2026

Prepared byCompany A

01Captured use case

From the guided interview and uploaded flow 14 requirements · 6 connected tools · 5-stage flow

Overview

A media agency group runs paid media campaigns for brand clients across search, social, display and video, in several markets. Each campaign passes through five teams and six systems.

The group wants one platform for campaign operations: structured briefs, standard workflows, auditable approvals and live status for clients, leaders and finance.

Success measures

Brief-to-kickoff cycle time
Hours spent compiling status
Approval disputes
Over- and under-allocated staff

Key characteristics

Scale: 1,000+ users in five teams, across several markets
Teams: Client service, planning, buying, trafficking, creative studio
Client reports: Daily pacing and weekly campaign reports, built from media platforms and signed off before release
Leadership: Weekly status across clients and markets; read only
Finance: Delivered-versus-booked status per campaign for client billing and month-end close
Systems: Slack and Teams for collaboration; HubSpot and Salesforce for clients and deals; ADvendio for orders; Mediaocean for plans, buys and billing
Policy: Group single sign-on, automatic provisioning, SIEM logging, data held in a set region
Out of scope: Media buying itself, which stays in Mediaocean; pacing and performance data, which stay in media platforms

Process and pain points

Brief

Client service captures objectives, budget, channels, markets and dates.

PainBriefs arrive incomplete. Planners chase details.

Plan

Planners build the media plan and staff the campaign. The client approves.

PainEach campaign type starts from scratch. Staffing relies on instinct.

Buy and traffic

Buyers book media in Mediaocean. Traffickers set up placements and creative.

PainHandoffs between teams are manual.

Review

Creative and client teams review assets before launch.

PainFeedback sits in email and chat. Sign-offs leave no trail.

Report and close

Pacing and campaign reports go to the client. Finance bills delivered media and closes the month.

PainNo cross-campaign view. Status is compiled by hand.

Every stageGroup policy governs sign-in, provisioning, audit and data location.

Design question

How should Asana be set up and connected to run this from brief to month-end close, and what does it take to build?

02Design summary

What is the design?

One Asana project per campaign, kept standard by templates and a bundle.A form takes the brief, rules hand work between teams, five approval gates record sign-off and portfolios replace hand-compiled status.

What do the agents do?

Read briefs, draft OKRs, status and variance notes, and triage sync failures.Each output stays a draft until a named person approves or posts it. No agent writes to Mediaocean or billing.

What connects, and how?

Four Asana apps and one integration layer, under three data contracts.Mediaocean keeps plans, bookings and billing. Asana reads milestones, delivery and billing status from it and never writes back.

Which plan?

Enterprise with Compliance Management and AI Teammates.Capacity planning, the bundle, single sign-on and SCIM start on Enterprise. Compliance Management feeds the audit log to the SIEM.

What does it take?

12 weeks in seven phases, with a one-market pilot.83–98 consultant days, 18–21 of them for the agents. Answers to Q4 and Q5 settle the integration ranges.

CoverageAll 14 requirements trace to a component in section 05 or 07. Video proofing is partial and UK data location is open; section 10 holds both questions. Campaign OKRs are added to make the success of each campaign measurable.

03Target process

Matched to Accelyte's Media and agencies process map, campaign delivery. Five of its seven stages apply; pitch and post-campaign review sit outside this scope. Numbers give the order of work.

01Brief

02Plan

03Buy and traffic

04Review

05Report and close

Client service

1Submit brief

7G2 Client approves plan

12G3 Client approves creative

15Post status, release reports

Planning

4G1 Accept brief and OKRs

6Build plan, staff by role

Buying and trafficking

8Book media in Mediaocean

10Traffic placements

13G4 Go-live check

Creative studio

11Proof creative

Finance

18G5 Close the month

Asana, integrations and agents

2Read brief, list gapsAI

3Draft campaign OKRsAI

5Create campaign and its goal

9Sync milestones and delivery

14Draft weekly statusAI

16Sync billing status

17Draft variance notesAI

Done by a person Approval gate, named approver Runs in Asana or the integration layer AIAgent draft; a person approves or posts it

Exceptions

Incomplete brief: Step 2 lists the gaps on the brief and returns it to client service. Planning never sees it.
Plan or creative rejected: The stage reopens and its gate repeats. Each decision stays on the approval task.
Under-delivery: Step 17 drafts a note when delivered falls below booked; finance reviews it before close.
Sync failure: The triage step opens a task for buying with the likely cause. The nightly check retries.

What changes at each stage

Stage	Today	In the design
Brief	Briefs arrive incomplete	The brief agent reads the client's document and fills the brief; incomplete briefs return before planning sees them. OKRs are drafted for G1
Plan	Each campaign starts from scratch	The campaign project and its goal are created from approved data; the capacity plan staffs by role before names are known
Buy and traffic	Manual handoffs	Rules assign the next team when a stage completes; milestones and delivery arrive from Mediaocean
Review	Feedback in email, no trail	Proofing on the asset; approval tasks record who signed off and when
Report and close	Status compiled by hand	Status and variance notes arrive as drafts; dashboards and campaign goals show progress to leaders

04Solution architecture

Native or Asana app Build in the integration layer, or MCP Dark outline: agent · Dashed box: outside the design

Architecture decisions

Asana runs the work. Mediaocean keeps the money.

Plans, bookings and billing stay in Mediaocean. Asana holds the plan ID, milestones, delivery and billing status, read one way and never written back. Finance keeps one source of truth for billed media.Pattern system of work, system of record · Vendor Mediaocean integrations27
Templates start campaigns. A bundle keeps them standard.

Four templates set up each campaign by type. One bundle carries the stage sections, shared fields and handoff rules, and an edit to it reaches every campaign that uses it. With 1,000 users, that stops each team drifting to its own version.Docs bundles, templates18, 1 · Map campaign delivery stages
One integration layer, checked nightly.

An iPaaS runs the four custom flows with retries, logs and one token per flow, under Asana's 1,500 requests a minute. Webhooks deliver at most once, and in August 2026 task change events stopped for about a day. A nightly job re-reads both sides and corrects drift.Docs webhooks, rate limits25, 16 · Practitioner thread26 · Pattern integration layer with reconciliation
Rules hand off. People approve.

Rules move work and assign the next team when a stage completes. Five gates stay with named approvers, and G1 also approves the campaign OKRs.Docs rules, approvals23, 4 · Pattern human gates, automated handoffs
Access follows the group directory.

Sign-in and provisioning come from the group identity provider. Leaders and finance readers take view-only seats. Integrations run as one integration user on the campaign teams only, because a service account with full permissions reaches all organisation data.Docs SSO, SCIM, view-only, service accounts7, 8, 19, 20 · Pattern least privilege
Models draft, code writes, people approve.

Agents read briefs, draft OKRs, status and variance notes, and triage sync failures. Structured writes go through code against a data contract, and client-facing output passes a named person. The OKR agent writes through the REST API, because neither the MCP server nor AI Teammates can create goals.Docs MCP server, AI Teammates, goal metrics30, 31, 33 · Pattern models draft, code writes, people approve

05Platform configuration

Work model

Group portfolioLeaders, view-only
Client portfolioOne per client
Campaign projectFrom template, bundle attached
Stage sectionsBrief to close
Approval tasks G1–G5Named approvers
Campaign goalObjective, linked to its project
Key-result sub-goalsTwo or three, one metric each
Campaign briefsIntake project with the form
TeamsOne per function, six

Custom fields

Field	Type	Set by
Client, market	Single-select	Brief form
Campaign type	Single-select	Brief form
Channels	Multi-select	Brief form
Flight start, end	Date	Brief form
Budget	Number, currency	Brief form
Primary KPI, target	Single-select, number	Brief form
Mediaocean plan ID	Text	Integration
Billing status	Single-select	Integration
Delivered vs booked	Number, percent	Integration

Fields set by the integration are corrected by the nightly check if someone edits them by hand. Field values follow contract C1 in section 11.

Components

Component	Configuration	Requirement met	Plan	Source
Intake
Brief form	One form in Campaign briefs. Branches by campaign type, channel and market. Objectives, budget, flight dates, primary KPI and target required.	Structured brief, routed by type	Advanced	2, 1
Brief agent	AI Teammate, default assignee of new briefs. Reads the client's brief from email or files, fills empty fields, comments with gaps.	Structured brief	Add-on	31, 1
Work model
Campaign templates	Search, social, display, video. Stage sections, milestones and approval tasks G1–G5.	Repeatable framework per type	Starter	1
Campaign bundle	Stage sections, shared fields and handoff rules, attached to every campaign project.	Standard stages with logic	Enterprise	18
Portfolios	One per client, nested in a group portfolio. The market field filters each view.	Every campaign in one view	Advanced	1
Automation
Handoff rules	Stage task completed: move to the next section, assign the next team's lead, post to its channel.	Automatic handoffs	Starter	3, 23
Approval rules	Approval status changes: notify the requester; on rejection, reopen the stage task.	Auditable sign-off	Advanced	23, 4
Status drafts	AI Studio workflow drafts each weekly status from the project as a comment; client service edits and posts it.	Roll-up status without manual work	Starter	21, 22
Review
Approvals	Five gates, each with a named approver. Decisions stay on the approval task.	Auditable sign-off at each gate	Advanced	4
Proofing	Images and PDFs marked up on the task. Video reviewed in the studio's tool and linked on G3.	Creative review, partial	Advanced	4
Resourcing, reporting and goals
Capacity plan	Allocations by role in weekly hours. Placeholders hold capacity before names are known.	Resource visibility before commitment	Enterprise	6
Dashboards	Leadership: campaigns by status, client and market. Finance: billing status and delivered versus booked.	Roll-up status without manual work	Advanced	5
Campaign goals	One objective per campaign, progress taken from two or three key-result sub-goals. Created after G1; delivery values daily from Mediaocean.	Measurable campaign outcomes, added	Advanced	34, 33

Sign-in, provisioning, audit and data location are set in section 07.

Edition this configuration needs

PlanEnterprise

Add-onsCompliance Management, AI Teammates

Full seatsDelivery teams, approvers, integration user

View-only seatsLeaders, finance readers

Capacity planning, placeholders, the bundle, single sign-on, SCIM and view-only seats set the plan. AI Teammates include 5 requests per user a month, up to 50 per account; above that, prepaid requests cost $0.50 each, sized from brief volume. Data residency joins only if Q2 requires it; Timesheets and Budgets only if Q3 does.1, 6, 18, 19

06Integrations and data flow

Asana app, native feature or AI Teammate Build in the integration layer, or MCP Letters and numbers match the table

Which mechanism, when

Webhook: Triggers only. Delivered at most once, so each webhook flow has the nightly check behind it.25
REST API: Every structured write: projects, fields, goals. Integration user, one token per flow.16, 24, 33
MCP: People working through Claude, ChatGPT or Gemini. Runs as the person, one workspace per session, one-hour tokens.29, 30
AI Teammate: Agent work inside Asana that reads email and files. Uses the triggering user's access.31, 32
File contract: Mediaocean, unless the client's contract includes API access (Q4).27
Asana app: Slack, Teams, HubSpot and Salesforce.15

Flows

Flow	From → to	Trigger	Data	Mechanism, identity, contract	Source
B	Email, files → Asana	Brief arrives	Client's brief into brief fields	AI Teammate connectorsTriggering user · drafts only	31
1	HubSpot → Asana	Task opened	Client and deal context	HubSpot app widget on tasks	13
2	Asana → iPaaS → Asana	G1 approved	Brief into a new campaign project	Webhook, then template instantiation, an asynchronous jobIntegration user · C1	25, 24
3	Mediaocean → Asana	Hourly	Plan ID, milestones, delivery, billing status	No Asana app; file or partner API, per Q4Integration user · C2	15, 27
O	iPaaS → Asana goals	G1 approved; daily	Approved OKRs; delivery values	REST: create goals, set metric valuesIntegration user · C3	33, 34
4	Salesforce → Asana	Order created or changed	ADvendio orders become trafficking tasks	Salesforce app; iPaaS only if Q5 shows the objects are out of reach	14, 28
5	Asana → Slack, Teams	Stage done, approval requested	Updates in team channels	Asana apps and rules integrations; Teams needs a paid Teams plan	11, 12, 23
6	Directory → Asana	Joiner or leaver	User accounts	SCIMScoped service account	8, 20
7	Asana → SIEM	Continuous	Audit events	Audit Log APIScoped service account	9, 20
A	Assistant ↔ Asana	Person asks	What that person can see or edit	MCP server V2, OAuth appThe person · full seats only, per Q7	29, 35
R	Both ways	Nightly	Flows 2, 3 and O	Re-reads both sides, corrects drift; triage drafts the likely causeIntegration user	25, 26

System of record for each data object

Data	Owned by	In Asana as
Clients and deals	HubSpot	Widget on tasks; client field
Orders	Salesforce, through ADvendio	Trafficking tasks
Media plans and bookings	Mediaocean	Plan ID and milestones
Billing and delivery	Mediaocean	Billing status, delivered vs booked
Pacing and performance	Media platforms	Not held
Campaign OKRs	Asana; delivery values from Mediaocean	Objective with key-result sub-goals
Briefs, work, approvals	Asana	Native records
People	Group directory	Synced user accounts

Build rules for the integration layer

Tokens: One per flow, since Asana applies limits per token.16
Throttle: Honour Retry-After; about 10 parallel workers at most.16
Contract check: Each record is checked against its contract before any write; failures are quarantined. Practice
Idempotent: Writes keyed on the contract's match key, so a re-run never duplicates. Practice
Agent writes: Drafts, comments and the agent's own tasks only; structured writes go through code. Practice
Failures: Record and error go to an operations channel, with the triage draft attached. Practice

07Access and governance

Role	Seat	Can do
Client service	Full	Own client portfolios, campaign projects and goals; record client decisions at G2 and G3
Planning, buying, trafficking	Full	Work stage tasks; approve G1 and G4
Creative studio	Full	Proof creative and answer feedback
Finance approver	Full	Approve G5. View-only users cannot complete tasks.19
Leaders, finance readers	View-only	Read portfolios, projects, goals and reporting; no edits, comments or integrations19
Integration user	Full	Campaign briefs and campaign teams only; one token per flow
Service account	Scoped	SCIM provisioning and audit log only20

Agents

Agent	Runs on, as	May write	Approved by
Brief agent	AI Teammate, with the triggering user's access; cannot raise its own permissions32	Brief fields, comments, subtasks	Planning lead at G1
OKR agent	Custom agent; code writes as the integration user	A draft comment; goals only after G1, through C3	Planning lead at G1
Status and variance	AI Studio; reads its triggering task and project22	Draft comments	Client service posts; finance at G5
Exception triage	LLM step in the iPaaS; read-only on Mediaocean	Exception tasks for buying	The buyer who resolves it
AI assistants	MCP, as the person who signs in29	What that person may edit	The person

Controls

Sign-in: SAML through the group identity provider. Session timeout from 1 hour to 30 days.7
Provisioning: SCIM from Okta, Microsoft Entra ID, OneLogin or Google Workspace.8
Audit: Asana keeps 90 days; the SIEM keeps the rest. Splunk and Panther integrations listed.9
Data location: Listed regions: United States, Germany, Japan, Australia. A UK-only rule goes to Asana before the quote.10
AI scope: A super admin enables Asana AI. Each AI Studio workflow reads only its triggering task and project unless a builder widens it.22
AI approvals: AI Teammates need the running user's approval to send email or remove members.31
Attribution: AI Teammate actions in connected apps appear as the triggering user's, so agents work in labelled comments and their own tasks.32
AI data: Asana's AI partners must delete customer data once a query completes.21

08Gaps and risks

Item	Why	Response	Source
GapVideo proofing	Proofing covers images and PDFs	Studio keeps its video review tool, linked on G3 (Q1)	4
GapUK data location	No listed UK region	Confirm with Asana before the quote (Q2)	10
GapSeveral approvers	Sits under Timesheets and Budgets	One approval task per approver, or the add-on (Q3)	17
RiskMediaocean access	No public developer programme shown	API if the client's contract allows; scheduled file if not (Q4)	27
RiskMissed change events	Webhooks deliver at most once	Nightly reconciliation	25, 26
RiskStale feed	A Mediaocean drop arrives late or not at all	Freshness check in C2; stale flag on the finance dashboard	Practice
RiskMonth-start volume	5 project creation jobs per user at once	Queue creation in the iPaaS	16
RiskInstructions in briefs	Client documents can carry text aimed at the agent	Brief agent writes fields and comments only; email and member changes need approval	31
RiskAI request quota	Included allowance caps at 50 per account	Prepaid requests sized from monthly brief volume	1
RiskWrong OKR draft	A model can misread an objective	Targets come only from brief fields; G1 approves every OKR	Practice
RiskAdoption	Five teams change tools at once	One-market pilot; an admin owns templates and the bundle	Practice

09Build plan and estimate

Phase

W10

W11

W12

0Confirm

1Foundation

2Work model

3Integrations

4Agents

5Pilot, one market

6Rollout, hypercare

Hatched: length depends on Q4 and Q5. Outlined: agents join the pilot once they pass their test sets.

Phases

Phase	Weeks	Delivers	Done when
Confirm	1	Answers to Q1–Q7, Asana quote, Mediaocean access	Design signed off
Foundation	1–3	SSO, SCIM, teams, admin and AI settings, audit feed	Test users sign in; audit events reach the SIEM
Work model	2–6	Fields, form, templates, bundle, rules, approvals, capacity plan, dashboards	One test campaign runs from brief to close
Integrations	4–9	Asana apps, campaign creation, Mediaocean sync, goal sync, ADvendio flow, nightly check	Seven days of syncs with no open exception
Agents	6–10	Brief agent, OKR agent, status and variance drafts, triage step	Each agent meets its agreed accuracy on a test set
Pilot	7–10	One market, two clients, live campaigns	Baseline and pilot figures for the four success measures
Rollout	10–12	Remaining markets, training, hypercare	All markets live; hypercare closed

Effort estimate Blueprint

Workstream	Basis	Days
Confirm and design sign-off	Seven questions, one review	3
Foundation: identity, admin, audit	SSO, SCIM, SIEM feed	5
Work model configuration	4 templates, 1 bundle, 10 fields, 5 gates, 2 dashboards	14
Asana apps and rules integrations	Slack, Teams, HubSpot, Salesforce	3
Campaign creation flow	Webhook, template instantiation, C1	4
Mediaocean sync and nightly check	C2; API at the low end, file at the high end	10–16
ADvendio flow	None if the Salesforce app reaches the orders	0–6
Agents
Brief agent	AI Teammate set-up, instructions, 20-brief test set	3
OKR agent and goal sync	Drafting step, Goals API writes, C3	6–8
Status and variance drafts	Two AI Studio workflows	2
Exception triage step	Classifier in the iPaaS, task template	3
Agent evaluation	Test sets, accuracy thresholds, sign-off	4–5
Delivery
Testing and acceptance	End-to-end, five gates, four flows	6
Pilot support	Four weeks, one market	8
Training and rollout	Five teams, remaining markets	8
Hypercare	Two weeks after the last market	4
Total		83–98

Team Blueprint

Role	Seniority	Owns	Weeks	Days
Solution architect	Senior	Design sign-off, open questions, acceptance, pilot steering	1, 8–10	9
Integration engineer	Senior	iPaaS flows, contracts C1–C3, nightly check, SIEM feed	1–9, 12	18–30
Asana consultant	Mid-level	Admin set-up, work model, Asana apps, training, hypercare	1–6, 10–12	26
AI engineer	Mid-level	Brief, OKR, status and triage agents; test sets	6–10	18–21
Test and adoption analyst	Junior	Test scripts, pilot support, training materials	7–12	12
Total		Senior 27–39 · Mid-level 44–47 · Junior 12		83–98

From the client: an ad operations product owner, about a day a week; an identity admin in weeks 1–3; a Mediaocean contact for Q4 and weeks 4–9; the finance approver for the pilot close.

Estimate from Accelyte delivery practice. Days by grade at your rate card give the price; the SOW draft carries this plan, team and exit criteria.

10Open questions and sign-off

Question for the clientEffect on the design

Is video creative reviewed in Asana or in a separate proofing tool?Asana proofing covers PDF, PNG, JPG, GIF and BMP files; video is not listed.4

None if the studio's tool stays; G3 links to it.

Does group policy require client data to be stored in the UK?Asana's listed residency regions are the United States, Germany, Japan and Australia.10

Sets the data route; may move the plan to Enterprise+.

Does any gate need more than one approver on the same item?Several approvers on one item sit under the Timesheets and Budgets add-on.17

Adds the add-on, or one approval task per approver.

Does the client hold Mediaocean API access, and which records should sync?Mediaocean lists API integrations with named partners; no public developer programme is shown.27

API: 10 days. Scheduled file: 16 days.

Do ADvendio orders sit in Salesforce objects the Asana app can read?ADvendio runs inside Salesforce.28

Yes removes the ADvendio build.

Do clients send briefs as documents or emails, and where do they land?The brief agent reads Gmail, Outlook, Google Drive and SharePoint.31

Sets the brief agent's connector; none if briefs only come through the form.

Should leaders ask an AI assistant about campaign status?View-only users cannot use integrations; assistants reach Asana through MCP as the person.19, 29

A yes moves those leaders to full seats.

Sign-off

Designed byAccelyte design agent, 18 October 2026

Reviewed byYour solution lead

Approved byClient sponsor

Next steps

Close the seven questions

The answers set the data route, both integration sizes and the agents' reach.

Sign off the design

Your lead reviews it; the client sponsor approves it.

Issue the SOW

Drafted from the build plan and estimate, at your rates.

11Data contracts

Every structured write passes one of three contracts. A record that fails is quarantined and raised as an exception; nothing partial reaches Asana.

Brief to campaign project

Once, on G1 approval · flow 2

Field	Type	Rule	Lands in
`brief_id`	Task ID	Required; match key	Link on the project
`client`, `market`	Enum	Values from the field options	Client, Market
`campaign_type`	Enum	search, social, display, video	Selects the template
`flight_start`, `flight_end`	Date	End on or after start	Flight fields; template start date
`budget`, `currency`	Decimal, ISO 4217	Budget above zero	Budget
`primary_kpi`, `kpi_target`	Enum, decimal	Both required	KPI fields; OKR agent input
`objectives`	Text	Required	Project brief; OKR agent input

A missing field returns the brief to client service. Nothing is created.

Mediaocean delivery and billing

Hourly, file or partner API · flow 3

Field	Type	Rule	Lands in
`plan_id`	String	Required; match key	Mediaocean plan ID
`campaign_ref`	String	Equals `brief_id`	Campaign project
`currency`	ISO 4217	Equals the brief's currency	Check only
`booked_amount`, `delivered_amount`	Decimal	Zero or above	Delivered vs booked; delivery key result
`billing_status`	Enum	pending, reconciled, rejected	Billing status
`milestones[]`	Name, due, done	Optional	Milestone tasks
`as_of`	UTC timestamp	At most 26 hours old; never older than the stored value	Freshness flag

Idempotent on plan_id and as_of. A booked amount of zero leaves the percentage blank. Statuses follow Mediaocean's invoice statuses; confirm under Q4.27

Campaign goal

Created after G1; values daily · flow O

Field	Type	Rule	Lands in
`objective`	Text, one sentence	Approved at G1	Goal; progress from its sub-goals
`key_results[]`	Name, unit, target	Two or three; percent, number or currency	One sub-goal each, one metric
`linked_project`	Project ID	Required; match key	Related work
`owner`	User	Client service lead	Goal owner
`period`	Date range	Flight dates	Goal dates
`current_value`	Number	Delivery: daily from C2. KPI: client service, from client reports	Metric current value

Targets come from brief fields and are approved at G1; the agent never changes them. KPI values come from client reports, not media platforms.34, 33

12Sources

Pricing and plan comparisonasana.com
How to use forms branchinghelp.asana.com
Workflow builderhelp.asana.com
Giving feedback and approvalshelp.asana.com
Portfolio dashboardshelp.asana.com
Capacity planninghelp.asana.com
Authentication and access managementhelp.asana.com
Provisioning users with SCIMhelp.asana.com
Audit Suite API and integrationshelp.asana.com
Data residency for Asanahelp.asana.com
Slack + Asanaasana.com/apps
Microsoft Teams and Asanahelp.asana.com
HubSpot + Asanaasana.com/apps
Salesforce + Asanaasana.com/apps
Asana app directoryasana.com/apps
API rate limitsdevelopers.asana.com
Release notes, September 2026forum.asana.com
Bundleshelp.asana.com
View-only licenceshelp.asana.com
Service accountshelp.asana.com
AI Studioasana.com
AI Studio adminhelp.asana.com
Rules integrations and widgetshelp.asana.com
Instantiate a project from a templatedevelopers.asana.com
Webhooks guidedevelopers.asana.com
Task change events not emitted, August 2026forum.asana.com
Prisma digital integrationsmediaocean.com
ADvendio product profilecapterra.com
Integrating with Asana's MCP serverdevelopers.asana.com
V2 MCP server generally availableforum.asana.com
AI Teammateshelp.asana.com
Access control for AI Teammateshelp.asana.com
Update a goal metricdevelopers.asana.com
Goal progress and connected workhelp.asana.com
Spring 2026 releaseasana.com

Accelyte knowledge used

Process map: Media and agencies, campaign delivery: seven stages, five used
Patterns: System of work and system of record; integration layer with reconciliation; human gates with automated handoffs; models draft, code writes, people approve; least privilege

Documentation read on 18 October 2026. Statements from delivery practice are marked Practice. Example output; client details anonymised.

About this example

Produced by the Accelyte design agent from one guided interview and an uploaded process flow. It builds on the example specification for the same use case. On paid plans it carries your brand. Run your own on Asana, free: accelyte.ai/asana-scoping-agent-form

Need fit and price only?

AI-assisted scoping returns the specification: accelyte.ai/scoping-agent-example