> ## Documentation Index
> Fetch the complete documentation index at: https://docs.morf.health/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Create Or Update Contact

> Documentation for the Create Or Update Contact action for Zoho

![images/zoho.svg](https://mintcdn.com/morfhealth/EU2WCxuXGIUQcziR/images/zoho.svg?fit=max\&auto=format\&n=EU2WCxuXGIUQcziR\&q=85\&s=28ee7916825be920945756f3894db556)

## Getting Started

Easily connect Morf to your Zoho account and automate your Zoho workflows, such as syncing contacts, managing deals, and more.

## Get access to the API

To connect Morf with Zoho, you need to create a Zoho API client and gather a few credentials. Follow these steps:

1. Go to the [Zoho Developer Console](https://api-console.zoho.com/).
2. Click **GET STARTED** if prompted.

   ![Get Started](https://mintcdn.com/morfhealth/VPKyBRVuRAgQM-CM/images/zoho_get_started.png?fit=max\&auto=format\&n=VPKyBRVuRAgQM-CM\&q=85\&s=d2d2a89e61fb0f6e080ed6fa30ac9685)
3. Under **Self Client**, click **CREATE NOW**.

   ![Choose a Client Type](https://mintcdn.com/morfhealth/VPKyBRVuRAgQM-CM/images/zoho_choose_a_client_type.png?fit=max\&auto=format\&n=VPKyBRVuRAgQM-CM\&q=85\&s=fc1d589ecf71a6a1f9f205985f4c6eba)
4. Fill in the required details. Once created, go to the **Client Secret** tab and copy the **Client ID** and **Client Secret**. You will need these to configure the Zoho integration in Morf.
5. Visit the [Zoho CRM homepage](https://crm.zoho.com) and retrieve your **Organization ID**:

   * Click your profile icon in the top-right corner.
   * Hover to reveal your Organization ID.

   ![Find Organization ID](https://mintcdn.com/morfhealth/VPKyBRVuRAgQM-CM/images/zoho_org_id.png?fit=max\&auto=format\&n=VPKyBRVuRAgQM-CM\&q=85\&s=3ca3229f43a71e03eff203e8def7b70d)

## Configure Zoho in Morf

1. In the Morf Dashboard, navigate to **Integrations** > **+ Connect Integration**.
2. Enter your **Client ID**, **Client Secret**, and **Organization ID**.

# Parameters

**Action** `Parameters`

**parameters**

**ID** `string`

This field maps to the destination API `ID` field.

**Email** `string` *required*

`PII`
This field maps to the destination API `Email` field.

**First Name** `string`

`PII`
This field maps to the destination API `First_Name` field.

**Last Name** `string` *required*

`PII`
This field maps to the destination API `Last_Name` field.

**Account Name** `string`

This field maps to the destination API `Account_Name` field.

**Lead Source** `string`

This field maps to the destination API `Lead_Source` field.

**Date of Birth** `values.v1.Date`

`PII`
This field maps to the destination API `Date_of_Birth` field.

**Phone** `string`

`PII`
This field maps to the destination API `Phone` field.

**Mailing Street** `string`

`PII`
This field maps to the destination API `Mailing_Street` field.

**Mailing City** `string`

`PII`
This field maps to the destination API `Mailing_City` field.

**Mailing State** `string`

`PII`
This field maps to the destination API `Mailing_State` field.

**Mailing Zip** `string`

`PII`
This field maps to the destination API `Mailing_Zip` field.

**Mailing Country** `string`

`PII`
This field maps to the destination API `Mailing_Country` field.

**Fields** `Map\<Contact Field,dynamic (any)\>`

This field maps to the destination API `<Contact_Field>` field.

```json Result Object Example theme={null}
{
  "$result_object_key": {
    "account_name": "Acme Corp",
    "additional_fields": {
      "Custom_Field_1": "Value1",
      "Custom_Field_2": "Value2"
    },
    "date_of_birth": "1990-01-01",
    "email": "jane.doe@example.com",
    "first_name": "Jane",
    "id": "6325355123451030002",
    "last_name": "Doe",
    "lead_source": "Website",
    "mailing_city": "San Francisco",
    "mailing_country": "USA",
    "mailing_state": "CA",
    "mailing_street": "123 Main St",
    "mailing_zip": "94105",
    "phone": "+1234567890"
  }
}
```

```json Result Object Description theme={null}
{
  "$result_object_key": {
    "account_name": "The name of the account associated with the contact.",
    "additional_fields": "Additional fields for the contact.",
    "date_of_birth": "The contact's date of birth.",
    "email": "The contact's email address.",
    "first_name": "The contact's first name.",
    "id": "The contact's unique identifier.",
    "last_name": "The contact's last name.",
    "lead_source": "The source from which the lead originated.",
    "mailing_city": "The city for mailing.",
    "mailing_country": "The country for mailing.",
    "mailing_state": "The state for mailing.",
    "mailing_street": "The street address for mailing.",
    "mailing_zip": "The ZIP code for mailing.",
    "phone": "The contact's phone number."
  }
}
```

### Result Object Field Details

You can use the result of the action's data as inputs to downstream workflow actions.

Each fetch action requires an object name, which nests the action's result data inside the downstream data context in the workflow. See [Passing Data Between Actions](https://docs.morf.health/docs/knowledge_base/passing_data_between_actions.md) for how to set it and reference the result from downstream nodes.

Here we demonstrate how to refer to this data using the prefix `$result_object_key`.

**Contact** `Fetch Action Response Object`

**fields**

**id** `string` *required*

`ID` The contact's unique identifier.

```json CEL theme={null}
$result_object_key.id
```

```json Example theme={null}
"6325355123451030002"
```

**email** `string`

`PII` The contact's email address.

```json CEL theme={null}
$result_object_key.email
```

```json Example theme={null}
"jane.doe@example.com"
```

**first\_name** `string`

`PII` The contact's first name.

```json CEL theme={null}
$result_object_key.first_name
```

```json Example theme={null}
"Jane"
```

**last\_name** `string`

`PII` The contact's last name.

```json CEL theme={null}
$result_object_key.last_name
```

```json Example theme={null}
"Doe"
```

**account\_name** `string`

The name of the account associated with the contact.

```json CEL theme={null}
$result_object_key.account_name
```

```json Example theme={null}
"Acme Corp"
```

**lead\_source** `string`

The source from which the lead originated.

```json CEL theme={null}
$result_object_key.lead_source
```

```json Example theme={null}
"Website"
```

**date\_of\_birth** `values.v1.Date`

`PII` The contact's date of birth.

```json CEL theme={null}
$result_object_key.date_of_birth
```

```json Example theme={null}
"1990-01-01"
```

**phone** `string`

`PII` The contact's phone number.

```json CEL theme={null}
$result_object_key.phone
```

```json Example theme={null}
"+1234567890"
```

**mailing\_street** `string`

`PII` The street address for mailing.

```json CEL theme={null}
$result_object_key.mailing_street
```

```json Example theme={null}
"123 Main St"
```

**mailing\_city** `string`

`PII` The city for mailing.

```json CEL theme={null}
$result_object_key.mailing_city
```

```json Example theme={null}
"San Francisco"
```

**mailing\_state** `string`

`PII` The state for mailing.

```json CEL theme={null}
$result_object_key.mailing_state
```

```json Example theme={null}
"CA"
```

**mailing\_zip** `string`

`PII` The ZIP code for mailing.

```json CEL theme={null}
$result_object_key.mailing_zip
```

```json Example theme={null}
"94105"
```

**mailing\_country** `string`

The country for mailing.

```json CEL theme={null}
$result_object_key.mailing_country
```

```json Example theme={null}
"USA"
```

**additional\_fields** `object` *required*

Additional fields for the contact.

```json CEL theme={null}
$result_object_key.additional_fields
```

```json Example theme={null}
{
"Custom_Field_1": "Value1",
"Custom_Field_2": "Value2"
}
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.