Skip to main content

Overview

The Marketo integration allows Alysio to securely connect to a Marketo instance in order to retrieve marketing automation data including leads, activities, lists, programs, and campaigns. Once connected, users can query lead data, analyze marketing activity, explore list membership, retrieve program details, and review campaign information using natural language inside Alysio. Unlike some integrations that rely on OAuth authorization, the Marketo integration uses client credentials authentication with Marketo’s REST API. Users connect their Marketo instance by providing the required credentials and API endpoints through the Alysio integration settings. This integration enables revenue and marketing teams to combine Marketo data with CRM, outreach, and support systems within the Alysio platform.

Supported Data and Capabilities

The Marketo integration supports access to several key marketing automation objects.

Leads

Retrieve lead records and lead metadata stored in Marketo. Supported operations include: Retrieving lead schema and searchable fields
Querying leads using filters
Retrieving leads by email address
Retrieving leads by Marketo lead ID
Lead schema discovery is recommended before performing lead queries.

Activities

Retrieve activity records associated with leads. Activities may include email engagement, form submissions, program activity, and other tracked interactions. Activity retrieval requires a paging token and valid activity type identifiers.

Lists

Retrieve static lists and list membership. Supported operations include: Listing static lists
Retrieving leads within a list
Lists are commonly used to track campaign segments or marketing cohorts.

Programs

Retrieve marketing programs configured in Marketo. Programs may represent marketing initiatives, campaign structures, or lifecycle tracking workflows. Programs can be retrieved using identifiers, names, or tags.

Campaigns

Retrieve campaign records stored in Marketo. Campaigns may include marketing automation flows and program-based campaigns associated with marketing programs.

Paging

Retrieve paging tokens required for activity queries and other paginated endpoints. Paging tokens allow Alysio to retrieve activity data incrementally.

Authentication

The Marketo integration uses client credential authentication rather than OAuth. Users connect their Marketo instance by providing the following credentials: Client ID
Client Secret
Endpoint URL
Identity URL
These values are entered through the Alysio Settings → Integrations panel when connecting the Marketo integration.

Gathering Your Credentials

The required credentials can be found in the Marketo administration interface.

Client ID

Admin → Integration → LaunchPoint → View Details → Client ID

Client Secret

Admin → Integration → LaunchPoint → View Details → Client Secret

Endpoint URL

Admin → Integration → Web Services → REST API section Example format https://123-ABC-456.mktorest.com/rest

Identity URL

Admin → Integration → Web Services → REST API section Example format https://123-ABC-456.mktorest.com/identity

Required Credentials

CredentialPurpose
Client IDIdentifies the Marketo application for API authentication
Client SecretUsed with the client ID to obtain API access tokens
Endpoint URLBase URL used for Marketo REST API requests
Identity URLUsed to request access tokens for API authentication
All four values are required for the Marketo integration to function.

Credential Handling

The Client ID, Client Secret, Endpoint URL, and Identity URL are securely stored as part of the Marketo integration configuration. Alysio uses the Identity URL and client credentials to obtain an API access token before sending requests to the Marketo REST API through the Endpoint URL. Each tenant maintains their own credential configuration, ensuring requests are isolated to the correct Marketo instance. If credentials are rotated or the Marketo instance changes, the integration must be updated within Settings → Integrations.

MCP Tools

The Marketo MCP provides several tools that allow Alysio to retrieve marketing automation data.

marketo_get_leads_schema

Retrieves the Marketo lead schema including field metadata and searchable fields. Example prompts What lead fields can I query
Show Marketo lead schema

marketo_get_leads

Retrieves leads using specified filters and fields. Example prompts Find leads with this email domain
List leads matching this filter

marketo_get_lead_by_email

Retrieves a lead using an email address. Example prompts Get lead for john@company.com
Find lead by email

marketo_get_lead_by_id

Retrieves a lead using the Marketo lead ID. Example prompts Show lead 12345
Get lead by ID

marketo_get_activity_types

Retrieves activity types available within the Marketo instance. Example prompts What activity types are available
Show Marketo activity types

marketo_get_leads_activity

Retrieves lead activity records. Example prompts Show activity for these leads
List activity for this campaign
Activity queries require a paging token and activity type identifiers.

marketo_get_static_list

Retrieves static lists configured in Marketo. Example prompts Show static lists
List marketing lists

marketo_get_list_by_lead

Retrieves leads within a specific list. Example prompts Who is in this list
Show leads in list 456

marketo_get_programs_list

Retrieves marketing programs. Example prompts List our programs
Find program by name
Programs can also be filtered by tags or status.

marketo_get_campaign

Retrieves campaign records. Example prompts Show campaign 789
List marketing campaigns

get_paging_token

Retrieves a paging token for use in paginated queries. Example prompts Get paging token for activities
Create paging token for activity export

App Behavior

Marketo API calls are executed on demand when users request marketing data through Alysio. There is no background synchronization between Alysio and Marketo. Instead, API requests are executed in real time using the stored credentials and Marketo endpoint configuration. The system dynamically resolves the correct Marketo instance URL from the stored Endpoint URL.

Example Workflow

User asks Get lead activity for leads in our Q1 list Alysio routes the request to the Marketo MCP. The MCP retrieves the list ID using marketo_get_static_list. A paging token is retrieved using get_paging_token. Activity types are retrieved using marketo_get_activity_types. The MCP retrieves activity records using marketo_get_leads_activity. The Marketo API returns the activity data. Alysio presents the results in the chat interface.

Troubleshooting

Marketo Not Connected

The required credentials have not been entered. Solution
Navigate to Settings → Integrations and enter the Client ID, Client Secret, Endpoint URL, and Identity URL.

Authentication Error

The Client ID or Client Secret may be invalid. Solution
Verify credentials in Admin → Integration → LaunchPoint and update the integration connection.

Incorrect Endpoint URL

Requests may fail if the endpoint URL or identity URL is incorrect. Solution
Verify both URLs under Admin → Integration → Web Services → REST API section.

Invalid Lead Query

Lead queries may fail if the filter type or fields are not valid. Solution
Call marketo_get_leads_schema first to retrieve valid field names and searchable attributes.

Activity Retrieval Errors

Activity queries require a paging token and activity type identifiers. Solution
Call get_paging_token and marketo_get_activity_types before retrieving activity data.

Support

For assistance configuring or troubleshooting the Marketo integration, contact support@alysio.ai For Marketo REST API documentation, refer to Admin → Integration → Web Services in the Marketo dashboard or the Marketo developer documentation.