> For the complete documentation index, see [llms.txt](https://docs.planetcrust.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.planetcrust.com/human-connections/marketo/marketo/action-add-lead-to-list.md).

# Action: Add Lead to List

<p align="center"><a class="button primary" data-icon="circle-caret-right">Try @Human</a><a class="button primary" data-icon="check">Buy @Human Subscriptions</a><a class="button primary" data-icon="comments">Join @Human Community</a></p>

<figure><img src="/files/ZI9P18zdQnNcd8HbFnrL" alt="" width="375"><figcaption></figcaption></figure>

<p align="center">The Add Lead to List action includes a contact or lead in a specific marketing list for targeted campaigns or segmentation.</p>

{% embed url="<https://www.youtube.com/watch?v=CyuUuaBSZzA>" %}

#### Example User Story

I want to nurture new event registrants with a welcome email series, so I’ll use Marketo’s Add Lead to List action to include them in our "New Leads - Webinar" campaign list.

#### Fields

| Field Name  | Field Type | Required |
| ----------- | ---------- | -------- |
| listId      | Integer    | Yes      |
| leadId      | Integer    | Yes      |
| accessToken | String     | Yes      |

### Related Connections

[Marketo](/human-connections/marketo/marketo.md)

### Related Automations

Example link

### Code (Apache v2.0): Operation

```
{
  "handle": "add-lead-to-list",
  "state": "inDev",
  "meta": {
    "short": "Add Lead to List",
    "description": "Adds a lead to a specified list in Marketo."
  },
  "input": [
    {
      "name": "listId",
      "type": "Integer",
      "required": true,
      "meta": {
        "description": "The ID of the list to which the lead will be added."
      }
    },
    {
      "name": "leadId",
      "type": "Integer",
      "required": true,
      "meta": {
        "description": "The ID of the lead to be added to the list."
      }
    }
  ],
  "output": [
    {
      "name": "success",
      "type": "Boolean",
      "selector": ["success"],
      "meta": {
        "description": "Indicates whether the operation was successful."
      }
    },
    {
      "name": "status",
      "type": "String",
      "selector": ["status"],
      "meta": {
        "description": "The status message returned by Marketo."
      }
    }
  ],
  "steps": [
    {
      "type": "http",
      "http": {
        "method": "POST",
        "path": "/rest/v1/lists/{{listId}}/leads.json",
        "headers": {
          "Content-Type": "application/json"
        },
        "bodyTemplate": {
          "value": "{\"input\":[{\"id\":{{leadId}}}]}",
          "placeholders": [
            {
              "name": "listId",
              "type": "Integer",
              "description": "The ID of the list.",
              "required": true
            },
            {
              "name": "leadId",
              "type": "Integer",
              "description": "The ID of the lead.",
              "required": true
            },
            {
              "name": "accessToken",
              "type": "String",
              "description": "The access token for Marketo API authentication.",
              "required": true
            }
          ]
        }
      }
    }
  ]
}

```

<p align="center"><a class="button primary" data-icon="square-caret-right">Try @Human</a><a class="button primary" data-icon="check">Buy @Human Subscription</a><a class="button primary" data-icon="comments">Join @Human Community</a></p>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.planetcrust.com/human-connections/marketo/marketo/action-add-lead-to-list.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.