About the Marketo category

anon99371720 · September 21, 2022, 11:16am

Add topics about this connector package here.
Always check the ‘How to use the Alumio connector packages’ topic.

Extra information

System documentation: Endpoint Reference - Marketo Developers

Connector package documentation

1. Setting up the Marketo HTTP Client

1.1 Steps

In the Alumio Dashboard, go to Clients > HTTPS Client. Create a new HTTP Client and select the Marketo HTTP Client as the prototype of the HTTP Client.
Fill in the Account ID, Client ID, and Client Secret.
Press “Grant Access to Marketo”.
The Key will show up and you can save the Client for further use.

2. Subscribing to Entities from Marketo

2.1 Steps

Go to Connections → Incoming, create a new incoming configuration, and select the Marketo Subscriber as the subscriber.
Select the entity you want to subscribe to from Marketo.
(Optional) Add any specific request parameters needed to subscribe to the entity.
You can add a transformer to manipulate the request parameters into anything you need if necessary.
Select the Marketo HTTP Client to use.

2.2 General Concept

We follow the Marketo documentation on building this connector, so you can easily use the connector based on the Marketo API Reference.

Entity

This is the entity you want to subscribe to from Marketo. Please refer to the entities in Management APIs from the Marketo API Reference page.

Request Parameters

These are the parameters you can provide to get the needed entities based on the Marketo API Reference documents. Please look at the example below on how to fill Request Parameters when subscribing to “Get Static List by id”.

“Path” is the path parameter of the URL. For example the {id}.
“Query” is a defined set of parameters attached to the end of a URL.
Example: www.url.com?type=true&start=0

To understand Marketo’s definition of the endpoint, we can consult their documentation.

Alumio will send an API request to Marketo with the URL /rest/asset/v1/staticList/1009.json

Input Transformer

Any transformers set here will be executed before the Request Parameters are loaded. This means that you can add any transformer to provide and transform the request parameters into anything you need, either as path parameters and/or as query parameters of an entity.

HTTP Client

This is the HTTP Client configuration you will use to access Marketo.

3. Publishing Entity to Marketo

3.1 Steps

Go to Connections → Outgoing, create a new outgoing configuration, and select the Marketo Publisher as the publisher.
Select the action that you want the publisher to do with the data.
Select the Marketo entity where you want the data to be published.
You can optionally add any query parameters to the request.
You can add transformers to manipulate the data into anything you need before submitting it to Marketo.
Select the Marketo HTTP Client to use.

3.2 General Concept

Like the subscriber, the publisher has similar methods on how to use it. The difference is the payload that will be submitted by the publisher originating from the data (from routes, from transformers in the outgoing configuration), though you can also add or modify the payload using the Entity Transformer.

Action

Currently, we support Post and Delete Methods.

Entity

We support publishing to most Marketo endpoints, but not with publishing Bulk End Points for now. Please refer to the entities from the Marketo API Reference page. Based on the documentation, some endpoints may need one or more path parameters.

You can put the query id you want to send to Marketo into a payload key in the data, as follows:

“Path” is the path parameter of the URL. For example the {id}.
“Query” is a defined set of parameters attached to the end of a URL.
Example: www.url.com?type=true&start=0
“Payload” is the data contained within a request.

Alumio will send an API request to Marketo to add the Lead id 22490 into a listId 1575.

The request to Marketo will be sent with URL /rest/v1/lists/1575/leads.json?id= 22490