Marketo forms
Forms 2.0 capture, the skipped follow-up page, and field mapping.
Route Marketo leadsto the right Salesforce rep
Default routes Marketo form fills to the right Salesforce rep and books the meeting.
The workflow starts when the Pixel captures a submission of your embedded Marketo form, and Marketo still receives it.
Look up each lead in Salesforce by email and return its current owner.
Rules of Engagement routes this form fill, and a smart campaign webhook on a score change can use the same ruleset.
Update Record replaces a placeholder owner, such as the Marketo sync user, with the rep the rules picked.
The assigned rep's calendar opens on your page after the visitor submits.
The Pixel captures Forms 2.0 submissions after Marketo accepts them. A smart campaign can also call Default's webhook, for example when a score changes.

Forms 2.0 capture, the skipped follow-up page, and field mapping.
Pixel capture, smart campaign webhooks, and writing results back through your CRM.
Start a workflow from a Marketo webhook, and send each event through 1 path so it routes once.
Match Record checks Salesforce first, then a rule or round robin picks a rep for each new lead and for any lead still owned by the sync user. Create Record writes the new leads to Salesforce.

Pick the owner by territory or company size from 1 shared ruleset.
Take turns across a team, with weights and out-of-office skips.
Tell the new owner in Slack, with the lead's score and company.
The assigned rep's calendar opens on your page in place of Marketo's follow-up page, and you can set where visitors go after they book or close the calendar.

The calendar opens over your page, with no second form to fill in.
Visitors who close the calendar go down the Not booked branch for follow-up.
“It’s the control layer we’re using to run GTM from the same brain.”
Default writes the owner and other fields to Salesforce with Update Record or Create Record, and Marketo picks them up through its Salesforce sync when it syncs those fields. That sync is Marketo's native connector: leads, contacts, and Salesforce campaigns sync both ways, and each cycle pauses 5 minutes before the next.
Yes, a Marketo smart campaign runs when the lead's score crosses your threshold, for example with the Score is Changed trigger, and calls Default's webhook through a Call Webhook flow step. The Default workflow then matches the lead in Salesforce and assigns an owner with Round-Robin.
No, Default connects to Marketo through the Pixel on your Marketo forms, the Incoming Webhook trigger for Marketo webhooks, and your Salesforce sync, since Marketo isn't a native integration and Default doesn't sign in to it. To write to Marketo, a Send to Webhook node can call a service you run that uses the Marketo REST API.
Default's Pixel captures each Marketo form submission while the visitor is still on the page, so the Form Submission workflow can route the lead and open a calendar right after submit. Send each event through 1 path, the Pixel or a webhook, or the lead routes twice.
Yes, when the form's Default workflow has a Display Scheduler node, the Pixel tells Marketo to skip its follow-up page and opens the routed rep's calendar on your page, while Marketo still receives the submission. The form has to be embedded in your page, since the Pixel can't read a cross-origin iframe.
Routing, enrichment, and scheduling for every inbound lead.
Turn website form fills into routed Salesforce leads.
Take turns across a team with weights and paused reps.
Route every Salesforce lead and book the meeting.
Keep every routing rule in 1 ruleset.
Route leads across both CRMs from 1 workflow.
One platform to manage workflows, enrich records, route leads, and schedule meetings.