> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/flow/component-builder/interactions-panel/fire-confetti.md).

# Fire Confetti

The Fire Confetti interaction plays a celebratory confetti animation on screen.

## Overview

The fire confetti action is a fun and interactive feature that adds a celebratory element to a user's experience. When triggered, this action releases a shower of colorful confetti on the screen, simulating a real-life confetti celebration. This action is often used when a user has achieved a goal, completed a task, or reached a milestone. This action can be customized to change the appearance of the confetti.

## Configuration

Fire Confetti actions are accessible from the [Interaction Panel](https://docs.avonnicomponents.com/flow/component-builder/interactions-panel.md).

### Steps to follow

* **Open the Interaction Panel**
* Create your action
* Select "**`Fire Confetti`**" as an interaction type
* And select a variant. The available variants are **Base**, **Random Direction**, **Realistic**, **Fireworks**, **Snow**, and **Pride**.

{% hint style="warning" %}
Add [the interaction service component](https://docs.avonnicomponents.com/flow/flow-components/interaction-service.md) to ensure the fire confetti works appropriately.
{% endhint %}

## Example

| Name                                                                                                                                                                                            | Description                                                     | Illustration                                                                                                                                                                                                     |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [**Creating a Confetti Celebration on the Final Screen**](https://docs.avonnicomponents.com/flow/tutorials/components/delay-interaction/creating-a-confetti-celebration-on-the-final-screen.md) | Learn how to set up a confetti celebration on the final screen. | ![](https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2Fgit-blob-aa9c92d71a7bdad76216b98dc037ceab33a3624c%2F2023-07-04_10-08-29.png?alt=media) |

## Saved JSON example

Interactions are saved as a JSON array in the interaction attribute of the component. This is a "Fire Confetti" interaction using the exact key names:

```json
[
  {
    "type": "FireConfetti",
    "confettiVariant": "random-direction"
  }
]
```

* `type` is the interaction name, `FireConfetti`.
* `confettiVariant` is `base`, `random-direction`, `realistic`, `fireworks`, `snow` or `pride`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avonnicomponents.com/flow/component-builder/interactions-panel/fire-confetti.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
