> 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/actions/data-manipulation-and-transformation/convert-lead.md).

# Convert Lead

## Overview

This action lets you convert leads into accounts, contacts, and opportunities directly within your Salesforce flows. Automating this process can save time, reduce errors, and ensure a smooth transition from lead to customer.

***

## How it Helps

Instead of manually converting leads in Salesforce, this action lets you seamlessly integrate lead conversion into your automated flows. This is particularly helpful for onboarding new leads or qualifying leads based on specific criteria.

***

## When to Use It

This action is ideal when you need to:

* **Automate lead conversion based on specific criteria or actions in your flow.**
* **Streamline the lead-to-customer conversion process.**
* **Ensure consistent and accurate lead conversion.**
* **Reduce manual data entry and potential errors.**

***

## Example

To automatically convert qualified leads after they reach a certain stage:

1. **Configure the Action:** Specify the lead to be converted and configure optional settings like creating or linking to existing accounts, contacts, and opportunities.
2. **Trigger the Action:** Use a Decision element in your flow to trigger the "Convert Lead" action when a lead meets your defined criteria (e.g., lead status is "Qualified").

***

## Key Considerations

* **Optional Settings:** The action provides toggles for various settings, allowing you to customize the conversion process.
* **Record Relationships:** Consider how the relationships between accounts, contacts, and opportunities align with your flow's logic.
* **Lead Conversion Rules:** Be aware of your organization's standard Salesforce lead conversion rules, as they may affect the conversion process


---

# 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/actions/data-manipulation-and-transformation/convert-lead.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.