ACTION_ID: outreach_create_prospect
NAME: Outreach: Create prospect
CATEGORY: Outreach
CREDITS: 0

Create a prospect in Outreach.io with an arbitrary attribute map,
optionally linked to an account, stage and owner. Returns the new
prospect ID.

PREREQUISITE: Outreach 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

account (dynamicDropdown, optional)
  Account. Select the account where you'd like to add the prospect.

prospect_stage (dynamicDropdown, optional)
  Prospect Stage. Select the stage prospect will be in

prospect_owner (dynamicDropdown, optional)
  Prospect owner. Add the prospect owner ID

prospect_attributes (dynamicJsonArray, required)
  Prospect attributes. Add the prospect attributes

2. OUTPUTS

status (string) — Status/Response of the request

prospect_id (number) — ID of the prospect just got created

3. HOW TO CONFIGURE

Every dropdown here is resolvable, and so is the attribute catalog
— call it to learn which attribute names Outreach accepts:

  POST .../options/account            (body: {})
  POST .../options/prospect_stage     (body: {})
  POST .../options/prospect_owner     (body: {})
  POST .../options/prospect_attributes (body: {})

Configure Action body:

{
  "inputs": {
    "account": "<account id from options>",
    "prospect_stage": "<stage id from options>",
    "prospect_owner": "<owner id from options>",
    "prospect_attributes": [
      { "name": "emails", "value": "{{person_work_email_waterfall_01ab.work_email}}" },
      { "name": "firstName", "value": "{{input.first_name}}" },
      { "name": "lastName", "value": "{{input.last_name}}" },
      { "name": "title", "value": "{{enrich_person_linkedin_profile_01cd.person_current_job_title}}" }
    ]
  }
}

Field-by-field:
  - prospect_attributes  Required. `[{name, value}]` against Outreach's
                         prospect attribute names (camelCase, e.g.
                         `firstName`, `emails`, `linkedInUrl`) — take
                         them from the options response, do not guess.
  - account / prospect_stage / prospect_owner
                         Optional relationships. Omit to leave unset.

4. KEY NOTES

- `prospect_attributes` uses Outreach's own camelCase attribute names,
  not snake_case. Resolve them via Get Action Field Options rather than
  guessing.
- This always creates. It does not check for an existing prospect — run
  `outreach_lookup_prospect` first and gate with `run_if` when
  duplicates matter.
- `prospect_id` comes back as a number and feeds
  `outreach_add_prospect_to_sequence` / `outreach_update_prospect`
  directly.
- Owner and stage IDs are workspace-specific; re-resolve them if the API
  key is rotated to a different Outreach org.

5. WHERE IT FITS IN A WORKFLOW

Pattern: outreach_lookup_prospect -> outreach_create_prospect (run_if:
prospects is empty) -> outreach_add_prospect_to_sequence. The
lookup-then-create idiom, same shape as the Salesforce one.

6. WHEN TO USE

Use outreach_create_prospect to push a newly enriched person into
Outreach as a prospect before sequencing them.

7. WHEN NOT TO USE

The prospect may already exist and you want one call
  -> action-detail/outreach_update_prospect.txt

Need to find prospects rather than create them
  -> action-detail/outreach_lookup_prospect.txt

Last updated: 2026-08-03.