> 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/upsert-record.md).

# Upsert Record

The **Upsert Record** interaction creates or updates a Salesforce record directly from the component in a single step.

## Overview

The **`Upsert Record`** interaction triggers a record upsert operation. Use this interaction to create or update a Salesforce record directly from the component: if the record already exists, it is updated; otherwise, a new record is created.

## Configuration

### **On Success**

The interactions to execute when the record upsert succeeds. Accepted interactions are: [Show Toast](/flow/component-builder/interactions-panel/show-toast.md), [Flow Navigation](/flow/component-builder/interactions-panel/flow-navigation.md), [Refresh All Queries](/flow/component-builder/interactions-panel/refresh-all-queries.md) and [Fire Confetti](/flow/component-builder/interactions-panel/fire-confetti.md).

### **On Error**

The interactions to execute when the record upsert fails. Accepted interactions are: [Show Toast](/flow/component-builder/interactions-panel/show-toast.md), [Flow Navigation](/flow/component-builder/interactions-panel/flow-navigation.md), [Refresh All Queries](/flow/component-builder/interactions-panel/refresh-all-queries.md) and [Fire Confetti](/flow/component-builder/interactions-panel/fire-confetti.md).

## Example

Imagine a screen flow where users maintain their notification preferences. An Upsert Record interaction saves the preference record in a single step — creating it the first time and updating it on every subsequent visit — without any additional logic in Flow Builder to decide between a create and an update. On success, a Show Toast interaction confirms the save; on error, a Show Toast interaction with the `Error` variant surfaces the problem.


---

# 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/upsert-record.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.