Marketo

Discover more about the Marketo connector and how to use it on the Digibee Integration Platform.

The Marketo connector integrates with Marketo’s marketing automation platform, allowing you to manage leads, campaigns, and activity data in your pipelines. You can create or update leads, add them to campaigns or lists, and get activity records to support automated lead management, campaign execution, and reporting.

Parameters

Take a look at the configuration parameters for the connector. Parameters supported by Double Braces expressions are marked with (DB).

General tab

Parameter	Description	Default value	Data type
Account	The account used by the connector. Supported type: OAuth Provider.	N/A	Account
Fail On Error	If enabled, interrupts the pipeline execution when an error occurs. If disabled, execution continues, but the "success" property will be set to false.	False	Boolean

API tab

Parameter	Description	Default value	Data type
APIs (DB)	The available APIs for this connector.	N/A	String
Path	The specific Marketo endpoint to be accessed. Based on the selected path, additional options may be available for configuring query parameters or other required settings. For details on each endpoint, refer to the Marketo API Documentation.	N/A	String
Method	The HTTP method used for the request.	N/A	String

Settings tab

Parameter	Description	Default value	Data type
Connect Timeout (ms)	Maximum time allowed for establishing a connection, in milliseconds.	30000	Integer
Read Timeout (ms)	Maximum time allowed for reading data, in milliseconds.	30000	Integer
Stop on Client Error	When enabled, stops the pipeline execution if a 4xx HTTP error occurs.	False	Boolean
Stop on Server Error	When enabled, stops the pipeline execution if a 5xx HTTP error occurs.	False	Boolean
Override Response Charset	When enabled, replaces the charset returned by the endpoint with the one specified in the Response Charset property. Otherwise, the charset from the Content-Type header is used.	True	Boolean
Response Charset	Defines the charset to be used when Override Response Charset is enabled.	UTF-8	String
Advanced Settings	Advanced configurations.	False	Boolean
Raw Mode	If activated, receives or sends a non-JSON payload.	False	Boolean
Raw Mode As Base64	When activated, shows the response as base64.	False	Boolean
Save As Local File	When activated, saves the response as a file in the local pipeline directory.	False	Boolean
Response File Name (DB)	File name or complete file path (for example, tmp/processed/file.txt). This parameter supports Double Braces, but the reference to account information is not allowed.	N/A	String
Allow Insecure Endpoints	When activated, allows unsafe calls to HTTPS endpoints to be made.	False	Boolean
Enable Retries	When activated, allows new tries in case of server errors.	False	Boolean
Number Of Retries	Maximum number of tries before giving up the call.	0	Integer
Time To Wait Between Retries	Maximum time between tries (in milliseconds).	0	Integer
Compress Body With GZIP	When activated, allows the body to be compressed with GZIP.	False	Boolean
Force HTTP 1.1	When activated, forces the request to use HTTP 1.1.	False	Boolean
Override Response Charset	When activated, overwrites the charset returned to the endpoint with the specified charset in "Response Charset" property. Otherwise, the return of the charset in the “Content-Type” header will be respected.	False	Boolean
Response Charset	Used only when "Override Response Charset" is activated; forces the use of the specified charset (Standard: UTF-8).	UTF-8	String
Disable Connection Pooling	When activated, it doesn't keep connections in a pool. Recommended for endpoints with connection reuse issues.	False	Boolean
Invalidate SSL Sessions on Every Call	When activated, invalidates SSL sessions on every call. Recommended for endpoints with SSL session reuse issues. Activating the option will make the connector single-threaded - it means that every execution will be sequential for the same REST added to the pipeline canvas.	False	Boolean

Documentation tab

Parameter	Description	Default value	Data type
Documentation	Section for documenting any necessary information about the connector configuration and business rules.	N/A	String

Usage example

Filter lead

Use the connector to filter one or more leads that match a specific filter type, such as email.

• Account: OAuth Provider account configured with Marketo credentials.

• APIs: https://066-ACM-164.mktorest.com

• Path: /rest/v1/leads.json

• Method: GET

• Query {filterType}: id

• Query {filterValues}: 63538

Example response:

{
  "status": 200,
  "statusMessage": "200",
  "body": {
    "requestId": "c85#199298cf93d",
    "result": [
      {
        "id": 63538,
        "firstName": "John",
        "lastName": "Smith",
        "email": "[email protected]",
        "updatedAt": "2025-09-08T13:38:47Z",
        "createdAt": "2025-09-06T01:42:01Z"
      }
    ],
    "success": true
  },
  "headers": {
    "Connection": "keep-alive",
    "Content-Length": "228",
    "Content-Type": "application/json;charset=UTF-8",
    "Date": "Mon, 08 Sep 2025 13:38:48 GMT",
    "Server": "nginx"
  }
}