Creating or editing an endpoint for Marketo
Endpoints provide the configuration information that the Studio and the Integration Appliance use to connect to Marketo platform. Marketo connector supports only OAuth authentication mechanism so as to authorize users to perform operations. Marketo connector only supports HTTPS connection.
Selecting or editing a Marketo endpoint
- In the Create Endpoint or Edit Endpoint pane,
configure the Marketo endpoint as described in the following table.Note: Changing the configuration properties of an endpoint affects all orchestrations that use that endpoint in the project. The edits are global, not local.
- Click Test Connection to confirm that the connection details are valid and you are able to connect to Marketo successfully.
- Click OK.
Field Name | Description |
---|---|
Host Name | Host Name for Marketo instance (cloud) |
API Version | API version for Marketo instance. Default value: v1 |
Client Id | OAuth Client Id for accessing Marketo instance |
Client Secret | OAuth Client Secret for accessing Marketo instance |
Following parameters are required in endpoint test connection screen to make connection via Proxy:
Field Name | Description |
---|---|
Host name | Host Name of Proxy Network |
Port | Port Number of Proxy Network |
User Name | User Name for accessing service via proxy network |
Password | Password for accessing service via proxy network |
Objects Supported by the Marketo Connector
Following objects are supported by the Marketo Connector and the API available for the supported object:
Marketo Objects | Create | Update | Upsert | Delete | Retrieve All | Retrieve | Search |
---|---|---|---|---|---|---|---|
Lead | Yes | Yes | Yes | Yes | Yes | Yes | |
List | Yes | Yes | Yes | ||||
Campaign | Yes | Yes | Yes | ||||
Opportunity | Yes | Yes | Yes | Yes | Yes | ||
Company | Yes | Yes | Yes | Yes | Yes | ||
Sales Person | Yes | Yes | Yes | Yes | Yes | ||
Custom Object | Yes | Yes | Yes | Yes | Yes | ||
Opportunity Roles | Yes | Yes | Yes | Yes | Yes | ||
Lead Activity | Yes | ||||||
Deleted Leads | Yes | ||||||
Lead Changes | Yes | ||||||
Actity Types | Yes | ||||||
Folder | Yes | Yes | Yes | Yes | Yes | Yes | |
Folder Content | Yes | ||||||
Email Template | Yes | Yes | Yes | Yes | Yes | Yes | |
Email Template Content | Yes | Yes | |||||
Yes | Yes | Yes | Yes | Yes | Yes | ||
Email Content | Yes | Yes | |||||
Email Dynamic Content | Yes | Yes | |||||
Snippet | Yes | Yes | Yes | Yes | Yes | ||
Snippet Content | Yes | Yes | |||||
Snippet Dynamic Content | Yes | Yes | |||||
File | Yes | Yes | Yes | Yes | |||
Segmentation | Yes | ||||||
Segment | Yes |
Atomic Operations:
- For Leads
- Merge Leads
- Get Paging Token
- For Lists
- Remove Leads from list
- Add Leads to list
- Member of List
- Bulk APIs for Lead
- Import Leads
- Get Import Lead Status
- Get Import Failure File
- Get Import Warning File
- For Campaign
- Schedule Campaign
- Request Campaign
- For Email
- Update Email Content in Editable Section
- Send Sample Email
- For Email, Email Template and Snippet
- Approve Objects
- Unapprove Objects
- Discard Draft Objects
- Clone Objects
Custom Objects support:
Marketo supports Custom Objects. User can define custom object only using Marketo UI. Once custom object is defined, user can use the connector to Create, Update, Upsert, Delete and Search records of custom object.
- Begin with Alphabet
- Contains only alphanumeric characters
- Special characters only _ (Underscore)
Custom Fields support
Marketo supports custom fields only for Lead object and custom objects.
For Create and Update activities, in the Map Inputs of lead object will have additional nodes for custom fields so that user can provide values for them.
For Retrieve, RetrieveAll and Search activity, the response object will have custom fields data if exists.
For example, Lead object Map input/output:
company
billingStreet
billingCity
. .
customField1
customField2