How Can n8n Automatically Mark Leads as Converted?

You can use n8n to automatically mark a Referral Factory Lead as converted when a specific action happens in another system.

In Referral Factory, marking a Lead as converted means changing their status from Pending to Qualified. The native Referral Factory node in n8n includes a Qualify User action, so you can do this directly without building a custom API request.

Start your n8n workflow with the app or system where the conversion happens.

For example, you might qualify a Lead when:

Then:

Your workflow could look like this:

CRM Deal becomes Closed Won → n8n → Referral Factory Qualify User

Or:

Customer completes payment → n8n → Referral Factory Qualify User

The first node in your n8n workflow determines what event should count as a conversion.

If your conversion happens in a CRM, choose the record or object that contains the conversion information and configure the trigger around the field, status, or stage your business uses to identify a successful customer.

For example:

Deal/Opportunity → Stage changes to Closed Won

or:

Contact → Lifecycle Stage changes to Customer

If your conversion happens outside your CRM, the trigger could instead monitor something such as a successful payment, completed order, new spreadsheet row, or event received through a webhook.

The important part is that the trigger represents the action your business considers a successful referral. Referral Factory does not decide which CRM field or stage should count as converted in this workflow — you define that condition in n8n.

The Qualify User action supports three ways to identify the Referral Factory Lead:

Map the identifier from your trigger node to the matching field in the Referral Factory Qualify User action.

For example:

CRM Contact Email → Referral Factory Email Address

You must also select the correct Referral Factory campaign so the qualification is applied to the correct Lead.

The Lead must already exist in Referral Factory. The Qualify User action qualifies an existing Lead; it does not create a new one.

Qualification happens when the trigger condition in your n8n workflow is met and the workflow reaches the Referral Factory Qualify User action.

For example:

Lead joins Referral Factory → Deal is created in CRM → Deal later becomes Closed Won → n8n runs → Lead becomes Qualified in Referral Factory

This means you can qualify Leads at the point that makes sense for your business rather than when they first submit their details.

Once the workflow is active, n8n can process new qualifying events automatically.

The Qualify User action is used to update an existing Referral Factory Lead, not to create another Lead.

Make sure the identifier passed from n8n belongs to the correct Lead and that the correct campaign is selected.

If your source system can send the same conversion event more than once, configure your n8n trigger or workflow logic so that only the events you want to use for qualification continue to the Qualify User step.

When using email as the identifier, selecting the correct campaign is especially important when the same email address may exist across different campaigns.

Qualification can also affect rewards.

If your campaign has an active Reward Rule that is triggered when a referral qualifies, changing the Lead from Pending to Qualified causes Referral Factory to evaluate that Reward Rule.

Depending on your reward configuration, the reward can then appear as Due for review or be issued automatically if Auto Issue Rewards is enabled.

Qualifying a Lead and issuing a reward are therefore separate steps. A Lead can be Qualified while the associated reward is still waiting to be issued.

Before activating the workflow:

If the Lead is not qualified, check the n8n execution to confirm that the trigger ran successfully. Then verify the Referral Factory connection, campaign selection, identifier mapping, and that the Lead already exists in the selected campaign.