Overview
The Marketo integration lets users connect their Marketo instance so Alysio can query leads, lead schema, activities, static lists, programs, and campaigns on their behalf. Users can ask Alysio to get lead schema, fetch leads (by filter or by email/ID), retrieve lead activity, get static lists and list membership by lead, list programs, and get campaigns—all in natural language. The integration uses the user’s Marketo credentials (Client ID, Client Secret, Endpoint URL, Identity URL) via the connection form; authentication is not OAuth 2.0. Use marketo_get_leads_schema first to discover available and searchable fields for lead queries.
Supported capabilities / objects
- Leads — Lead schema (fields, searchable fields); get leads with filters; get lead by email; get lead by ID.
- Activities — Activity types; lead activity (with paging token from get_paging_token).
- Lists — Static lists; list membership by lead (leads in a list).
- Programs — List programs (by ID, name, or tag; with optional filters).
- Campaigns — Get campaign(s) by filter.
- Paging — Get paging token for activity and other paginated APIs.
Authentication
Method: Not OAuth 2.0. Marketo connection uses Client ID, Client Secret, Endpoint URL, and Identity URL. Users must obtain these four values from their Marketo instance and enter them when connecting Marketo to Alysio (e.g. in the Marketo integration form). The stored credential supplies the endpoint and identity URLs and the client ID/secret used to obtain access tokens for the Marketo REST API.
Redirect URI: Not applicable—Marketo connection does not use OAuth 2.0.
Gathering your Credentials
Users are required to enter their Marketo Client ID, Client Secret, Endpoint URL, and Identity URL when first connecting to the integration. You can find your Marketo application credentials by visiting LaunchPoint in the Admin section of your Marketo Dashboard.
Where to find each value:
- Client ID — Admin → Integration → LaunchPoint → View Details → Client Id on your Marketo dashboard.
- Client Secret — Admin → Integration → LaunchPoint → View Details → Client Secret on your Marketo dashboard.
- Endpoint URL — Admin → Integration → Web Services, in the REST API section.
- Identity URL — Admin → Integration → Web Services, in the REST API section.
The Endpoint URL typically looks like https://064-CCJ-768.mktorest.com/rest and the Identity URL like https://064-CCJ-768.mktorest.com/identity.
Press the blue “Continue” button to save your credentials.
Required credentials (all four)
- Marketo Client ID — Enter your Marketo Client ID. Find it in Admin → Integration → LaunchPoint → View Details → Client Id in Marketo.
- Marketo Client Secret — Enter your Marketo Client Secret. Find it in Admin → Integration → LaunchPoint → View Details → Client Secret in Marketo.
- Marketo Endpoint URL — Enter your Marketo REST endpoint URL (e.g.
https://064-CCJ-768.mktorest.com/rest). Find it in Admin → Integration → Web Services (REST API section) in Marketo.
- Marketo Identity URL — Enter your Marketo Identity URL (e.g.
https://064-CCJ-768.mktorest.com/identity). Find it in Admin → Integration → Web Services (REST API section) in Marketo.
Token handling
- The Client ID, Client Secret, Endpoint URL, and Identity URL are stored as part of the Marketo connection.
- The system uses the Identity URL and client credentials to obtain access tokens for the Marketo REST API; requests are sent to the Endpoint URL.
- Each user/tenant has their own credential; the MCP uses the appropriate credential so calls are isolated per connection.
- If credentials or URLs change (e.g. client secret rotated, instance migrated), the user must update the connection in Settings → Integrations.
- On disconnect, Marketo tools are unavailable until the user reconnects with valid credentials.
Credential justification
| Credential | Purpose |
|---|
| Client ID & Client Secret | Used to authenticate and obtain access tokens for Marketo API calls. |
| Endpoint URL | Base URL for Marketo REST API (leads, activities, campaigns, etc.). |
| Identity URL | Used for token requests to access the Marketo API. |
Connection required: Users must connect Marketo in Alysio and provide all four values (Client ID, Client Secret, Endpoint URL, Identity URL) before Marketo tools work. No OAuth 2.0 flow—credentials are entered in the Marketo integration form.
Credential security: Keep Client ID and Client Secret confidential. Rotate the client secret in Marketo (Admin → Integration → LaunchPoint) if compromised and update the connection in Alysio.
The Marketo MCP exposes the following tools. Users can invoke these capabilities through natural language in Alysio.
| Tool | Description | Example user prompts |
|---|
marketo_get_leads_schema | Returns the lead schema (fields and metadata), including which fields are searchable; use before get_leads or get_lead_by_* to choose filterType and fields. | ”What lead fields can I query?”, “Get Marketo lead schema.” |
marketo_get_leads | Fetches leads with filterType, filterValues, optional fields and nextPageToken; use schema for valid filter types and field names. | ”Find leads by email domain”, “List leads with this filter.” |
marketo_get_lead_by_email | Retrieves a lead by email address. | ”Get lead for john@company.com”, “Find lead by email.” |
marketo_get_lead_by_id | Retrieves a lead by Marketo lead ID. | ”Get lead 12345”, “Show lead by ID.” |
marketo_get_activity_types | Returns activity types from Marketo (for use as activityTypeIds in get_leads_activity). | ”What activity types are available?”, “Get Marketo activity types.” |
marketo_get_leads_activity | Retrieves lead activity; requires a paging token (get_paging_token) and activityTypeIds (get_activity_types); optional leadIds or listId. | ”Get activity for these leads”, “List lead activity for this list.” |
marketo_get_static_list | Retrieves static list(s) from Marketo; use returned id as listId for get_list_by_lead. | ”List our static lists”, “Get static list by name.” |
marketo_get_list_by_lead | Retrieves leads in a list by listId; use get_static_list for listId and get_leads_schema for fields. | ”Who’s in this list?”, “Get leads in list 456.” |
marketo_get_programs_list | Retrieves programs by ID, name, or tag (tagType + tagValue), with optional maxReturn, offset, status, dates. | ”List our programs”, “Find program by name.” |
marketo_get_campaign | Retrieves campaign(s) from Marketo with optional filter parameters. | ”Get campaign 789”, “List campaigns.” |
get_paging_token | Returns a paging token for use with get_leads_activity (and other paginated endpoints); pass sinceDatetime. | ”Get paging token for activities”, “Token for activity export.” |
App Behavior
- API calls are made on-demand only when the user asks something that requires Marketo data (e.g. lead schema, leads, activity, lists, programs, campaigns, paging token). There is no background sync; each request triggers the relevant Marketo API call using the user’s stored credential. The system resolves the Marketo endpoint URL from the stored credential so requests hit the correct instance.
Example flow
- User asks: “Get lead activity for leads in our Q1 list.”
- Alysio routes the request to the Marketo MCP.
- The MCP may call
marketo_get_static_list to find the list ID, get_paging_token for a token, marketo_get_activity_types for activityTypeIds, then marketo_get_list_by_lead or marketo_get_leads_activity with listId and the token.
- The request is sent to the user’s Marketo endpoint URL using the stored credentials.
- The MCP returns the activity (or list) data; Alysio presents the results in chat.
Troubleshooting
Common issues
- Marketo not connected — User has not completed the Marketo connection form with all four values. Fix: In Settings → Integrations, connect Marketo and enter Marketo Client ID, Marketo Client Secret, Marketo Endpoint URL, and Marketo Identity URL. Find Client ID and Secret in Admin → Integration → LaunchPoint → View Details; find Endpoint URL and Identity URL in Admin → Integration → Web Services (REST API section).
- 401 Unauthorized — Client ID or Client Secret invalid or revoked. Fix: In Marketo go to Admin → Integration → LaunchPoint, verify or regenerate the API-only user’s client ID and secret, then update the connection in Alysio.
- Endpoint URL not found / wrong instance — Endpoint or Identity URL missing or incorrect. Fix: In Marketo go to Admin → Integration → Web Services and copy the correct REST Endpoint URL and Identity URL (e.g.
https://xxx-xxx-xxx.mktorest.com/rest and https://xxx-xxx-xxx.mktorest.com/identity); update the connection in Alysio.
- Invalid filterType or fields — Lead query fails. Fix: Call
marketo_get_leads_schema first and use only searchable fields as filterType and field names from the schema as the fields parameter.
- Lead activity requires paging token — get_leads_activity needs a token from get_paging_token and activityTypeIds from marketo_get_activity_types. Fix: Call get_paging_token (with sinceDatetime) and marketo_get_activity_types, then pass nextPageToken and activityTypeIds into marketo_get_leads_activity.
Support
- Email: support@alysio.ai
- For Marketo REST API details, see Admin → Integration → Web Services in Marketo and Marketo developer documentation.
