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

Configure the connector using the parameters below. Fields that support Double Braces expressions are marked in the Supports DB column.

General

Parameter	Description	Type	Supports DB	Default
Alias	Name (alias) for this connector’s output, allowing you to reference it later in the flow using Double Braces expressions. Learn more.	String	❌	marketo-1
Account	The account used by the connector. Supported type: OAuth Provider.	Account	❌	N/A
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.	Boolean	❌	False

API

Parameter	Description	Type	Supports DB	Default
BaseURL	The available APIs for this connector.	String	✅	N/A
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.	String	❌	N/A
Method	The HTTP method used for the request.	String	❌	N/A

Settings

Parameter	Description	Type	Supports DB	Default
Connect Timeout (ms)	Maximum time allowed for establishing a connection, in milliseconds.	Integer	❌	30000
Read Timeout (ms)	Maximum time allowed for reading data, in milliseconds.	Integer	❌	30000
Stop on Client Error	When enabled, stops the pipeline execution if a 4xx HTTP error occurs.	Boolean	❌	False
Stop on Server Error	When enabled, stops the pipeline execution if a 5xx HTTP error occurs.	Boolean	❌	False
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.	Boolean	❌	True
Response Charset	Defines the charset to be used when Override Response Charset is enabled.	String	❌	UTF-8
Advanced Settings	Advanced configurations.	Boolean	❌	False
Raw Mode	If activated, receives or sends a non-JSON payload.	Boolean	❌	False
Raw Mode As Base64	When activated, shows the response as base64.	Boolean	❌	False
Save As Local File	When activated, saves the response as a file in the local pipeline directory.	Boolean	❌	False
Response File Name	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.	String	✅	N/A
Allow Insecure Endpoints	When activated, allows unsafe calls to HTTPS endpoints to be made.	Boolean	❌	False
Enable Retries	When activated, allows new tries in case of server errors.	Boolean	❌	False
Number Of Retries	Maximum number of tries before giving up the call.	Integer	❌	0
Time To Wait Between Retries	Maximum time between tries (in milliseconds).	Integer	❌	0
Compress Body With GZIP	When activated, allows the body to be compressed with GZIP.	Boolean	❌	False
Force HTTP 1.1	When activated, forces the request to use HTTP 1.1.	Boolean	❌	False
Disable Connection Pooling	When activated, it doesn't keep connections in a pool. Recommended for endpoints with connection reuse issues.	Boolean	❌	False
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.	Boolean	❌	False

Documentation

Parameter	Description	Type	Supports DB	Default
Documentation	Section for documenting any necessary information about the connector configuration and business rules.	String	❌	N/A

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"
  }
}