← All guides
Bonus Guide · GitHub · LWC Install

Install the Confetti LWC
from GitHub

No git knowledge required. No command-line typing. Claude does the work — you just paste a folder path, approve a few prompts, and drag-and-drop to finish.

Updated Sep 2, 2026
See it in action

The whole install, start to finish — download, prompt, approvals, drag-and-drop, confetti.

🎉
Install the Confetti LWC from GitHub
No git knowledge. No command-line typing. Claude does the work.
How easy this actually was Paste a folder path, approve a few prompts, drag-and-drop to finish. That is the whole thing. Here is what happened step by step.
1
Download the code from GitHub — no git required

Go to the Custom Confetti GitHub repo. Click the green Code button then Download ZIP. Save it somewhere you can find it (Downloads is fine). Unzip it.

That is the only step you do yourself Everything after this — moving files, running the deploy, wiring it up — Claude handles.
2
Tell Claude where you put it

Open Claude Code (Ctrl + Esc) and paste this prompt — just swap in your actual folder path:

Claude Code prompt I have downloaded and unzipped the confetti LWC from GitHub. The unzipped folder is at: C:\Users\YourName\Downloads\confetti-lwc-main Please copy the component files into this project and deploy to my connected org.

Claude knows your project structure. It will move the four component parts — the confetti widget, helper code, settings object, and starter colour themes — into the right spots automatically.

3
Approve the permission prompts as they appear

Claude will pop up a permission prompt each time it wants to run a terminal command. You will see this a few times. That is a built-in safety check — not a sign of trouble.

In this specific install, each prompt maps to one safe action:

What each prompt is actually doing
1
sf org list — checks which org is connected. Reads only, changes nothing.
2
Copy-Item — moves your downloaded files into the project folder. Stays entirely inside your own machine.
3
sf project deploy start — uploads the component to your already-connected org. Adds new pieces only, removes nothing.
Good habit to keep It is safe to approve all three of these because each one acts only on your own downloaded files and your own connected org — nothing reaches outside that scope. That said, it is always worth a quick glance at what a prompt says before approving rather than auto-approving everything forever.
4
Drag and drop to finish — in Salesforce, not VS Code

Once Claude confirms the deploy succeeded, go to your Salesforce org. Open any record page in App Builder (Setup → App Builder, or the gear icon on a record → Edit Page).

Find Custom Confetti in the component list on the left. Drag it onto the page. Fill in three properties: Field API Path (the object and field together, e.g. Opportunity.StageName), Trigger Value (e.g. Closed Won), and Confetti Theme — paste the theme's API Name, not its Label (e.g. Green_Yellow, not "Green Yellow"). Save and activate.

A word from an Aussie It's Colour. Not Color. Every field, every label, every theme in this build spells it properly — six letters, one very important U. If your fingers just autocorrected that out of habit, put it back. 🇦🇺
Done Go to a record, set your field to the trigger value, and watch it go. Total effort: paste a folder path, approve three prompts, drag-and-drop.

That's it — go make it rain confetti 🎉

One ZIP download, one prompt to Claude, three approvals, one drag-and-drop.
That's the whole path from "found a component on GitHub" to "it's live on a record page."

Found this useful?
Mia
Builds on the VS Code + Salesforce + Claude setup guide — get that running first.

⚠️ This guide assumes a Developer Edition org only. Do not deploy to a production or sandbox org without understanding what you're deploying and getting appropriate approval first.