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

# Set multiple custom field values on a conversation by phone number

> Bulk variant of `/conversations/set-custom-field`. Accepts an array of `{ fieldId | fieldName, value }` items and applies them all in one call. Designed for the Make.com "Array of Collections" parameter type.
Each item identifies its field with either `fieldId` (preferred, from `/rpc/custom-fields`) or `fieldName`. Pass `value: null` on an item to clear that field.
The whole batch is validated up front: if any item references an unknown field, the request fails before any updates are written.




## OpenAPI

````yaml /openapi-make.json post /integrations/make/conversations/set-custom-fields
openapi: 3.0.3
info:
  title: SmartSend Make.com API
  version: 1.0.0
  description: >-
    Public HTTP API for the SmartSend Make.com integration. Every request is
    authenticated with the `x-organization-id` header. These are the endpoints
    Make.com (and any external automation tool) calls to send messages, manage
    conversations, tags, lists, custom fields, and more.
  contact:
    name: SmartSend Support
    email: support@smartsend.com
servers:
  - url: https://smartsend-server.otherwise.co.il
    description: Production
  - url: http://localhost:3091
    description: Local development
security:
  - organizationId: []
tags: []
paths:
  /integrations/make/conversations/set-custom-fields:
    post:
      tags:
        - Make.com Integration
      summary: Set multiple custom field values on a conversation by phone number
      description: >
        Bulk variant of `/conversations/set-custom-field`. Accepts an array of
        `{ fieldId | fieldName, value }` items and applies them all in one call.
        Designed for the Make.com "Array of Collections" parameter type.

        Each item identifies its field with either `fieldId` (preferred, from
        `/rpc/custom-fields`) or `fieldName`. Pass `value: null` on an item to
        clear that field.

        The whole batch is validated up front: if any item references an unknown
        field, the request fails before any updates are written.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - phoneNumber
                - fields
              properties:
                phoneNumber:
                  type: string
                  description: Phone number in any format (972..., 05..., +972...)
                fields:
                  type: array
                  minItems: 1
                  description: One or more field updates to apply
                  items:
                    type: object
                    properties:
                      fieldId:
                        type: string
                        description: ID of the custom field (from /rpc/custom-fields)
                      fieldName:
                        type: string
                        description: Name of the custom field (alternative to fieldId)
                      value:
                        type: string
                        nullable: true
                        description: Value to set. Pass null to clear the field.
      responses:
        '200':
          description: Custom fields updated successfully
      security:
        - organizationId: []
components:
  securitySchemes:
    organizationId:
      type: apiKey
      in: header
      name: x-organization-id
      description: Your SmartSend Organization ID. Required on every request.

````