Skip to main content

Improved Retrieve User and Company Profile Actions

We’ve improved retrieve user profile and retrieve company profile to accept comma-separated identifiers in a single input, so workflows no longer need multiple branches for different identifier types.

— Daniel Marr

Overview

The retrieve user profile and retrieve company profile actions are now more flexible and workflow-friendly.

Previously, each action could only accept one identifier type at a time. If your workflow might receive different identifier types, you had to build separate branches to handle each case.

Now, both actions support comma-separated input values, so you can provide multiple identifier types in one field.

What Changed

Before

Each action accepted only one of the following per run:

  • Provider ID
  • Public ID
  • LinkedIn profile URL

This often required multiple workflow branches.

Now

Both actions accept a single comma-separated input containing any combination of:

  • Provider ID
  • Public ID
  • LinkedIn profile URL

Why This Matters

  • Fewer workflow branches
  • Simpler action configuration
  • Cleaner and more maintainable automation logic

Example

{{contact.linkedin_provider_id}}, {{contact.linkedin_public_id}}, {{contact.linkedin_profile_url}}