The Workflow Library

Library / Data quality / data-quality-025

LinkedIn and social URL cleanup and format enforcement

Data qualityContactData Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. LinkedIn profile URLs land in one clean, consistent format with tracking parameters stripped, and anything that is not a real LinkedIn profile URL gets flagged instead of silently sitting there unusable.

Workflow map Enrollment, branches and actions at a glance data-quality-025
flowchart TD
    A[LinkedIn URL known or changed] --> B[Custom code: strip tracking, force https + www, check /in/ or /company/ path]
    B --> C{Valid shape?}
    C -->|yes| D[Set cleaned URL, status Valid - standardized]
    C -->|no| E[Status: Invalid - needs review, value untouched]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when reps or forms paste LinkedIn URLs in varied forms: with or without "https://", with or without "www.", with tracking query parameters attached, or as a mobile-app share-link format.
  • UseUse it to standardize the field for reliable use in mail merges, sales tools, or a "view on LinkedIn" button, so the stored value always opens correctly.
  • SkipDo not use it as validation that the profile is real, active, or belongs to the actual contact. It checks URL shape, not identity.
  • SkipDo not use it on a property that also stores non-LinkedIn social links; keep LinkedIn in its own property so the pattern-matching logic only has to understand one URL shape.
The preview ends here. Six sections are in the library. counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.3 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.5 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build, and the custom coded action ships as a ready-to-paste .js file.PDF, Markdown, JSON, code
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library, 149 EUR

or the data quality pack, 39 EUR

One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.