--- title: "Creating Only Contacts in Salesforce" source_url: https://help.chilipiper.com/hc/en-us/articles/40519834244115-Creating-Only-Contacts-in-Salesforce article_id: 40519834244115 updated_at: 2026-09-17T18:02:13Z --- ## Who can use this feature? Available on All Products or Routing & Scheduling Available to Only Admins [Billing Center](https://fire.chilipiper.com/fire/admin/billing/overview) [Get a Demo](https://www.chilipiper.com/request-demo?utm_source=zendesk&utm_medium=help-center&utm_campaign=chili-hub) By default, Chili Piper creates a Lead in Salesforce if the prospect does not already exist. Chili Piper can also create a Contact instead when an Account already matches. These settings are configured per product: in ChiliCal under [**CRM Actions**](https://help.chilipiper.com/hc/en-us/articles/29767375437203-CRM-Actions-in-ChiliCal), in [**Concierge**](https://help.chilipiper.com/hc/en-us/articles/28522554434323-Creating-a-Concierge-Router-in-Demand-Conversion-Platform#h_01HVRACA5CH8BYFTP8ANPM1PY5:~:text=Salesforce%20Nodes-,Create%20or%20Update%20Record,-After%20the%20prospect) with the **Create or Update Record** node, and in [**Chat**](https://help.chilipiper.com/hc/en-us/articles/27532198601107-Creating-a-Journey-in-Chat#h_01HS8ZMG87QCYAMA8V1FMXAT1V:~:text=Chat%22%20Slack%20notification.-,Update%20or%20Create%20Salesforce%20Record%20Node,-After%20collecting%20an) with the **Update or Create Salesforce Record** node. Some companies never want a Lead created, only a Contact. There are four ways to achieve this with Chili Piper. Each has different requirements and trade-offs, so this article describes all four and helps you choose between them. * * * #### Table of Contents * Choosing a method * Method 1: Zapier or other middleware * Method 2: Salesforce package with an auto-conversion Flow * Method 3: Distro Lead Conversion node * Method 4: Orchestrator creates the Contact directly * Need help choosing? * * * ## Choosing a method Start by deciding which outcome you need: * **No Lead at any point.** The prospect must go straight to a Contact; * **A temporary Lead is acceptable.** Chili Piper creates a Lead, and an automated process converts it to a Contact right away. Method | Creates a Lead first? | Needs middleware? | Requires | Considerations ---|---|---|---|--- 1\. Zapier or other middleware | No, once the CRM actions are set to create only the Event | Yes | A Zapier account (or similar tool) connected to Chili Piper and Salesforce | External dependency. Lead creation must be turned off in the Chili Piper CRM actions, or the Lead removed in Salesforce, to avoid duplicates 2\. Salesforce package with an auto-conversion Flow | Yes, converted by a Flow | No | A package installed on request from Chili Piper | Older approach. Lead-to-Account matching is simpler than in Distro 3\. Distro Lead Conversion node | Yes, converted by Distro | No | At least one Distro license | Advanced Lead-to-Account matching and the most configuration options 4\. Orchestrator creates the Contact directly | No | No | Orchestrator | No Lead at any point. Validate Account matching for prospects new to Salesforce. Usually two Flows > **Note:** For new setups, prefer Orchestrator or Distro over middleware. Orchestrator is the most direct route because no Lead is created at any point and no external tool is involved. Validate its Account-matching behavior against your requirements before rolling it out widely. When a temporary Lead is acceptable, Distro offers the most flexible matching without middleware. * * * ## Method 1: Zapier or other middleware This is the original approach. A Zap (or an equivalent automation in another tool) starts from Chili Piper's **New Meeting** trigger and creates the Contact, an Account when needed, and the Event in Salesforce. It depends on an external tool: if the middleware is delayed or fails, the Salesforce records are delayed or missing too. Here are the steps to create this in Zapier: 1. Make a new Zap and include Chili Piper's "New Meeting" as the Trigger. Check out Available Fields [Here](https://help.chilipiper.com/hc/en-us/articles/35907405102227-Zapier-Available-Fields-Demand-Conversion-Platform). 2. (optional) Create a Filter if you only want your Zap to run for specific "Event Types", "Event Meeting Type", or other parameters. 3. Select "Salesforce" as your Action. 4. **[Add an Action Step]** Select "Search for Salesforce Account" (_optional_) * Field to Search By: "Account Name" * Search Value: "Prospect Company" * Select "Create Salesforce Account if it doesn't exist yet?" * Account Name: "Prospect Company" 5. **[Add an Action Step]** Select "Create Contact" ![](https://help.chilipiper.com/hc/article_attachments/40519826725651) 6. Map Fields from Chili Piper * Last Name = Prospect Last Name * First Name = Prospect First Name * Email = Prospect Email * Mobile Phone = Prospect Mobile Phone * Meeting Type = Event Type * Lead Source = "Chili Piper" (optional) * Account = the Account ID returned by the "Search for Salesforce Account" step, so the Contact is linked to the Account (if you added that step) 7. **[Add an Action Step]** Find a Contact * Field to Search By = Email * Search Value = Prospect Email 8. **[Add an Action Step]** Select "Create Event" * Booked By = "Use a Custom Value (advanced)" -> Booker Salesforce ID * Meeting Type = "Use a Custom Value (advanced)" -> Event Type * Assigned To = "Use a Custom Value (advanced)" -> Assignee Salesforce ID * Event Queue = "Use a Custom Value (advanced)" -> Event Queue * Subject = "Use a Custom Value (advanced)" -> Event Title * Duration = Event Duration 9. That is it. Turn the Zap on and give it a test. > **Note:** Chili Piper also creates a Lead on its own when a meeting is booked, unless the CRM actions for that product are set to create only the Event. If a Lead is still created, use a Salesforce Flow to delete it or merge it with the new Contact so you do not end up with duplicates. Contact Chili Piper Support or your Chili Piper rep if you require assistance in setting this up. * * * ## Method 2: Salesforce package with an auto-conversion Flow Chili Piper creates the Lead as usual. A Salesforce package provided by Chili Piper adds a Flow that matches the Lead to an Account, converts the Lead to a Contact, and optionally creates an Opportunity. The conversion runs inside Salesforce, so no middleware is involved. Keep in mind: * A Lead exists in Salesforce until the Flow converts it; * The Lead-to-Account matching is simpler than the matching available in Distro (Method 3); * This is an older approach. It remains available on request for teams that cannot use Distro or Orchestrator. To request the package, contact Chili Piper Support or your Chili Piper rep. * * * ## Method 3: Distro Lead Conversion node Chili Piper creates the Lead as usual, and a Distro router converts it to a Contact. The [**Lead Conversion node**](https://help.chilipiper.com/hc/en-us/articles/25740616368531-Distro-Router-Lead-Conversion-Node) uses Distro's Lead-to-Account matching settings to attach the Contact to an existing Account, can always create a new Account instead, and can optionally create an Opportunity. Requirements: * At least one Distro license; * A Lead exists in Salesforce until the router converts it. High-level setup: 1. Keep Lead creation enabled in the Chili Piper CRM actions for your product; 2. [Create a Distro router](https://help.chilipiper.com/hc/en-us/articles/23304655920403-Creating-a-Distro-Router) with a Lead trigger and an entry rule that matches the Leads Chili Piper creates; 3. Add the **Lead Conversion** node and configure the Converted Status, whether to create an Opportunity, and whether to always create an Account; 4. Place any Field Update, SLA, or Assign and Update Ownership nodes before the Lead Conversion node. Conversion ends the flow, because the Lead no longer exists afterwards. > **Note:** If the automated conversion fails, confirm that the same Lead can be converted manually in Salesforce. Salesforce validation rules and required fields apply to automated conversions too. * * * ## Method 4: Orchestrator creates the Contact directly [**Orchestrator**](https://help.chilipiper.com/hc/en-us/articles/53535895896467-What-is-Orchestrator) listens for Chili Piper events and writes to Salesforce, so it can create the Contact itself. No Lead is created at any point, and no middleware is involved. The common pattern with Concierge is: * In the Concierge Flow, keep only the **Create Event** Salesforce node and remove **Create or Update Record** , so Chili Piper does not create a Lead or a Contact; * An Orchestrator Flow with the **Meeting Booked** trigger checks whether the guest already exists as a Contact, then creates the Contact, and an Account when needed; * Optionally, a second Orchestrator Flow with the **Meeting Not Scheduled** trigger does the same for prospects who submit the form but do not book. The **Meeting Booked** trigger fires for meetings from any Chili Piper product, so the same Flow also covers ChiliCal, Chat, and Handoff bookings as long as that product's CRM actions do not create a Lead or a Contact. The **Meeting Not Scheduled** trigger is available only for forms tied to Concierge Flows. > **Note:** Because Concierge creates only the Event, the first Event write can run before the Contact exists. Chili Piper retries Salesforce Event creation automatically, starting a few minutes after booking and continuing for about two days, so the Event is created on a later attempt once Orchestrator has created the Contact. If the Contact is created after the retries end, retry the Salesforce action from the meeting's activity in Chili Piper. High-level setup: 1. In the Concierge Flow, remove the **Create or Update Record** node and keep **Create Event** ; 2. In Orchestrator, create a Flow and set **Flow will Start** to **Meeting Booked**. Add a Condition on Trigger to scope it to the right Concierge Flow if needed (see [Trigger nodes](https://help.chilipiper.com/hc/en-us/articles/53506115976083-How-do-I-use-Trigger-nodes-in-Orchestrator)); 3. Add a [Matching node](https://help.chilipiper.com/hc/en-us/articles/53507381639955-How-do-I-use-the-Matching-node-in-Orchestrator) on the guest email to find an existing Salesforce Contact and Account; 4. Add a [Condition node](https://help.chilipiper.com/hc/en-us/articles/53527243403795-How-do-I-use-the-Condition-node-in-Orchestrator) that branches on whether a Contact was found; 5. On the not-found branch, add a [Create Record node](https://help.chilipiper.com/hc/en-us/articles/53533269333907-How-do-I-use-the-Create-Record-node-in-Orchestrator) for the Contact, and another for the Account when a new Account is needed. On the found branch, use an [Update Record node](https://help.chilipiper.com/hc/en-us/articles/53533286291859-How-do-I-use-the-Update-Record-node-in-Orchestrator) if the existing Contact should be updated; 6. If prospects who do not book also need a Contact, build a second Flow with the **Meeting Not Scheduled** trigger; 7. Test the scenarios that matter to you: existing Contact, new Contact, existing Account, new Account, meeting booked, and meeting not booked. Validate these points before rolling it out: * **Account matching.** The Matching node finds records by the guest's email. When the person is new to Salesforce, decide how the Flow determines whether the Contact belongs to an existing Account or needs a new one, and confirm that logic against your data; * **Duplicate Contacts.** Always check for an existing Contact before the Create Record node; * **Two Flows.** Meeting Booked and Meeting Not Scheduled are separate triggers, so covering both outcomes takes two Flows. Meeting Not Scheduled works only with forms tied to Concierge Flows; * **AI credits.** Parsing form data in Orchestrator consumes AI credits. The usage is small for most teams; confirm it for high-volume forms; * **Licensing.** Orchestrator is a separate Chili Piper product. * * * ## Need help choosing? Share the following with Chili Piper Support or your Chili Piper rep, and we will help you pick the method that fits: * Whether a temporary Lead is acceptable, or Leads must never exist; * How Accounts should be matched (email domain, company name, or custom rules); * Whether an Opportunity needs to be created as part of the process; * Which Chili Piper product books the meeting (Concierge, ChiliCal, Chat, or Handoff); * The expected volume of form submissions.