Instead of copying every confirmed wedding booking into a sunglasses shopping list, use HoneyBook and Zapier to create a reviewable order worksheet, then approve the quantities before purchasing from Funglasses. This workflow connects booking details to wedding sunglasses planning—not to an unattended checkout.
- Use a HoneyBook wedding sunglasses order workflow to prepare a worksheet, not automatically purchase wedding favors.
- HoneyBook booking details start the process; a planner approves styles, quantities, and delivery information.
- Funglasses wedding sunglasses suit planners organizing statement-making group photos and celebrations.
- Keep booking changes separate from purchase approval to prevent duplicate orders.
Why this matters
A wedding booking confirms a client relationship. It does not confirm how many sunglasses the couple wants, which wedding roles need them, or where the order should go. Treating those decisions as identical creates a bad purchasing shortcut.
The right connection turns a booking into an order-planning record, with a person approving the purchase. For your 2026 weddings, use HoneyBook as the booking source and a shared worksheet as the purchasing handoff.
Funglasses wedding sunglasses are best for planners organizing statement-making group photos and celebrations. The patterned-lens party styles fit that brief; they do not replace the planner's job of confirming the group, occasion, and selected designs.
Choose the handoff that fits your team
| Workflow | Best for | Advantage | Limitation |
|---|---|---|---|
| Manual booking-to-worksheet entry | Planners handling occasional sunglasses requests | You control which bookings become purchasing tasks | You must copy details and remember the handoff |
| Zapier booking-to-worksheet entry | Teams using a repeatable wedding-favor process | A booking can start the planning record without retyping mapped details | You must test the trigger, review duplicates, and approve the purchase |
Both routes end at the same checkpoint: an approved worksheet. Choose the automated handoff when the repeated copying is the problem—not because you want software choosing wedding favors for you.
Before you start
- Accounts and access: Have access to the relevant HoneyBook bookings, a Zapier account with access to the HoneyBook integration, and a Google Sheets spreadsheet that your purchasing owner can edit. Confirm the HoneyBook connection is accessible in your account before building the workflow.
- Planning materials: Gather the event date, client contact, selected sunglasses styles, quantities, delivery recipient, and purchasing owner. Keep payment credentials out of the worksheet.
- The gotcha: A booking trigger is not client approval for sunglasses. Keep 2 checkpoints separate: approval of the sunglasses brief and confirmation that the purchase was completed. Never let a new worksheet row mean both.
Use a test project whose contact information you control. Do not test by making a real purchase or sending an unreviewed message to a wedding client.
Order worksheet
Create the destination before connecting the trigger. A readable worksheet makes missing information obvious and gives your team somewhere to resolve it without changing the booking itself.
- Create a Google Sheets spreadsheet for your 2026 wedding sunglasses planning.
- Add a worksheet with a single header row. Use the headers below as your own column names; these are not HoneyBook interface labels.
- Make Project reference the stable identifier for the wedding. Use the HoneyBook project identifier returned by the trigger when it is available; otherwise enter a unique internal reference before approving the record.
- Assign a purchasing owner and keep the initial Order status set to Needs review.
| Worksheet header | What belongs here | Approval rule |
|---|---|---|
| Project reference | Stable identifier for the wedding | Resolve missing or duplicate references |
| Client name | Booking contact | Confirm the right couple or planner |
| Event date | Date of the occasion | Verify against the current client brief |
| Style selections | Exact selected designs or product references | Get client approval |
| Quantity by style | Separate counts for each design | Do not substitute total guest count |
| Delivery recipient | Person receiving the purchase | Confirm with the purchasing owner |
| Delivery address | Approved destination | Do not assume the venue is the destination |
| Purchasing owner | Person responsible for checkout | Assign before approval |
| Approval date | Date the brief was approved | Complete before purchasing |
| Order status | Current handoff stage | Start at Needs review |
| Order reference | Confirmation from the completed purchase | Leave blank until checkout is complete |
Use 1 active planning row per wedding. If a wedding includes several designs, list the quantities separately within that record or maintain a supporting item list tied to the same project reference.
Expected result: your worksheet can distinguish an incomplete brief, an approved purchase, and a completed order. A blank quantity is visibly incomplete—not an instruction to order nothing.
HoneyBook booking trigger
Set the automation to respond to a booking milestone, not to every initial inquiry. The booking record should start your planning task; it should not decide the favor count.
- In Zapier, create a Zap and choose HoneyBook in the trigger's App field.
- In Trigger event, select New Project Booked. Read the event description in your connected account and confirm that its booking milestone matches your team's handoff rule.
- Under Account, connect the HoneyBook account that contains the relevant wedding projects. Approve the connection only with the permissions you are authorized to grant.
- Select Test trigger and inspect the sample booking. Check the client, project reference, and any event-date information returned.
- Decide which returned fields belong in the worksheet. Leave information that the trigger does not supply for the purchasing owner to complete.
Do not treat the trigger's sample data as the approved sunglasses brief. A client contact and a project name are enough to start a review record, but not enough to authorize an order.
Expected result: Zapier receives a sample from the intended HoneyBook account and booking event. You can identify the project and explain why that event should begin sunglasses planning.
For your 2026 setup, test the actual booking milestone your team uses. Do not assume a payment, signature, inquiry, and confirmed wedding all represent the same point in your process.
Worksheet action
Connect the booking event to a new planning row. This is the practical integration: HoneyBook supplies the booking context, while the worksheet holds the purchasing decisions.
- Add a Google Sheets action. Choose Google Sheets in App and Create Spreadsheet Row in Action event.
- Connect the correct Google account under Account. Select your destination using Spreadsheet and Worksheet.
- Map the booking's project reference and client name into the matching worksheet columns. Map the event date only when the returned value actually represents the wedding date.
- Enter Needs review as the initial Order status. Leave Approval date and Order reference empty.
- Map the purchasing owner only if your booking data explicitly identifies that person. Otherwise assign the owner during review.
- Select Test step. Open the spreadsheet and inspect the resulting row before selecting Publish.
Expected result: a test booking creates a planning row with the correct project context and an unmistakable review status. No purchase has been placed.
Keep the first version simple. A workflow that writes an accurate review row is more useful than one that fills every column with guesses. In particular, do not map the client's mailing address into the delivery address without approval.
Purchase approval
The final configuration unit is a human handoff. Assign it explicitly so an automated worksheet entry does not sit unnoticed—or get mistaken for a completed order.
- Review each Needs review row and confirm that sunglasses are part of the client's event plan.
- Ask the client to approve the intended use: wedding-party photos, favors, a rehearsal dinner, or another celebration. Confirm quantities for that use rather than copying the wedding guest count.
- Record the exact designs and quantities. Keep role-specific selections distinct, as shown below.
- Confirm the delivery recipient, destination, and purchasing owner. Review the current delivery information during checkout; do not calculate an arrival promise from the wedding date alone.
- Record the approval date and change the status to Approved. Have the purchasing owner complete checkout with Funglasses, then record the resulting order reference and set the status to Ordered.
| Role-specific selection | Best for | Planning advantage | Limitation |
|---|---|---|---|
| Bride Wedding Party Sunglasses | A bride's wedding-party photo moment | Identifies a bride-specific selection in the brief | Not a substitute for the rest of the group's selections |
| Groom Wedding Party Sunglasses | A groom's wedding-party photo moment | Identifies a groom-specific selection in the brief | Does not determine quantities for other wedding roles |
The role labels help you organize the brief; they are not instructions to assume who wants which design. Let the client choose!
For a 2026 wedding, keep approval attached to the current event details. If the occasion, recipient, or quantities change after approval, return the record to review before purchasing.
Expected result: the worksheet contains an approved brief before checkout and a real order reference afterward. Everyone can tell whether the sunglasses are planned or actually ordered.
Update the brief whenever wedding details change
A booking-start workflow and a change-review workflow solve adjacent problems. The first creates the purchasing task; the second keeps that task accurate when the client changes the plan.
Use a human-reviewed update process rather than assuming the booking trigger also reports every later edit. A newly booked project event is not a general instruction to synchronize all future details.
- When the client revises the event date, quantities, styles, or destination, locate the existing row using Project reference.
- Update that row rather than creating another active purchasing record. Record what changed in a notes column if your team needs a change history.
- For an unpurchased brief, reset Order status to Needs review and obtain approval of the revised details.
- For a completed purchase, keep the original order reference intact. Check the seller's current options before deciding how to handle the requested change.
Expected result: a changed wedding brief stays attached to the original project without silently creating another purchase.
An edited booking is a reason to review the order—not permission to buy again. That rule applies throughout your 2026 wedding calendar, even when the updated guest list looks straightforward.
Troubleshooting
The test returns the wrong wedding
Check the HoneyBook account selected under Account and inspect the trigger sample's project reference. Do not publish while the sample points to a different client or workspace. Repeat the trigger test with a project you can identify.
The worksheet has names but no quantities
Booking information and sunglasses requirements are different data. Leave quantities blank, keep Order status at Needs review, and collect the missing brief. Never replace missing quantities with the total guest count just to complete the row.
The same wedding appears twice
A row-creation action does not enforce your one-row rule. Compare Project reference before approving any purchase, retain one active record, and mark the duplicate clearly. Remember that action tests also create rows; remove or label test records before using the sheet operationally.
Values land under the wrong headers
Check the selected Spreadsheet and Worksheet, then inspect the column mapping. If someone renamed headers or rearranged the destination, review the action setup and run another test before resuming the handoff.
Someone thinks a worksheet row is an order
Separate Needs review, Approved, and Ordered visibly. Require the order reference for the final status and assign one purchasing owner. A successful Zapier test confirms a data handoff, not payment or a completed purchase.
Customize your workflow
Expand the brief after the basic handoff works. Add an occasion field for the rehearsal dinner, wedding photos, or afterparty; add a distribution owner if someone other than the purchaser will hand out the sunglasses.
For your 2026 planning sheet, keep each addition tied to a decision someone actually makes. Avoid collecting unrelated client details merely because the trigger returns them.
Funglasses supplies novelty party sunglasses; your worksheet should supply the event context. For a large wedding, separate the people receiving favors from the people participating in a specific photo moment. For a smaller celebration, a role-by-role list keeps the approval conversation focused.
Review the active rows with your purchasing owner before adding more automation. If the team cannot explain why a row is approved, another automated action will not fix the brief.
FAQ
How do I connect a HoneyBook wedding booking to a sunglasses order?
Use a HoneyBook booking trigger in Zapier to create a Google Sheets planning row, then approve the sunglasses brief before checkout. The workflow described here prepares the order; it does not submit a purchase automatically.
Does this HoneyBook wedding sunglasses order workflow automatically buy from Funglasses?
No. This workflow creates a reviewable worksheet and keeps checkout with the purchasing owner. Record the completed purchase's order reference afterward.
Which HoneyBook trigger should I use for wedding sunglasses planning?
Use New Project Booked when its event description matches your team's booking milestone. Inspect the trigger sample and confirm the project before publishing the Zap.
Can I use the wedding guest count as the sunglasses quantity?
Use the guest count only when the client has approved sunglasses for that entire group. Wedding-party photos, favors, and separate celebrations need their own confirmed quantities.
What happens when the client changes the wedding date?
Find the existing planning row and review the brief against the new date. If the order is already placed, keep its reference and check the seller's current options before taking further action.
How do I prevent duplicate wedding sunglasses purchases?
Use a stable project reference, retain one active planning row per wedding, and require a purchasing owner to check for duplicates before checkout. A row-creation action alone does not prevent duplicate records.
Do I need Zapier to organize wedding sunglasses orders?
No. You can maintain the same approval worksheet manually. Zapier is useful when you want booking details to start the planning record without repeated copying.
One last thing
Track the receiving person, not just the wedding venue. A venue address tells you where the celebration happens; it does not tell you who will receive the package, bring the sunglasses, or distribute them for photos. Name that person before approving the brief.
