Spin up a client workspace when HoneyBook books a project
When a project is booked in HoneyBook, create the Google Drive folder, copy your Asana delivery template, and announce the win in Slack.
HoneyBook
Google Drive
Asana
SlackOperationsSalesOnboarding AutomationNotifications & AlertsBuild 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.
Additional information
What does this prompt do?
- Listens for new bookings in HoneyBook and kicks off the workspace setup automatically.
- Creates a dedicated Google Drive folder named with the client and event date so files have a home from day one.
- Duplicates your standard Asana delivery template into a fresh project so every onboarding task is pre-loaded.
- Posts a kickoff message in Slack with the client name, project type, event date, and budget, plus one-click links to the new folder and Asana project.
What do I need to use this?
- A HoneyBook account where you book projects.
- A Google Drive account with a parent folder where client folders should live.
- An Asana workspace with the delivery project template you want to clone for every new client.
- A Slack workspace and the channel you want kickoff announcements posted to.
How can I customize it?
- Change the Slack channel, or send to multiple channels for sales and delivery teams.
- Tweak the folder naming pattern (for example, add the project type or month) so files sort the way your team likes.
- Swap in a different Asana template per project type, or skip Asana for certain bookings.
- Edit the kickoff message to include extra context like the lead source, account owner, or a link to the HoneyBook project.
Frequently asked questions
Does this work for every type of HoneyBook project, or only certain ones?
What goes in the kickoff Slack message?
Can I use my existing Asana template instead of building a new one?
What if I want the client folder inside a specific parent in Google Drive?
Will this fire if I edit a project later in HoneyBook?
Related templates
Every Friday, get a ready-to-read preview of your league's weekend matches, with positions, form, scorers to watch, and predicted results, posted to Slack.
Every Monday morning, finance leadership gets a clear recap of last week's Braintree sales, refunds, and disputes by email and Slack.
Every morning we check your list of IP addresses for abusive activity, update your spreadsheet, and alert your team only about the risky ones.
Every time you ship to Heroku, we post a clear summary to Slack listing what changed, who deployed it, and whether it was a rollback.
Every weekday morning, your team gets one Slack briefing on who's flying today, their live flight status, and any delays or cancellations to act on.
Every Monday we scan your office, VPN, mail, and hosting IP ranges for abuse reports, post a summary to Slack, and open a ticket when anything crosses your risk line.
Stop rebuilding the same client workspace by hand.
Connect HoneyBook, Google Drive, Asana, and Slack once, and every new booking gets the full setup in seconds.