> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/workflow/handle-outcomes/component-success-and-failure-actions.md).

# Run actions after component success or failure

In this section you will learn about Success/Error Actions

Use success and error actions in a component's **Actions** configuration to respond after its base action completes. For example, navigate after a form submission or show a failure response.

These are component callbacks. They do not define a global error handler for every workflow step.

## Configure a callback

1. Select the button or component.
2. Open its **Actions** tab.
3. Select **Success Action** or the error action.
4. Choose the response and configure its inputs.

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LQ08RFAKZvFADEiXKFy%2F-MkG1RiPTKWfDYvDfjhH%2F-MkG334b4SIDDLtwVkWa%2Fimage.png?alt=media\&token=d66463c5-2968-4386-8712-a5313d078e32)

Multiple callback operations run in parallel rather than as a guaranteed sequence. If a notification depends on an earlier update's result, put the dependent operations in an explicitly ordered workflow.

## Navigate after success

Choose **Navigate to Page** as the success action and select the destination page.

{% @arcade/embed url="<https://app.arcade.software/share/3YAWw7T7y6NdF4icSGKN>" flowId="3YAWw7T7y6NdF4icSGKN" %}

Test both a successful submission and a failed submission. The app should navigate only after the intended successful action.

## Send an email after success

Choose **Run Operation → App Built-ins → Send Email** and configure the recipient and message.

{% @arcade/embed url="<https://app.arcade.software/share/X04eNBXIEVrUn6kV9tWv>" flowId="X04eNBXIEVrUn6kV9tWv" %}

Test with an address you control. Use dynamic values from the action's available context rather than a fixed recipient intended only for setup.

## Verify failure behavior

Cause a controlled failure using fictional input. Confirm that the error response appears and that success-only effects do not occur. Check whether the base action changed any data before retrying.

See [failure handling](/workflow/handle-outcomes/handle-failures-and-prevent-duplicate-processing.md) and [running a workflow from a callback](/workflow/start-a-workflow/run-from-a-button-or-list-action.md).


---

# 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.jetadmin.io/workflow/handle-outcomes/component-success-and-failure-actions.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.