The job Use Watch for
Sign-ups or account data from another system, sent to Marketo as they happen Lead upsert: POST /rest/v1/leads.json with createOrUpdate, up to 300 records a call The lookup field, email by default, decides what counts as the same person. Pick the wrong one and you create duplicates.
A big list or a nightly file of product usage Bulk import: POST /bulk/v1/leads.json with a CSV, up to a 10 MB body It runs as a job. Poll its status and read the failures file, or rejected rows disappear without anyone noticing.
Leads, activities or program members copied to a warehouse Bulk extract: create the job, enqueue it, poll status, then fetch the file Each job covers at most 31 days, two run at once, ten can queue, and exports share a 500 MB daily quota.
Recent activity for a known set of leads Activities: get a paging token from /rest/v1/activities/pagingtoken.json, then page forward Ask only for the activity types you need. Every page is a call against the daily total.
Something outside Marketo should happen the moment a lead qualifies A webhook called from a smart campaign flow step It's defined under Admin, but marketing ops decides when the campaign fires it, so agree who owns that campaign.