Skip to content
The Workflow Library
Get the full library

Route leads created via API/integration (source = integration) bypassing forms logic

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Data Hub Professional.

8 steps
Per-hub plans: also Marketing Hub Professional

On per-hub plans, one of its steps belongs to another subscription: add to static list needs Marketing Hub Professional. Both are required to build it as written. On seat pricing the edition covers both.

Updated for HubSpot seat pricing
OutcomeA contact created through an API integration gets the same default properties and routing treatment a form submission would have given it, instead of arriving incomplete because it never touched a HubSpot form.
Workflow maplead-routing-048
Contact created via API/integration leads to Territory unknown?. Territory unknown? leads to Yes: Set default Territory; No: Lifecycle Stage unknown?. Set default Territory leads to Lifecycle Stage unknown?. Lifecycle Stage unknown? leads to Yes: Set Lifecycle Stage = Lead; No: Consent required and unknown?. Set Lifecycle Stage = Lead leads to Consent required and unknown?. Consent required and unknown? leads to Yes: Add to API-created - needs consent review; No: Mark Backfilled Defaults Applied = true. Add to API-created - needs consent review leads to Mark Backfilled Defaults Applied = true. Mark Backfilled Defaults Applied = true leads to Standard routing workflow enrolls normally. Yes No Yes No Yes No Contact created via API/integration Territory unknown? Set default Territory Lifecycle Stage unknown? Set Lifecycle Stage = Lead Consent required and unknown? Add to API-created - needs consent review Mark Backfilled Defaults Applied = true Standard routing workflow enrolls normally
Contact created via API/integration leads to Territory unknown?. Territory unknown? leads to Yes: Set default Territory; No: Lifecycle Stage unknown?. Set default Territory leads to Lifecycle Stage unknown?. Lifecycle Stage unknown? leads to Yes: Set Lifecycle Stage = Lead; No: Consent required and unknown?. Set Lifecycle Stage = Lead leads to Consent required and unknown?. Consent required and unknown? leads to Yes: Add to API-created - needs consent review; No: Mark Backfilled Defaults Applied = true. Add to API-created - needs consent review leads to Mark Backfilled Defaults Applied = true. Mark Backfilled Defaults Applied = true leads to Standard routing workflow enrolls normally. Yes No Yes No Yes No Contact created via API/integration Territory unknown? Set default Territory Lifecycle Stage unknown? Set Lifecycle Stage = Lead Consent required and unknown? Add to API-created - needs consent review Mark Backfilled Defaults Applied = true Standard routing workflow enrolls normally

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

When to use it, when not to

Use it

  • Use it whenever contacts enter the portal through a connected app or a direct API call (a custom integration, a legacy CRM migration feed, a partner system) rather than a HubSpot form, and currently skip properties that forms normally set (hidden fields, consent defaults, an initial Territory or Lifecycle Stage).
  • Use it as a backfill-and-route step that runs once per contact, feeding the standard routing workflow (lead-routing-001 or similar) once the missing defaults are filled in.
Read more on when to use itShow less

Skip it

  • Do not use it if the integration already sets every property a form would; there is nothing to backfill, route these directly through the standard workflow.
  • Do not use it to backfill legal or consent-related properties silently. If forms normally capture explicit consent, an API-created contact skipping that step needs a genuine compliance decision, not an automatic assumption of consent, see Known pitfalls.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 4 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 8 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 5 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Lead routing spec

Not the workflow you needed?

More in Lead routing

50 specs in this section

See all 50 This category, 39 EUR
FreeRound-robin lead assignment by territoryContact15 steps Route leads by postal code / zip using a lookup table (postal-to-territory)Contact2 steps New lead auto-assignment by owner rotationContact3 steps First-contact SLA timer with owner reminder taskContact11 steps

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library