Marketo Engage
Turn orders and customer changes into the right Marketo Engage audiences and campaigns, with a person approving what goes out.
58 ways to read, 8 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Marketo Engage, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Sync companyApproval by rule
- Add custom activityApproval by rule
- List lead activitiesRead
Example flow
- Marketo Engage · List lead activitiesDone
- Marketo Engage · Sync companyNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Marketo Engage.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Marketo Engage
- Marketo Engage's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.
For developers
Technical detail
Read and sync Marketo leads, lists, programs, members, activities, custom objects, companies and opportunities; read campaigns, smart lists, emails, forms, landing pages, folders and tokens.
Adobe API docs- Source actions
- 58
- Destination actions
- 8
- Data types
- 47
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Activities1
- List lead activitiesSource
Activities of up to 10 types after a paging token, optionally for specific leads.
Activity paging tokens1
- Get activity paging tokenSource
Paging token representing a start date for activity and lead change reads.
Activity types1
- List activity typesSource
Standard and custom activity types with primary and secondary attributes.
API usage1
- Get API usageSource
API call counts per day and per API user, for today or the last 7 days.
Campaigns2
- Get campaign (lead database)Source
A batch or trigger campaign by ID (read-only).
- List campaigns (lead database)Source
Batch and trigger campaigns from the lead database API, filterable by ID, name, program or workspace (read-only).
Channels1
- List channelsSource
Program channels with their progression statuses and success steps.
Companies2
- Get companiesSource
Companies matching values of a searchable field (for example externalCompanyId).
- Sync companyDestinationProvider duplicate protectionApproval before production
Creates or updates one company deduplicated on externalCompanyId (or id).
Custom activities1
- Add custom activityDestinationNot retried automaticallyApproval before production
Records a custom activity (of an approved custom activity type) on a lead.
Custom activity types1
- List custom activity typesSource
Custom activity types with status, primary and secondary attributes.
Custom object types2
- Describe custom object typeSource
Fields (with data types) and keys of one custom object type.
- List custom object typesSource
Custom object types with dedupe fields, searchable fields and relationships.
Custom objects2
- Get custom object recordsSource
Custom object records matching values of a searchable field.
- Sync custom object recordDestinationProvider duplicate protectionApproval before production
Creates or updates one custom object record on its dedupe fields.
Deleted leads1
- List deleted leadsSource
Lead deletions after a paging token (deleted within the last 14 days).
Email templates2
- Get email templateSource
An email template asset's metadata.
- List email templatesSource
Email template assets with status and folder.
Emails2
- Get emailSource
An email asset's metadata.
- List emailsSourceIncremental
Email assets (metadata: subject, sender, template, status); content is not returned.
Files1
- List filesSource
Files in Design Studio with MIME type, size and URL.
Folders2
- Get folderSource
A folder or program node in the folder tree.
- List foldersSource
Marketing folders and programs in the folder tree, optionally under a root.
Form fields1
- List form fieldsSource
Fields on a form with data type, label, required flag and visibility rules.
Forms2
- Get formSource
A form asset's settings.
- List formsSource
Form assets with language, progressive profiling and follow-up settings.
Landing pages2
- Get landing pageSource
A landing page asset's metadata.
- List landing pagesSource
Landing page assets with template, URL and status; page HTML is not returned.
Lead changes1
- List lead changesSource
Data value changes and new lead activities for chosen fields after a paging token.
Lead fields1
- Describe lead fieldsSource
Lead fields with data type, length, updateability and searchability.
Lead list memberships1
- List a lead's static listsSource
Static lists a lead belongs to.
Lead partitions1
- List lead partitionsSource
Lead partitions available for lead syncs.
Lead program memberships1
- List a lead's programsSourceIncremental
Programs a lead is a member of with progression status and success.
Lead smart campaign memberships1
- List a lead's smart campaignsSourceIncremental
Smart campaigns a lead is a member of.
Leads3
- Get leadSource
A lead by Marketo ID.
- Get leads by filterSource
Leads matching up to 300 values of a searchable field.
- Create or update leadDestinationProvider duplicate protectionApproval before production
Syncs one lead, deduplicated on the lookup field (email by default). Consent fields such as unsubscribed change only when mapped explicitly.
List members2
- Add leads to static listDestinationProvider duplicate protectionApproval before production
Adds up to 300 leads to a static list; existing members are left unchanged.
- List static list membersSource
Leads in a static list.
List membership checks1
- Check static list membershipSource
Whether each of up to 300 leads (by Marketo ID) is in a static list.
Lists2
- Get static listSource
A static list by ID.
- List static listsSource
Static lists, optionally filtered by program or workspace name.
Named account lists1
- Get named account listsSource
Named account lists matching values of a searchable field (name or marketoGUID).
Named accounts1
- Get named accountsSource
Named accounts (ABM) matching values of a searchable field, for example name or marketoGUID.
Opportunities2
- Get opportunitiesSource
Opportunities matching values of a searchable field (for example externalOpportunityId).
- Sync opportunityDestinationProvider duplicate protectionApproval before production
Creates or updates one opportunity deduplicated on externalOpportunityId.
Opportunity roles2
- Get opportunity rolesSource
Lead roles on opportunities matching a searchable field.
- Sync opportunity roleDestinationProvider duplicate protectionApproval before production
Creates or updates one opportunity role (externalOpportunityId, leadId, role).
Program member fields1
- Describe program member fieldsSource
Program member fields with data type, updateability and searchability.
Program member statuses1
- Set program member statusDestinationProvider duplicate protectionApproval before production
Sets the program status for up to 300 leads (adds them to the program if needed).
Program members1
- List program membersSource
Program members filtered by a searchable member field.
Program tokens1
- List folder or program tokensSource
My tokens defined on a folder or program, with type and value.
Programs3
- Get programSource
A program with tags, costs and dates.
- List programsSourceIncremental
Programs with type, channel, status and folder.
- Find programs by tagSource
Programs carrying a tag type and value.
Sales persons1
- Get sales personsSource
Sales persons matching values of a searchable field such as externalSalesPersonId or id.
Segmentation segments1
- List segments of a segmentationSource
Segments in a segmentation.
Segmentations1
- List segmentationsSource
Segmentations with status and folder.
Smart campaign smart lists1
- Get smart campaign smart listSource
The smart list (audience rules) of a smart campaign.
Smart campaigns2
- Get smart campaignSource
A smart campaign, optionally with flow steps.
- List smart campaignsSourceIncremental
Smart campaigns with type, status and qualification rules.
Smart lists2
- Get smart listSource
A smart list, optionally with its triggers and filters.
- List smart listsSourceIncremental
Smart list assets with folder and workspace.
Snippets1
- List snippetsSource
Snippet assets with status and folder.
Static lists1
- List static lists (assets)SourceIncremental
Static list assets with folder and workspace, filterable by folder and update time.
Tag types1
- List tag typesSource
Program tag types with required flag and applicable program types.
Access and limits
- Authentication
- LaunchPoint custom service client ID and secret
- Plans and access
- All Marketo Engage subscriptions include the REST API. Requires an API-only user with an API role and a LaunchPoint custom service; access is limited by the role's permissions and workspaces.
- Test environment
- Marketo sandbox instances are available on some subscriptions.
- Rate limits
- 100 calls per 20 seconds and 10 concurrent calls per instance; 50,000 calls per day by default. Errors 606/607/615 signal rate, quota and concurrency limits.
- Pagination
- Lead database lists use nextPageToken (300 records per page); activities need a paging token from a start date; asset lists use offset and maxReturn (200).
- Provider events
- Marketo webhooks are configured as smart campaign flow steps. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Deleting leads, list members, custom objects, companies and opportunities is not implemented.
- Requesting, scheduling, activating or deactivating campaigns, sending sample emails and approving or unapproving assets are not implemented; campaign and smart campaign operations are read-only.
- Adding leads to a static list (list_members.create) or setting program member status (program_member_statuses.update) can qualify leads for trigger smart campaigns (Added to List, Program Status is Changed) that send email or change data in Marketo.
- Removing list members, deleting records and assets, bulk imports and bulk exports are not implemented.
- Email, landing page, snippet and template content (HTML) is not returned; asset reads expose metadata only. Creating or updating assets, folders, tokens and smart lists is not implemented.
- Asset lookups by name (byName endpoints) are not implemented; use list filters and get by ID.
- Lead syncs never use createDuplicate or createOnly, so repeats converge on the lookup field.
- Marketo reports token expiry (601/602) inside HTTP 200 bodies; the request fails and the next run obtains a new token.
- Activity and lead change reads need a paging token; call Get activity paging token first and pass it as startToken.
Developer reference
- Create the Adobe credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Marketo Engage, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/marketo and the Connections API.