> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/no-code-platform/form-data-hub-events.md).

# Form data hub events

Data hub events can be used to start a dataflow

### Form data hub events

Currently supported form data hub events:

* ***On created***: this event is fired after a form is saved and this is a new form
* ***On updated***: this event is fired after a form is saved and this is an existing form
* ***On saved***: this event is always fired after a form is saved
* ***On deleted***: this event is fired after a form has been deleted

### How-to

To enable the events to be send to the data hub 2 settings need to be set on the form definition

The first one is the data hub property, this can be found under the category connections. The connection should be set to the data hub which will handle the events

The other property which needs to be set is one or more of the events 

<figure><img src="https://870194474-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_kE41Rl4pOtwKfvvQq%2Fuploads%2FwMPcs9pdGWsUZIOSQHwv%2Fimage.png?alt=media&amp;token=9cc8a68b-16e6-4925-b17c-5befc5d8c630" alt=""><figcaption><p>Data hub event properties</p></figcaption></figure>


---

# 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://academy.any2info.com/any2info-academy/no-code-platform/form-data-hub-events.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.