tMarketoListOperation Standard properties

Property Type

Select the way the connection details will be set.

• Built-In: The connection details will be set locally for this component. You need to specify the values for all related connection properties manually.

• Repository: The connection details stored centrally in Repository > Metadata will be reused by this component.

  You need to click the [...] button next to it and in the pop-up Repository Content dialog box, select the connection details to be reused, and all related connection properties will be automatically filled in.

This property is not available when other connection component is selected from the Connection Component drop-down list.

Select the component whose connection details will be used to set up the connection to Marketo from the drop-down list.

Enter the API Endpoint URL of the Marketo Web Service. The API Endpoint URL can be found on the Marketo Admin > Web Services panel.

Enter the client ID for the access to the Marketo Web Service.

The client ID and client secret key can be found on the Marketo Admin > LaunchPoint panel, by clicking View Details for the service to be accessed. You can also contact Marketo Support via support@marketo.com for further information.

Enter the client secret key for the access to the Marketo Web Service.

To enter the secret key, click the [...] button next to the secret key field, and then in the pop-up dialog box enter the password between double quotes and click OK to save the settings.

Schema and Edit schema

A schema is a row description. It defines the number of fields (columns) to be processed and passed on to the next component. When you create a Spark Job, avoid the reserved word line when naming the fields.

• Built-In: You create and store the schema locally for this component only.

• Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job designs.

Click Sync columns to retrieve the schema from the previous component connected in the Job.

This component offers the advantage of the dynamic schema feature. This allows you to retrieve unknown columns from source files or to copy batches of columns from a source without mapping each column individually. For further information about dynamic schemas, see Dynamic schema.

This dynamic schema feature is designed for the purpose of retrieving unknown columns of a table and is recommended to be used for this purpose only; it is not recommended for the use of creating tables.

Note that the dynamic schema feature for this component is only supported in the REST API mode.

Operation

Select an operation to be performed from the drop-down list.

• addTo: This operation adds one or more leads to a list.

• isMemberOf: This operation verifies whether the specific leads exist in the list.

• removeFrom: This operation removes one or more leads from a list.

Add or remove many prospects

Select this check box to add multiple leads to or remove multiple leads from a list.

This check box is available only when addTo or removeFrom is selected from the Operation list.

Die on error

Select the check box to stop the execution of the Job when an error occurs.

Clear the check box to skip any rows on error and complete the process for error-free rows.

When errors are skipped, you can collect the rows on error using a Row > Reject connection if the Add or remove many prospects check box is cleared.

API Mode

Select the Marketo API mode, either REST API (default) or SOAP API.

For more information about the Marketo REST API, see http://developers.marketo.com/documentation/rest/.

For more information about the Marketo SOAP API, see http://developers.marketo.com/documentation/soap/.

Enter the timeout value (in milliseconds) for the connection to the Marketo Web Service before terminating the attempt.

Enter the maximum number of reconnect attempts to the Marketo Web Service before giving up.

Enter the time period (in milliseconds) between subsequent reconnection attempts.

tStatCatcher Statistics

Select this check box to gather the Job processing metadata at the Job level as well as at each component level.

The number of calls. This is an After variable and it returns an integer.

The error message generated by the component when an error occurs. This is an After variable and it returns a string.

Usage rule

This component is usually used as an intermediate component, and it requires an input component and an output component.