Skip to content
telipot
telipot
Join the waitlistSign in

Save a person as a contact in the account, returning its ID.

Use the create a contact endpoint to add a new contact to your team's Apollo account.

Job people.contacts.create

Your AI asks

choose input values first
telipot inspect apollo.people.contacts.create

Provider's rate

Free
Inspect· before choosing inputs

apollo.people.contacts.create

FreeYour plan

Whose account it uses

1The person asking
not needed
2Your company’s Apollo plan
Selected identity for this example
3Our account
not used

Choose inputs

first_name · First name of the contact.

last_name · Last name of the contact.

No complete example input is recorded. Inspect reads the schema; it does not run the task.

What it costs

Free

no charge from the provider

For developers · inspect first

Read the schema and choose input values

telipot inspect apollo.people.contacts.create

No complete example input is recorded. Read the field notes below before building the call.

first_name

string

First name of the contact.

last_name

string

Last name of the contact.

organization_name

string

Name of the contact's employer.

title

string

Current job title.

account_id

string

Apollo ID of the account the contact belongs to.

email

string

Email address of the contact.

website_url

string

Corporate website URL.

label_names

array

Names of the lists the contact belongs to.

contact_stage_id

string

Apollo ID of the contact stage.

present_raw_address

string

Personal location of the contact.

direct_phone

string

Primary phone number.

corporate_phone

string

Work or office phone number.

mobile_phone

string

Mobile phone number.

home_phone

string

Home phone number.

other_phone

string

Alternative phone number.

typed_custom_fields

object

Values for the account's custom fields, keyed by the custom field's ID; custom fields are unique to each account.

run_dedupe

boolean · default false

Set true to match an existing contact and overwrite it with the values sent instead of always creating a new one; the returned id then belongs to the existing contact.

contact

object

Full output schema · JSONNested fields and constraints

Output JSON Schema

{
  "type": "object",
  "properties": {
    "contact": {
      "type": "object",
      "properties": {
        "id": {
          "type": "string"
        },
        "first_name": {
          "type": "string"
        },
        "last_name": {
          "type": "string"
        },
        "name": {
          "type": "string"
        },
        "title": {
          "type": "string"
        },
        "email": {
          "type": "string"
        },
        "email_status": {
          "type": "string"
        },
        "linkedin_url": {
          "type": [
            "string",
            "null"
          ]
        },
        "organization_name": {
          "type": "string"
        },
        "organization_id": {
          "type": "string"
        },
        "account_id": {
          "type": "string"
        },
        "contact_stage_id": {
          "type": "string"
        },
        "owner_id": {
          "type": "string"
        },
        "created_at": {
          "type": "string"
        },
        "updated_at": {
          "type": "string"
        },
        "label_ids": {
          "type": "array",
          "items": {
            "type": "string"
          }
        }
      }
    }
  }
}

A real answer

No example captured yet: one is recorded when telipot catalog verify passes.