Marketo Connector Reference | MuleSoft Documentation
# Marketo Connector Reference
Marketo is marketing automation software that aids marketing practitioners, executives, and sales reps to score, nurture, and understand leads. Marketo empowers users with marketing automation, email marketing, lead management, and revenue attribution.
## Connections
To connect to a system, whether it is a source of data or the target where you are sending data, you must create a connection with that system’s required credentials. You typically connect to different systems within a flow and can reuse each connection every time you need to connect.
This system requires the following credential information for its connections: 

Connection Name
    
Enter a connection name that will help you remember the details of this connection. You can reuse connections multiple times in a single flow, and in more than one flow, and the credentials are hidden after you create the connection. Therefore, it’s helpful to provide a name that easily identifies this connection from others.
Only you can see the connection. Other users in your Composer app must create their own connections. 

Token URL
    
The URL of the endpoint that provides the access token for Marketo. 

Client ID
    
The OAuth Client ID that you use to log in to Marketo. 

Client Secret
    
The OAuth Client Secret that you use to log into Marketo. 

REST API Endpoint
    
The base URL of your Marketo instance.
## Triggers
Each flow starts with either a _scheduler_ or a _trigger_. Schedulers are set to a default frequency of 15 minutes. Triggers, such as "each time a new record is created", are defined by you and provide multiple options related to the data in your system.
Triggers use a polling process to actively check for new updates from an external system. The polling frequency is 15 seconds.
This system provides the following trigger options: 

New Lead
    
Returns a list of new lead activities after a given datetime.
### Polling Frequency
For triggers in this connector, the **Polling Frequency** field is required. This field enables you to select how often Composer makes a request to the underling system API to look for changes to records in active flows. You can select a different polling frequency for each flow in your organization. With a shorter frequency, the flow executes more often; however, a shorter frequency consumes more API calls. For example, if you have an order management flow, you might require nearly real-time updates, which can be achieved with a 15-second polling interval (which equates to 5760 API calls per day). In contrast, if your flow updates a pricing catalog, you could poll the flow every hour (which equates to 24 API calls per day).
## Actions
After you connect to a system and define the trigger or configure a scheduler, you define the actions that the flow performs. For example, you can copy a record between different systems, such as Workday and Salesforce. The actions you can perform depend on which system you are connected to.
This system provides the following actions: 

Create Lead
    
Creates a lead to the target audience. Provide a value for **Push Lead to Market to Request**. 

Update Lead
    
Updates a lead to the target audience. Provide a value for **Push Lead to Market to Request**. 

Get/Find Lead
    
Retrieves a single lead record through its Marketo ID. 

Add Lead to List
    
Adds a Person record to a target static list. 

Update Lead Program Status
    
Changes the program member status of a lead in a target program. Provide a value for **Change Lead Program Status Request**. 

Create Custom Object
    
Create a custom object record for the target audience. Provide a value for **Sync Custom Object Request**. 

Update Custom Object
    
Update a custom object record for the target audience. Provide a value for **Sync Custom Object Request**.
## See Also
  * Mulesoft Composer: Overview
  * MuleSoft Composer: Getting Started
  * Composer Connector Reference
  * Knowledge Articles