Skip to main content
POST
/
flows
/
linkedin-content-search-enrich
/
run
/
async
Run linkedin-content-search-enrich flow asynchronously
curl --request POST \
  --url https://api.edges.run/v1/flows/linkedin-content-search-enrich/run/async \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '
{
  "inputs": [
    {
      "linkedin_content_search_url": "<string>",
      "custom_data": {
        "meta": "<unknown>"
      }
    }
  ],
  "steps": [],
  "parameters": {
    "linkedin-search-content": {},
    "linkedin-extract-post": {},
    "linkedin-extract-people": {},
    "linkedin-extract-company": {},
    "fullenrich-enrich-people": {}
  },
  "identity_ids": [
    "44444444-4444-4444-4444-444444444444"
  ],
  "identity_mode": "direct"
}
'
{
  "uid": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "workflow": {
    "uid": "<string>",
    "metadata": {
      "account_rotation": true
    }
  }
}
The LinkedIn Content Search Enrich flow lets you search LinkedIn posts using a content search URL, then enriches each result with author profile and company information. This flow is perfect for content monitoring, lead generation from engagement, and competitive analysis.

​
Flow Steps

The flow executes steps in the following order:
  1. Search LinkedIn Content (required): Searches LinkedIn for posts matching your search criteria
    • Extract LinkedIn Post Content: Extracts detailed post content and metrics
    • Extract LinkedIn People: Extracts detailed information from the post author’s profile
    • Extract LinkedIn Company Profile: Extracts company information for the author’s current company
    • Full enrich people: Enriches profiles with contact information (emails and/or phone numbers). Credit costs: 2 credits for emails, 20 credits for phones, 22 credits for both.
Some steps have dependencies on other steps. For example, Full enrich people requires profile data from previous steps. If you include a step that has dependencies, the required steps will be automatically activated even if you don’t explicitly include them in your request body.
Each item in the inputs array can include an optional custom_data object. The only valid key inside custom_data is meta. Use meta to attach a free-form object (e.g. your own IDs, tags, or context) that will be passed through and available in the flow output.Example:
"inputs": [
  {
    ...
    "custom_data": {
      "meta": {
        "foo": "bar",
        "crm_id": 1234
      }
    }
  }
]
We currently require meta as a workaround to ship this capability; a more solid implementation will follow soon without breaking changes.
Examples: 
curl --request POST \
  --url https://api.edges.run/v1/flows/linkedin-content-search-enrich/run/async \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <your-api-key>' \
  --data '{
  "inputs": [
    {
      "linkedin_content_search_url": "https://www.linkedin.com/search/results/content/?keywords=AI%20automation"
    }
  ],
  "identity_mode": "managed"
}'

curl --request POST \
  --url https://api.edges.run/v1/flows/linkedin-content-search-enrich/run/async \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <your-api-key>' \
  --data '{
  "steps": [
    "Extract LinkedIn Post Content",
    "Extract LinkedIn People",
    "Extract LinkedIn Company Profile",
    "Full enrich people"
  ],
  "parameters": {
    "linkedin-search-content": {
      "max_results": 50,
      "only_extract_unique_profile": true
    },
    "linkedin-extract-people": {
      "sections": true,
      "experiences": true
    },
    "fullenrich-enrich-people": {
      "enrich_level": "emails"
    }
  },
  "inputs": [
    {
      "linkedin_content_search_url": "https://www.linkedin.com/search/results/content/?keywords=saas%20growth"
    }
  ],
  "identity_ids": ["44444444-4444-4444-4444-444444444444"]
}'

curl --request POST \
  --url https://api.edges.run/v1/flows/linkedin-content-search-enrich/run/async \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <your-api-key>' \
  --data '{
  "parameters": {
    "linkedin-search-content": {
      "max_results": 100
    }
  },
  "inputs": [
    {
      "linkedin_content_search_url": "https://www.linkedin.com/search/results/content/?keywords=startup%20funding"
    }
  ],
  "identity_mode": "managed",
  "callback": {
    "url": "https://your-app.com/webhook/flow-results",
    "headers": {
      "Authorization": "Bearer your-webhook-token"
    }
  }
}'
Instead of polling for results, you can use webhooks to receive automatic notifications when this flow completes. Learn more about webhook payloads and handling.

Authorizations

​
X-API-Key
string
header
required

Body

application/json
​
inputs
object[]
required
Required array length: 1 - 1000 elements
​
steps
enum<string>[]

Optional list of step to run. If not provided, only the required steps will be run.

Available options:
linkedin-extract-post,
linkedin-extract-people,
linkedin-extract-company,
fullenrich-enrich-people
​
parameters
object
​
identity_ids
string<uuid>[] | null

An array of Identity UUIDs linked to identities (e.g. LinkedIn) used to execute the Action. You must provide at least one valid UID with access to the integration. Do not use account_uid values — only user_uid is supported.

Example:
["44444444-4444-4444-4444-444444444444"]
​
identity_mode
enum<string> | null
default:direct

If "auto", the Action will use any identities from the current workspace (unless you have provided a list of identity_ids). "managed" will use the Edges pool of identities for an extra credit cost

Available options:
direct,
auto,
managed
​
callback
object

Callbacks

POST
{$request.body#/callback/url}onSave

Body

application/json
​
flow_run
object
​
error
APIError · object

Represents an error returned by the API. This schema defines the standard structure of error messages to ensure consistent error handling across the application.

​
results_count
integer

Number of results in the current callback

​
results
object[]

Results of the current callback

Response

200

Callback successfully processed

Response

Successful response

Successful response

​
uid
string<uuid>
​
workflow
object