Fin for Sales can connect directly to your Marketo account and build a working data connector in minutes. The process requires no API knowledge, no code, and no manual field mapping.
Pick a template, connect Marketo with your API credentials, and our AI generator inspects your Marketo instance (including custom fields) to build a fully configured connector. Review the suggested mappings, adjust as needed, and add it to your setup. Fin can then pull live person context into sales conversations and sync qualified people back to Marketo.
What you can do:
📥 Enrich person (read) | 📤 Sync person (write) |
Fin pulls live person context from Marketo into your sales conversations. | Fin syncs qualified people to Marketo. This is an upsert: it updates the matching person if one exists, or creates a new person in your selected partition if it doesn't. |
Note: Two templates are available: Enrich person from Marketo (read) and Sync conversation data to a Marketo lead (write).
Important: Set up Enrich person and Sync person together
The Sync Conversation Data (write) connector is an upsert (it will either update an existing Marketo person or create a new one).
At the start of a conversation, Fin doesn't know the Marketo person ID. The Enrich person (read) connector is what resolves a returning person to their existing Marketo record (and its lead ID).
If you set up Sync person without Enrich person, Fin has no stored Marketo person ID and has to fall back to matching on email alone (which is slower), and fails outright if two people in the partition share that email. Set up both so writes are keyed on the person's ID and land on the right record.
Before you start
Marketo doesn't use a one-click sign-in, so you'll need four values from your Marketo admin before you start:
REST API endpoint and Identity URL: in Marketo, go to Admin > Integration > Web Services. Both must be HTTPS mktorest.com URLs from the same account (for example https://123-ABC-456.mktorest.com/rest and https://123-ABC-456.mktorest.com/identity).
Client ID and Client secret: open your custom service under Admin > Integration > LaunchPoint and click View Details.
How to set it up
Connect Marketo to Fin for Sales from the "Connected services" section in Fin AI Agent > Sales > Train > Integrations.
Step 1: Connect Marketo
Enter your REST API endpoint, Identity URL, Client ID, and Client secret.
We verify the credentials against Marketo before saving them. If Marketo rejects them, nothing is stored.
Step 2: Pick a template
Choose Enrich person from Marketo (read) or Sync conversation data to a Marketo lead (write). To sync people back, set up both.
Step 3: Choose a person partition
Choose which partition Fin should use, so it reads and writes the right record. If your account has only one accessible partition, it's selected for you.
Everything Fin does is scoped to this partition: people outside it aren't found during enrichment, and new people are created inside it.
Step 4: Provide a test email
This runs a real lookup against your Marketo account so the connector can be built and tested against live data. The person isn't contacted. The email needs to match a person that exists in the partition you selected.
Step 5: Let AI generate the connector
This takes about 15–30 seconds while AI inspects your Marketo lead schema, runs a test request, and assembles the connector.
Step 6: Review the field mappings
You'll see a table of Marketo field → Intercom attribute mappings that you can edit before confirming. Marketo fields that don't match existing Intercom attributes are automatically mapped to new mkto_-prefixed attributes.
The Marketo person ID mapping is managed by Fin and can't be edited or removed. It's the key Fin uses to update the right record safely.
Step 7: Add it to your setup
Read connector: add it to enrichment - it runs at the start of each conversation.
Write connector: attach it to a routing outcome - it fires when that outcome is reached.
Note:
Sync is an upsert: Sync person updates the matching Marketo person, or creates one in your selected partition when none exists. Pair it with Enrich person so Fin can match returning people reliably.
Partition scoped: Fin only reads and writes within the partition you selected. Change it and the new partition applies from the next conversation onwards.
Auto-refresh: Marketo access tokens expire periodically; the connector refreshes automatically.
Custom fields included: Fin reads your Marketo custom fields during setup.
Troubleshooting
Issue | Solution |
"Marketo rejected these credentials" | Check the Identity URL, Client ID, and Client secret, and that the API-only user's custom service is active. |
"The Marketo API user cannot access any person partitions" | Grant the API-only user's role Read-Write Lead access in Marketo, then reconnect. |
"No Marketo person with this email exists in the selected partition" | The test email didn't match a person in the partition you selected. Verify the email exists there, or select the correct partition. |
"The test Marketo person needs a value in at least one writable field" | Write access is verified without changing data, so the test person needs at least one text field filled in. Use a more complete person record. |
Duplicate people showing up in Marketo | Sync person couldn't match a returning person to their existing record. Ensure Enrich person is also set up so the Marketo person ID is captured. |
Connector stopped working | Usually a Marketo auth issue. The connector should auto-refresh and retry. If it persists, reconnect Marketo. |
"Reconnect Marketo and select a person partition" | The connection or partition selection is missing. Reconnect Marketo and choose a partition again. |
Still stuck? Reach out to the support team for assistance.