Browse the docs

Agent setup guide

Creative Brief Intake

Turns each client request into a structured creative brief, files it as an Asana task and emails the client the open questions.

Available About 12 min to set up

What it does

Turns each client request into a structured creative brief, files it as an Asana task and emails the client the open questions.

  • Starts when your client request form posts to the webhook.
  • AI writes a structured creative brief (objective, audience, deliverables and specs, key message, tone, mandatory elements, deadline) and up to 6 clarifying questions, using only what the client wrote.
  • Creates a task with the brief in your Asana intake project.
  • Emails the client a confirmation with the questions, Reply-to your studio inbox. Unclear, out-of-scope or money questions wait for approval; switch review on to approve every one.

What it needs

  • A paid plan (agents run live on paid plans).
  • An AI provider key (Settings → AI Providers).
  • Asana, connected in Settings → Integrations.
  • A request form or site that can post to a webhook.

What it doesn't do

  • It doesn't assign designers, set due dates or estimate hours.
  • It files every request in one intake project (one per setup).
  • It never promises prices or dates you haven't written in your studio rules.
  • It doesn't read attached files, only the text and links in the request.

Availability and plans

Available

Its workflow is built and tested, and every app it needs is live. You can get it and set it up now.

Included free on the Enterprise plan; on other paid plans it's a one-time purchase per workspace (the price is on the Agents page). The Agents page in the app always shows its current status.

Before you start

  • A paid plan: agents run live, and the Free plan only runs Dry Runs.
  • An AI provider key (OpenAI, Anthropic, Google and more) in Settings → AI Providers. AI usage is billed by your provider.
  • These apps, connected in Settings → Integrations: Asana.
  • A form, app or system that can send each new item to a webhook URL (the agent starts from a webhook).
  • About 12 minutes.

Set it up step by step

Get the agent first (buy it, or it's already yours when your plan includes it), then in Agents → My agents press “Set up this agent”. That creates the agent's workflow in your workspace (it counts towards your plan's workflow limit) and opens the canvas with a setup checklist above it. Each item links to the exact place to go and ticks itself off when it's done.

1. Connect your AI provider

The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.

2. Connect Asana

Connect Asana (Settings → Integrations → Asana).

3. Describe your studio

Open “Write the creative brief” and replace the placeholder with your studio and brief rules.

SettingWhat to enterIn step
Your studio and brief rulesReplace the placeholder with your studio, the work you take on (deliverables, formats, brand rules), what a complete brief needs, what happens next for the client and your team name. It starts as “[DESCRIBE YOUR STUDIO OR TEAM, THE WORK YOU TAKE ON (DELIVERABLE TYPES, FORMATS, BRAND RULES), WHAT A COMPLETE BRIEF NEEDS, WHAT HAPPENS NEXT FOR THE CLIENT AND YOUR TEAM NAME HERE]” until you replace it.“Write the creative brief”

4. Pick the Asana project

Open “Create the task in Asana” and pick your account, workspace and intake project.

SettingWhat to enterIn step
Asana accountThe Asana account the intake task is created in. Pick your connected Asana account.“Create the task in Asana”
Asana workspaceThe workspace your intake project is in.“Create the task in Asana”
Intake projectThe project each brief becomes a task in, e.g. “Creative requests”.“Create the task in Asana”

5. Add your studio inbox

Open “Email the client” and enter the address the client's answers should go to.

SettingWhat to enterIn step
Studio inbox (Reply-to)The client's answers to the questions come back to this address.“Email the client”

6. Test it with Dry Run

Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.

7. Switch the trigger on

Open the trigger, copy the webhook URL and secret into your request form or site, and switch it on. Fields: client, name, email, request, deliverables, deadline, budget, references.

How it works

The agent is a normal workflow with 9 steps (1 AI step, with a person approving in Reviews). You can open, edit and monitor it like any other workflow.

  • New client request — Starts when your form or app sends data to the agent's webhook URL. Your client request form (or your site) posts each request to this webhook.
  • Write the creative brief — AI step (runs on your AI provider key). AI turns the request into a structured brief (objective, audience, deliverables, specs, tone, deadline) and lists the clarifying questions.
  • Create the task in Asana — Asana: Create a task. Creates a task in your intake project with the brief and the open questions.
  • Task created — Kept in the run history. The run history keeps the Asana task link.
  • Send the confirmation how? — Decision: picks the branch to follow. No email address: no confirmation. Routine requests: sent at once. Unclear, out-of-scope or money questions (or every one, if you switch review on): approved first.
  • No confirmation — Kept in the run history. Branch: No email. The request had no email address; the task is in Asana.
  • Approve the confirmation — A person approves or rejects it in Reviews (the run waits). Branch: Review. A teammate checks the confirmation and questions in Reviews, edits them if needed and approves.
  • Email the client — Sends an email from your workspace's sender. Branch: Routine / Approved. Emails the confirmation with the clarifying questions, with replies going to your studio inbox.
  • Confirmed — Kept in the run history. The run history keeps the brief and the confirmation.

Test it with Dry Run

Press Dry Run in the canvas. The agent runs on the sample data stored on its trigger (the “Sample data for Dry Run” box), so you can check every step's output before anything is live. Edit the sample to match the fields your own form or app sends.

Sample data fields

client, name, email, request, deliverables, deadline, budget, references.

  • Nothing is sent or written: app actions, emails and Slack posts are simulated, and AI steps don't call your AI provider.
  • Approval steps use the Dry Run decision you pick in the step's settings (approved, rejected or timeout), so you can try each branch.

Go live

  • Open the trigger, copy the webhook URL and secret into your request form or site, and switch it on. Fields: client, name, email, request, deliverables, deadline, budget, references.
  • The webhook is protected by a secret: send it in the header shown in the Activation panel (requests without it are refused with 403). Each request starts one run.
  • The setup checklist adds a “paid plan” item before activation: live runs need a paid plan (the Free plan only runs Dry Runs).
  • When every checklist item is done and the trigger is on, the checklist says “Live — this agent is running”. Follow its runs in the workflow's History tab and in Analytics → Agents.

Questions

Does it assign designers or estimate hours?

No. It creates the task in your intake project with the brief; your team assigns and estimates.

Can I approve every confirmation?

Yes. Change “REVIEW EVERY CONFIRMATION: no” to “yes” in the brief step.

Troubleshooting

  • “No AI provider connected” or a rejected key: connect or fix the key in Settings → AI Providers, then press Test there.
  • A checklist item stays unticked: the setting is still empty or still contains its placeholder text. Open the step from the checklist and fill it in.
  • An app step fails with “Needs reconnect”: the account's access was revoked or expired. Reconnect it in Settings → Integrations.
  • Nothing happens when your form sends data: check the webhook is switched on and the request carries the secret header (403 means it's missing or wrong).
  • A run shows as paused: it's waiting for someone in Reviews to approve or reject it.
  • A step failed: open the run in History and check that step in the Trace tab for the error and what it received.

Generated from the agent's own workflow, so it always matches what the agent does. Last updated .