ACTION_ID: close_crm_create_lead
NAME: Close CRM: Create Lead
CATEGORY: CRM
CREDITS: 0

Create a lead (the company-level record) in Close. A lead always comes
first — contacts in Close attach to a lead ID, so this is the step that
gives downstream contact actions something to hang off.

PREREQUISITE: Close CRM account connection — the user must create it in the Floqer UI
(Connections page); an agent cannot. Without it the action fails the row with
a connection / authentication error. Confirm it exists before configuring.

1. INPUTS

full_name (string, required)
  Full Name. The name of the lead — in Close this is the company name.

website_url (string, optional)
  Website URL. The website URL of the lead.

description (string, optional)
  Description. The description of the lead.

status (dynamicDropdown, optional)
  Status. The lead status to set. Resolve the allowed values through Get
  Action Field Options — Close statuses are per-organisation.

mailing_address_1 (string, optional)
  Mailing Address 1. Mailing Address 1 of the lead.

mailing_address_2 (string, optional)
  Mailing Address 2. Mailing Address 2 of the lead.

mailing_city (string, optional)
  Mailing City. Mailing City of the lead.

mailing_state (string, optional)
  Mailing State. Mailing State of the lead.

mailing_zipcode (string, optional)
  Mailing Zipcode. Mailing Zipcode of the lead.

mailing_country (string, optional)
  Mailing Country. Mailing Country of the lead.

business_address_1 (string, optional)
  Business Address 1. Business Address 1 of the lead.

business_address_2 (string, optional)
  Business Address 2. Business Address 2 of the lead.

business_city (string, optional)
  Business City. Business City of the lead.

business_state (string, optional)
  Business State. Business State of the lead.

business_zipcode (string, optional)
  Business Zipcode. Business Zipcode of the lead.

business_country (string, optional)
  Business Country. Business Country of the lead.

custom_fields (jsonArray, optional)
  Custom Fields. The custom fields of the lead, as `[{name, value}]`.

2. OUTPUTS

id (string) — ID of the Lead. The value downstream Close actions need as
their `lead_id`.
full_name (string) — Name of the Lead
display_name (string) — Display Name of the Lead
organization_id (string) — Organization ID of the Lead
status_id (string) — Status ID of the Lead
status_label (string) — Status Label of the Lead
description (string) — Description of the Lead
url (url) — URL of the Lead
html_url (url) — HTML URL of the Lead. The link a human opens in Close.
addresses (raw_array) — Addresses of the Lead
contacts (raw_array) — Contacts of the Lead
opportunities (raw_array) — Opportunities of the Lead
tasks (raw_array) — Tasks of the Lead
integration_links (raw_array) — Integration Links
custom (json) — Custom of the Lead
created_by (string) — Created By
created_by_name (string) — Created By Name
updated_by (string) — Updated By
updated_by_name (string) — Updated By Name
date_created (string) — Date Created
date_updated (string) — Date Updated

3. HOW TO CONFIGURE

`status` is a dynamic dropdown — resolve it before configuring:

  POST /api/v1/workflows/{workflow_id}/sheets/{sheet_id}/actions/{action_instance_id}/options/status
       (body: {})
       → the lead statuses defined in the connected Close organisation.

Configure Action body:

{
  "inputs": {
    "full_name": "{{input.company_name}}",
    "website_url": "{{input.company_domain}}",
    "description": "{{llm_models_01ab.generated_content}}",
    "status": "<status id from the options call>",
    "business_city": "{{floqer_company_firmographics_01cd.city}}",
    "business_country": "{{floqer_company_firmographics_01cd.country}}",
    "custom_fields": [
      { "name": "<field name from Close>", "value": "{{input.segment}}" }
    ]
  }
}

Field-by-field:
  - full_name       The company name. Required.
  - status          Pass the status ID from the options call, not the
                    label.
  - custom_fields   `[{name, value}]`. `name` must match the custom
                    field as Close defines it.

4. KEY NOTES

- This always CREATES. Run it twice on the same company and Close ends up
  with two leads — it has no duplicate detection on this path. Put a
  `close_crm_lookup_lead` in front of it, or use
  `close_crm_lookup_create_lead` which does both in one step.
- Read the lead ID off `id`, not off `organization_id`. `organization_id`
  is the Close organisation (the user's own workspace), the same value on
  every row — passing it as a `lead_id` downstream fails.
- The lead is the company; the people go on separately with
  `close_crm_add_contact`. A lead with no contacts is valid in Close but
  cannot be emailed.
- Both an address block (`mailing_*`) and a business block
  (`business_*`) exist and are independent. Fill whichever the user
  actually maps; leaving both empty is fine.

5. WHERE IT FITS IN A WORKFLOW

Pattern: enrichment -> close_crm_create_lead -> close_crm_add_contact
(lead_id: {{close_crm_create_lead_01ab.id}}), one contact action per
person found.

6. WHEN TO USE

Use close_crm_create_lead when the company is known not to be in Close
yet — typically on the empty branch after a lookup, or on a
freshly-sourced list.

7. WHEN NOT TO USE

The lead may already exist
  -> action-detail/close_crm_lookup_create_lead.txt

You only want the ID of an existing lead
  -> action-detail/close_crm_lookup_lead.txt

You are adding a person, not a company
  -> action-detail/close_crm_add_contact.txt

Last updated: 2026-08-13.