> 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/videos/all-videos/page-1/capture-a-signature-and-update-an-opportunity-in-salesforce-flow.md).

# Capture a Signature and Update an Opportunity in Salesforce Flow

Screen Flows · 7:35

A signature pad in a screen flow that saves the file on the opportunity and closes the deal as Closed Won.

{% embed url="<https://www.youtube.com/watch?v=WFQ2i_0AFzM>" %}

## Chapters

* [0:00 Capture a signature in a Salesforce screen flow](https://www.youtube.com/watch?v=WFQ2i_0AFzM\&t=0)
* [0:13 Why Salesforce Flow has no signature component](https://www.youtube.com/watch?v=WFQ2i_0AFzM\&t=13)
* [0:52 Use case: close an opportunity with a signature](https://www.youtube.com/watch?v=WFQ2i_0AFzM\&t=52)
* [1:20 The screen flow plan in Flow Builder](https://www.youtube.com/watch?v=WFQ2i_0AFzM\&t=80)
* [1:45 Prerequisites](https://www.youtube.com/watch?v=WFQ2i_0AFzM\&t=105)
* [2:06 recordId variable (the number one trap)](https://www.youtube.com/watch?v=WFQ2i_0AFzM\&t=126)
* [2:30 Get Records: read the opportunity](https://www.youtube.com/watch?v=WFQ2i_0AFzM\&t=150)
* [2:46 Decision: stop a double signature](https://www.youtube.com/watch?v=WFQ2i_0AFzM\&t=166)
* [2:57 Review screen with a Record Choice Set](https://www.youtube.com/watch?v=WFQ2i_0AFzM\&t=177)
* [3:26 Formula for the signature file name](https://www.youtube.com/watch?v=WFQ2i_0AFzM\&t=206)
* [3:37 Sign screen: add the Avonni Input Pen](https://www.youtube.com/watch?v=WFQ2i_0AFzM\&t=217)
* [3:54 Configure the signature pad in the Component Builder](https://www.youtube.com/watch?v=WFQ2i_0AFzM\&t=234)
* [5:02 Update Records: set the opportunity to Closed Won](https://www.youtube.com/watch?v=WFQ2i_0AFzM\&t=302)
* [5:19 Fault path: a clear error message](https://www.youtube.com/watch?v=WFQ2i_0AFzM\&t=319)
* [5:33 Quick action for the record page and mobile app](https://www.youtube.com/watch?v=WFQ2i_0AFzM\&t=333)
* [6:00 Test: sign and close the deal](https://www.youtube.com/watch?v=WFQ2i_0AFzM\&t=360)
* [6:38 4 pro tips for screen flows](https://www.youtube.com/watch?v=WFQ2i_0AFzM\&t=398)
* [6:58 Recap](https://www.youtube.com/watch?v=WFQ2i_0AFzM\&t=418)

## Related documentation

[Follow the documentation](https://docs.avonnicomponents.com/flow/flow-components/input-pen)


---

# 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/videos/all-videos/page-1/capture-a-signature-and-update-an-opportunity-in-salesforce-flow.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.