Spin up a client workspace when HoneyBook books a project

Build a code workflow that spins up the full client workspace the moment a project is booked in HoneyBook. The goal is to remove the manual scramble after a booking: folder, project plan, and team announcement should all be ready before anyone touches a keyboard.

Trigger: a HoneyBook webhook on the project_booked event. Use the Webhook Events reference in the HoneyBook integration to set up the subscription and read the payload (client name, project type, event date, budget, and project id at minimum).

Step 1: in Google Drive, run Create Folder. Name the folder using the client name and the event date (for example, "Smith Wedding 2026-09-12"). Let me configure a parent folder id so every client folder lands inside our shared "Clients" folder. Capture the new folder id and web view link.

Step 2: in Asana, run Duplicate a Project against our standard delivery template so every onboarding task, section, and custom field comes pre-loaded. Let me pick the template project id and the destination team. Name the new project with the same client name and event date. If the duplicate operation needs a fallback, Create a Project against the template team is acceptable. Capture the new Asana project id and permalink.

Step 3: in Slack, run Send a Message to post a kickoff announcement in our #bookings channel (let me pick the channel). The message should celebrate the win and include: client name, project type, event date, budget, a link to the Google Drive folder from Step 1, and a link to the Asana project from Step 2. Format it so the links are clearly clickable and the key facts are scannable.

Keep this deterministic (no agent reasoning needed): HoneyBook fires the webhook, the workflow runs Drive, Asana, then Slack in order, and surfaces clear errors if any step fails so we can retry. Do not create the Slack message if either Drive or Asana fails; the team should only see announcements for fully provisioned workspaces.