> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/integrations/marketo.md).

# Marketo

Connect Marketo to create or update supported leads, companies and opportunities from a workflow.

## Connect

An admin opens **Settings → Integrations → Marketo** and enters the custom service's **Client ID**, **Client secret** and **REST base URL** for the intended instance.

Saving requests an access token to verify credentials. It does not change records. The service user must have permission for the objects and writes your workflow uses.

## Configure a write

Choose the supported Marketo action and object. Map the lookup or identity fields, then map the fields to create or update. Use Marketo's destination field names and accepted types.

Decide how to handle an existing lead before using a create-or-update operation. Inspect the result for provider record IDs and individual errors.

## Capture a website form

[Marketo forms](/forms/marketo.md) capture a Forms 2.0 submission through the website tracker. The tracker connection and the Marketo API connection serve different purposes: detecting a form does not authorize CRM writes.

## Troubleshoot

Check the instance base URL, client credentials, service user permissions, required fields and provider limits.

Make a controlled live write and inspect the exact destination record. A successful token request or simulation does not prove an update will pass Marketo's validation.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/integrations/marketo.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.