> For the complete documentation index, see [llms.txt](https://tipn.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tipn.gitbook.io/docs/tipn-actions.md).
# Tipn Actions
## Overview
Normally, when a Tipn user likes a cast, the Tipn engine sends a USDC tip from the liker to the creator. Tipn Actions are a way to programmatically trigger onchain “actions” that augment the flow of value.
With Tipn Actions, tips are sent to an Action contract. The Action is invoked upon receiving the funds and can perform any onchain interaction. Example use cases include:
* Pooling funds into a prize
* Minting an NFT to the tipper
* Swapping USDC for tokens
Example flow for a Tipn Action whereby tips sent in the /tipn channel are pooled
## Creating a Tipn Action
Creating an Action consists of two steps
1. Implement an Action contract
2. List your Action in the Tipn app
A guide is provided for each below:
{% content-ref url="/pages/JoFjNGmUvUdddCYIfkiJ" %}
[Implement an Action](/docs/overview/implement-an-action.md)
{% endcontent-ref %}
{% content-ref url="/pages/3CtVWRtPJjg6vTeAFH6y" %}
[List an Action](/docs/overview/list-an-action.md)
{% endcontent-ref %}
{% hint style="info" %}
**Stuck somewhere?** React out to the [Tipn](https://farcaster.xyz/tipn) team on Farcaster for additional support.
{% endhint %}
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://tipn.gitbook.io/docs/tipn-actions.md?ask=&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 `build a script that syncs our docs to a CMS` 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.
