Built-in tool

Find People at Company

Find one or several decision-makers at one company from your ordered list of job titles (such as founder, CEO or head of sales), using AI research across LinkedIn and the web.

4 creditsNo API key needed

Endpoint

Parameters

NameTypeRequiredNote
companyDomainstring · requiredstringrequired

The company to find people at.

Example: stripe.com

companyLinkedinUrlstring · optionalstringoptional

Optional. When set, the node reads the company's LinkedIn employee list first and researches only the titles it cannot fill from there. Leave empty to research from the domain alone. A URL that turns out not to match this company is ignored and the run falls back to domain-only research.

Example: https://www.linkedin.com/company/stripe

companyNamestring · optionalstringoptional

Optional. Helps disambiguate search results when the domain alone is ambiguous.

Example: Stripe

jobTitlesarray · requiredarrayrequired

One title per row, most important first. Order is the priority order: it decides which title a person is filed under when they match more than one, and which titles get searched first if a run is up against its research budget. Matched loosely — "Head of Ecommerce" also matches "Ecommerce Lead" or "Director of Ecommerce". Up to 30.

Example: Head of Ecommerce

limitnumber · optionalnumberoptional

Maximum people in Priority mode (default 10, up to 100). All matches uses the research ceiling of 100 instead.

Default: 10

Example: 10

jobTitlesExcludearray · optionalarrayoptional

Exclude these titles and equivalent roles. For L&D-only work exclude Machine Learning and AI Research.

searchModestring · optionalstringoptional

Priority uses Limit. All matches researches beyond one person per title, up to 100 per company within the research budget. It cannot guarantee a complete employee census.

One of: priority (Priority), all_matches (All matches)

Default: priority

existingRecordModestring · optionalstringoptional

Keep existing preserves existing People across the whole Object and adds only new People to the destination List. It does not change Object settings.

One of: object_settings (Use Object settings), keep (Keep existing)

Default: object_settings

Response schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "elements",
    "total",
    "totalElements",
    "promptUsed",
    "fellBackToWebResearch",
    "employeeSearchesUsed",
    "webSearchesUsed",
    "budgetExhausted",
    "limit",
    "totalBeforeLimit",
    "truncatedByLimit",
    "searchMode",
    "researchLimitReached",
    "excludedPeopleCount",
    "unmatchedJobTitles"
  ],
  "properties": {
    "meta": {
      "type": "object",
      "properties": {
        "actualCreditCost": {
          "type": "number"
        },
        "modelUsageCredits": {
          "type": "number"
        }
      },
      "additionalProperties": false
    },
    "limit": {
      "type": "number"
    },
    "total": {
      "type": "number"
    },
    "elements": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "first_name",
          "last_name",
          "linkedin_profile_url",
          "job_title"
        ],
        "properties": {
          "job_title": {
            "type": "string"
          },
          "last_name": {
            "type": "string"
          },
          "first_name": {
            "type": "string"
          },
          "linkedin_profile_url": {
            "type": "string"
          }
        },
        "additionalProperties": false
      }
    },
    "promptUsed": {
      "enum": [
        "A",
        "B"
      ],
      "type": "string"
    },
    "searchMode": {
      "enum": [
        "priority",
        "all_matches"
      ],
      "type": "string"
    },
    "totalElements": {
      "type": "number"
    },
    "budgetExhausted": {
      "type": "boolean"
    },
    "webSearchesUsed": {
      "type": "number"
    },
    "totalBeforeLimit": {
      "type": "number"
    },
    "truncatedByLimit": {
      "type": "boolean"
    },
    "unmatchedJobTitles": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "excludedPeopleCount": {
      "type": "integer",
      "minimum": 0
    },
    "employeeSearchesUsed": {
      "type": "number"
    },
    "researchLimitReached": {
      "type": "boolean",
      "description": "The 100-person research ceiling was reached; further matching people may exist."
    },
    "fellBackToWebResearch": {
      "type": "boolean"
    }
  },
  "additionalProperties": false
}

Get started

How to use this tool

  1. Connect your AI

    Add Connie to ChatGPT, Claude or Slack once, and this tool comes with it. There’s no API key or account to set up.

  2. Ask for the outcome

    Describe what you need in plain words. Your AI runs this tool when the job calls for it, along with any others it needs.

  3. Make it a workflow

    Add it as a step in a workflow that runs the same way every time, on a schedule or when something happens.

  4. Stay in control

    Choose whether it runs on its own or asks first. When it asks, you see an Allow or Deny card before any credits are spent.