PipeLaunch Signals - Run Automation: Flow Input Variables
Run Automation lets you fire an Autolaunched Flow every time a given Signal type is detected. Configure it per signal type under Setup > Signals > [Signal type] by turning on Enable → Automatic Action → Run Flow, then picking your Flow.
Some signal types ship with a ready-made Flow template you can pick immediately (see the PipeLaunch Signals: Included Flow Templates article). Enrich Person, Find Person LinkedIn, and Find Company LinkedIn don't ship a template yet — Run Automation still works for them, you just need to build your own Autolaunched Flow. This doc lists exactly which variables your Flow receives for every signal type, so you can build one, plus a quick look at the data shapes involved.
Flow input variables by signal type
Company Change — 2 templates included (Create New Account / Create New Lead)
Both bundled templates receive the same variable set:
API Name | Data Type | Description |
|---|---|---|
| Text | Id of the Contact record |
| Text | New company's LinkedIn URL |
| Text | New company name |
| Text | New company website |
| Number | Confidence score (0–100) |
| Text | Contact's title at the new company |
| Text | Reserved — currently always blank |
| Text | Reserved — currently always blank |
| Text | Reserved — currently always blank |
| Text | Reserved — currently always blank |
| Text | Reserved — currently always blank |
Job Title Change — template included
API Name | Data Type | Description |
|---|---|---|
| Text | Id of the Contact record |
| Number | Confidence score (0–100) |
| Text | The new job title |
Name Mismatch — template included
API Name | Data Type | Description |
|---|---|---|
| Text | Id of the Contact record |
| Number | Confidence score (0–100) |
| Text | Corrected first name |
| Text | Corrected last name |
Enrich Person — no template yet
API Name | Data Type | Description |
|---|---|---|
| Text | Id of the Contact record |
| Long Text (JSON) | The full enriched LinkedIn profile, serialized as JSON — see shape below |
Find Person LinkedIn — no template
API Name | Data Type | Description |
|---|---|---|
| Text | Id of the record the person was matched to |
| Text | The found LinkedIn profile URL |
| Number | Confidence score (0–100) |
Find Company LinkedIn — no template
API Name | Data Type | Description |
|---|---|---|
| Text | Id of the record the company was matched to |
| Text | The found company LinkedIn URL |
| Number | Confidence score (0–100) |
Location Change — not currently supported
Run Automation does not fire a flow for this signal type today.
Quick data-structure reference
The Signal record (PipeLaunchSignal__c)
Every Signal — regardless of type — is stored as one of these records:
Field | Type | Description |
|---|---|---|
| Picklist | Signal type (Company Change, Enrich Person, Find Company Linkedin, Find Person Linkedin, Job Title Change, Location Change, Name Mismatch) |
| Picklist | Open, Closed, Ignored, or Error |
| Text | The new value detected |
| Text | The prior value on the record (blank for Enrich Person — there's nothing to compare against) |
| Percent | 100% = very high confidence |
| Date | Date the signal applies to (e.g. new job start date); not meaningful for every type |
| Long Text (JSON) | Raw JSON payload backing the signal — do not edit |
| Lookup | Whichever one is populated is the record the signal belongs to |
| Formula (Text) | Resolves to Contact/Lead/PersonAccount/Account based on which lookup is populated |
The LinkedIn profile JSON (var_PipelaunchValue_LinkedinRawData / Data__c)
This is the shape you'll parse in Apex or a Flow "Parse JSON" action. Top level only — most list fields below contain their own nested objects.
Field | Type | Description |
|---|---|---|
| Number | Parsing-engine version (format YYYYMMDD) |
| Text | LinkedIn profile slug (can change if the user changes their vanity URL) |
| Text | Full LinkedIn profile URL |
| Text | Stable LinkedIn identifier (never changes) |
| Text | Stable LinkedIn Recruiter identifier / URL |
| Text | Sales Navigator identifier |
| Text | Full display name |
| Object | Structured name parts |
| Text | Nickname extracted from the name |
| Text | Headline / current job title shown on the profile |
| Text | Profile "About" text |
| Object | Profile picture |
| Object | Address/location |
| List | Work history |
| List | Education history |
| List | Listed skills |
| List | Listed languages |
| List | Emails from LinkedIn's contact info |
| List | Phone numbers from LinkedIn's contact info |
| List | Website links from contact info |
| List | Instant-messaging handles |
| List | Certifications |
| List | Courses |
| List | Honors & awards |
| List | Organizations |
| List | Publications |
| List | Patents |
| List | Projects |
| List | Volunteering experience |
| Object | Connection count (capped at "500+") |
| Number | Follower count |
| Boolean | #OPEN_TO_WORK / #HIRING banner shown |
| List | Verification badges (e.g. work email verified) |
| Object | Birthday, if shared |
| Object | Gender, if available |
| Text | XING (non-LinkedIn network) identifiers, if matched |
Updated on: 11/09/2026