Workflows

Create Pages for a prospect list

Create one enrichment for the complete intended prospect list. Choose the template explicitly, supply its required values, and keep the returned identifiers for progress checks.

MCP

Prepare the request

Call get_template for the chosen slug and inspect its manifest. Each prospect needs linkedin_url; additional template values belong directly on that prospect object.

{
  "template_slug": "selected-template",
  "enrichment_name": "Product walkthrough test",
  "prospects": [
    {
      "linkedin_url": "https://www.linkedin.com/in/example-prospect/",
      "offer": "A tailored product walkthrough"
    }
  ]
}

Replace the template, profile, and example offer field with actual intended inputs. Do not add a nested template_variables object.

Submit once and follow the runs

Call enrich_prospects once for the complete list. Save enrichment_uuid and each PageRun public_id. Check progress with get_enrichment or get_page_run.

Creation is not idempotent. A repeated call creates new work; it does not extend or correct the original batch. After a timeout, search and inspect existing results before submitting again.

CRM association

For a verified HubSpot contact, use crm_provider: "hubspot" together with crm_contact_id. These fields must be paired. Check crm_writeback_state separately from Page success and confirm the actual CRM record when delivery matters.

Search guides and MCP references in one place.